Search Results pa_resource_accum_details




Overview

The PA_RESOURCE_ACCUM_DETAILS table is a core transactional table within the Oracle E-Business Suite Projects module (PA). Its primary role is to store the detailed mapping relationship between a summarized transaction record (in PA_TXN_ACCUM) and a specific member of a project's resource list. This table acts as a critical junction, providing an auditable trail of how raw expenditure items are associated with project resources for the purposes of cost accumulation, burdening, and reporting. It is essential for maintaining data integrity in the project costing engine, particularly in releases 12.1.1 and 12.2.2 where the accumulation architecture is central to performance.

Key Information Stored

The table's structure is defined by its foreign key relationships, which point to the essential entities involved in the resource mapping process. The primary key is a composite of TXN_ACCUM_ID and RESOURCE_LIST_ASSIGNMENT_ID, ensuring a unique link for each mapping instance. Key columns include TXN_ACCUM_ID, which references the summarized transaction in PA_TXN_ACCUM, and RESOURCE_LIST_ASSIGNMENT_ID, which links to the specific assignment in PA_RESOURCE_LIST_ASSIGNMENTS. Other critical foreign keys are PROJECT_ID and TASK_ID (linking to PA_PROJECT_ACCUM_HEADERS), RESOURCE_LIST_MEMBER_ID, RESOURCE_LIST_ID (linking to PA_RESOURCE_LISTS_ALL_BG), and RESOURCE_ID (linking to PA_RESOURCES). Together, these columns definitively answer which resource, from which list, was used to cost a given accumulated transaction.

Common Use Cases and Queries

This table is predominantly used for diagnostic reporting, reconciliation, and audit purposes within project costing. A common scenario involves tracing the cost posted to a project task back to the originating resource assignment. For example, to analyze all resource mappings for a specific project, one might use a query joining to PA_TXN_ACCUM and PA_RESOURCES. Another critical use case is during period close or cost reconciliation, where queries against this table help verify that transactions have been correctly mapped according to the active resource list assignments. Sample SQL often involves filtering by PROJECT_ID, TXN_ACCUM_ID, or RESOURCE_ID and joining to related descriptive tables like PA_RESOURCES to get resource names.

Related Objects

As indicated by its foreign keys, PA_RESOURCE_ACCUM_DETAILS has integral dependencies on several key Projects tables. It is a direct child of PA_TXN_ACCUM and PA_RESOURCE_LIST_ASSIGNMENTS. It also references PA_PROJECT_ACCUM_HEADERS (via project/task), PA_RESOURCE_LISTS_ALL_BG, and PA_RESOURCES. This table is typically accessed indirectly through standard Oracle Projects APIs and public views rather than via direct DML. Its existence is crucial for the processes managed by the Project Costing engine, and any data fixes or deep analysis of cost accumulation issues will invariably involve examining records in this table.