Search Results pji_fp_txn_accum_header

Overview

The table PJI_FP_TXN_ACCUM_HEADER is a core data object within the Oracle E-Business Suite (EBS) Project Intelligence (PJI) module, versions 12.1.1 and 12.2.2. As indicated by its product module status, PJI is considered obsolete, with its functionality superseded by Oracle Project Portfolio Management (PPM) and Oracle Business Intelligence Applications (OBIA). This table serves a foundational role in the project costing and resource planning architecture. Its primary function is to store unique combinations of resource attributes that are essential for mapping transactions to the Resource Breakdown Structure (RBS). The RBS is a hierarchical framework used to categorize and report on project resources, enabling detailed cost accumulation and analysis. This table acts as a header or reference point, ensuring transactional data is correctly classified within the project accounting and intelligence schemas.

Key Information Stored

The table's structure is designed to capture the key dimensions of a project resource or expenditure. While the full column list is not provided in the excerpt, the documented foreign key relationships reveal critical columns that define the resource attribute combinations. These include EXPENDITURE_ORG_ID and EXPENDITURE_ORGANIZATION_ID, which link to the HR_ALL_ORGANIZATION_UNITS table to identify the spending organization. The EXPENDITURE_TYPE column references PA_EXPENDITURE_TYPES, classifying the nature of the cost (e.g., labor, material). The EVENT_TYPE column references PA_EVENT_TYPES, categorizing the business event associated with the transaction. The table likely contains a primary key column (e.g., a header identifier) and other descriptive attributes that together form a unique combination for RBS mapping and subsequent transactional roll-up.

Common Use Cases and Queries

This table is integral to the ETL (Extract, Transform, Load) processes that populate the PJI summary tables for reporting. Common use cases involve analyzing resource costs by organizational hierarchy or expenditure category within the Project Intelligence dashboards. A typical analytical query might join this header table to fact tables to aggregate costs. For instance, to analyze planned costs by organization and expenditure type, a query pattern would be:

• SELECT h.EXPENDITURE_ORG_ID, h.EXPENDITURE_TYPE, SUM(f.PLAN_AMOUNT)
• FROM PJI_FP_TXN_ACCUM_HEADER h, PJI_FP_TXN_ACCUM_F f
• WHERE h.HEADER_ID = f.HEADER_ID
• GROUP BY h.EXPENDITURE_ORG_ID, h.EXPENDITURE_TYPE;

Data maintenance queries are also common, such as identifying orphaned header records not linked to any transactional fact data.

Related Objects

PJI_FP_TXN_ACCUM_HEADER maintains defined foreign key relationships with several foundational EBS tables, as documented. These relationships are critical for data integrity and dimensional reporting:

• HR_ALL_ORGANIZATION_UNITS: Joined via EXPENDITURE_ORG_ID and EXPENDITURE_ORGANIZATION_ID to provide organizational hierarchy details.
• PA_EXPENDITURE_TYPES: Joined via EXPENDITURE_TYPE to provide the expenditure type name and classification.
• PA_EVENT_TYPES: Joined via EVENT_TYPE to provide the event type description.

This table is a parent to transactional fact tables within the PJI schema, such as PJI_FP_TXN_ACCUM_F (for financial plan transactions), where the header's primary key is referenced as a foreign key to maintain the resource attribute context for each fact record.