Results for “pa_project_accum_headers”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PA_PROJECT_ACCUM_HEADERS is a Projects (PA) module table that stores project summary, or accumulation, records. Each row represents a unique combination of project, task, and resource list member, serving as the master header for accumulated project balances. Rather than holding transactional detail, it anchors the aggregated results that Oracle Projects derives from actuals, budgets, and commitments so that summary reporting and burdening processes do not need to re-scan detail transactions.

In Data Vault terms, the mined structure suggests a satellite-leaning classification. The table carries a surrogate primary key and a natural business key composed of project, task, and resource list member, which is characteristic of a satellite attached to a project/task/resource hub combination. This is a modeling heuristic only; functionally the table behaves as the aggregate header within the Projects accumulation schema.

Key Information Stored

The table contains 19 documented columns in release 12.2.2. The most significant are:

• PROJECT_ACCUM_ID — surrogate primary key (PA_PROJECT_ACCUM_HEADERS_PK) and the join key to all child accumulation tables.
• PROJECT_ID — foreign key to PA_PROJECTS_ALL; identifies the project.
• TASK_ID — foreign key to PA_TASKS; identifies the task within the project.
• RESOURCE_LIST_MEMBER_ID — foreign key to PA_RESOURCE_LIST_MEMBERS; identifies the resource member being accumulated.
• PROJECT_ID, TASK_ID, RESOURCE_LIST_MEMBER_ID — together form the unique business key (PA_PROJECT_ACCUM_HEADERS_U2).
• ACCUM_PERIOD — the accumulation period to which the summary belongs.
• RESOURCE_ID — the underlying resource associated with the accumulation.
• RESOURCE_LIST_ID — foreign key to PA_RESOURCE_LISTS_ALL_BG.
• RESOURCE_LIST_ASSIGNMENT_ID — foreign key to PA_RESOURCE_LIST_ASSIGNMENTS, linking the assignment context.
• TASKS_RESTRUCTURED_FLAG — indicates whether the task structure was restructured, affecting accumulation validity.
• SUM_EXCEPTION_CODE — captures any exception raised during summarization.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard audit columns.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program request context that generated or last updated the row.

Common Use Cases and Queries

Typical usage centers on project summary reporting and reconciliation of accumulated actuals, budgets, and commitments. A common pattern joins the header to its child tables via PROJECT_ACCUM_ID.

To find accumulation headers for a project:

• SELECT project_accum_id, project_id, task_id, resource_list_member_id, accum_period FROM pa_project_accum_headers WHERE project_id = :p_project_id;

To retrieve accumulated actuals alongside the header:

• SELECT h.project_id, h.task_id, h.resource_list_member_id, a.* FROM pa_project_accum_headers h, pa_project_accum_actuals a WHERE h.project_accum_id = a.project_accum_id AND h.accum_period = :p_period;

The table also supports detecting summarization errors through SUM_EXCEPTION_CODE and identifying records invalidated by task restructuring via TASKS_RESTRUCTURED_FLAG, which is useful in troubleshooting accumulation runs.

Related Objects

The header is referenced by several child accumulation tables and references Projects master data:

• PA_PROJECT_ACCUM_ACTUALS — joins on PROJECT_ACCUM_ID; holds accumulated actual amounts.
• PA_PROJECT_ACCUM_BUDGETS — joins on PROJECT_ACCUM_ID; holds accumulated budget amounts.
• PA_PROJECT_ACCUM_COMMITMENTS — joins on PROJECT_ACCUM_ID; holds accumulated commitment amounts.
• PA_PROJECTS_ALL — parent project definition, via PROJECT_ID.
• PA_TASKS — parent task, via TASK_ID.
• PA_RESOURCE_LIST_MEMBERS — resource member, via RESOURCE_LIST_MEMBER_ID.
• PA_RESOURCE_LIST_ASSIGNMENTS — via RESOURCE_LIST_ASSIGNMENT_ID.
• PA_RESOURCE_LISTS_ALL_BG — via RESOURCE_LIST_ID.
• PA_RESOURCE_ACCUM_DETAILS — shares PROJECT_ID, TASK_ID, and RESOURCE_LIST_MEMBER_ID for detail-level accumulation.