HP PPM and Informatica ETL Fundamentals

Support demands are typically free of charge as they involve basic assistance and troubleshooting. Standard demands and emergency demands usually have associated costs based on complexity, priority, and resource allocation.

In HP Project and Portfolio Management (PPM) / Kintana, the KNTA_INTERFACE_ERRORS table stores log information and error messages related to failed transactions or workflow steps executed via the Open Interface. Other tables like KNTA_DEBUG_MESSAGES are used for transient PL/SQL debug statements.

In PPM workflow design, the validation values defined in a subworkflow must match exactly with the return step's values. This ensures proper data flow and status transitions - mismatched values would break the workflow logic.

In HP PPM (Project Portfolio Management), making fields available in Advanced Search requires enabling the 'Display on Search and Filter' option under the Attributes tab for each field in the request type configuration. This is standard PPM functionality for field visibility control.

Variable length for storing field values in request types is not fixed to specific values like 200, 1000, or 4000 characters. The appropriate length depends on the field type, database column definition, and specific requirements of the field being stored. Different fields have different maximum length requirements.

When an AXA_RT_Application_Demand request type integrated with Augeo is created, records are inserted into both Augeo custom tables: AXA_AUGEO_TASKS_CURR_STATUS (for tracking current status) and AXA_AUGEO_TASKS_FLOW (for tracking workflow/flow information). This dual-table approach maintains both status and flow state for integration purposes.

In HP PPM's database schema, KCRT_REQUESTS, KCRT_REQ_HEADER_DETAILS, and KCRT_REQUEST_DETAILS are valid table names. However, KCRT_REQUESTS_TYPES is not a standard table name - the naming convention would typically use REQUEST_TYPE (singular) or a different naming pattern. This question tests knowledge of the actual PPM database schema.

In HP PPM workbench, the Configuration tab contains system configuration options including Workflows and Validations. Demand Mgmt handles demand management, Dashboard shows overview metrics, and Environments manages environment settings. Configuration is the correct tab for workflow and validation rules.

Data synchronization between Augeo and PPM occurs weekly, not hourly, daily, or monthly. This weekly data flow interval is part of the integration architecture between these systems. The frequency represents a balance between data freshness and system performance.

The default value for 'Business Approver' in AXA_RT_Application_Demand's Ownership section inherits from 'Primary Business Approver' in AXA_RT_Application_Definition's Application section. This represents a parent-child relationship where application definition settings flow down to specific demand requests.

SQL scripts invoked by Report Types are typically placed on the Application server rather than the Database server. This architecture allows the application server to manage report execution and SQL script invocation, keeping database servers focused on data storage and query execution rather than report logic.

AXA naming conventions follow a specific pattern: Module_DM_ES_Action format. AXA_DM_ES_Check_Fast_Track correctly follows this pattern with DM (Demand Management) module designation, while others are missing module prefixes or have incorrect formats. The convention ensures clear identification of module, functionality, and action.

Tables and Views with names beginning with KCRT (likely standing for 'Kynergy Request' or similar) were created by HP as part of the HP PPM (Project Portfolio Management) product database schema. This is not AXA or TCS custom development but HP's native table structure.

Test load functionality has specific constraints: it can only be performed on sessions configured for normal mode (not bulk mode), and it cannot be used with XML sources (flat file sources are acceptable). These limitations exist because test load performs validation that's incompatible with bulk processing and XML parsing complexity.

The Union transformation in Informatica is a passive transformation that combines data from multiple sources. When it receives data from multiple transaction generators, the Integration Service drops all incoming transaction boundaries and creates new transaction boundaries. Option A is incorrect because Union does not generate transactions. Option B is incorrect because Union does not remove duplicates (Unioner does). Option D is incorrect because you cannot use an active transformation like Sequence Generator upstream from Union.

To use the Workflow Monitor in Informatica, you need either the Workflow Manager privilege with execute permission on the folder OR the Workflow Operator privilege with read permission on the folder. Both options grant sufficient access to monitor workflows. Option A alone is insufficient, and Option B alone is also insufficient, but either combination works.

The Workflow Monitor provides session-specific details that help tune performance. Buffer block size can be optimized based on performance counters. Index and data cache sizes for Aggregator and Joiner transformations can be tuned based on session details. Source Qualifier does not have cache settings - cache is configured at the source/target level, not for Source Qualifier itself.

For performance counters in Informatica, the minimum percent of counter value for source qualifiers and targets typically ranges between 0-20. This indicates the minimum time spent on these operations. Higher ranges (20-40, 40-60) would indicate poor performance, while 5-15 is too narrow for the general guideline.

For XML target caches in Informatica, the index cache stores primary key and foreign key information in separate caches, while the data cache stores the actual XML row data during XML target generation. Option B is incorrect because index cache stores key information, not row data. Option C is incorrect because data cache stores row data, not key information.