Results for “pa_prj_accum_headers_ar”

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

Overview

PA_PRJ_ACCUM_HEADERS_AR is a Projects (PA) module table residing in the PA schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented role is that of an Archive/Purge companion table: it stores archived copies of rows originally held in the main project accumulation headers table, enabling historical retention of summarized project cost and revenue accumulation data after those records have been purged from the operational table. The metadata explicitly directs readers to the column comments on the main table for semantic definitions, indicating that PA_PRJ_ACCUM_HEADERS_AR mirrors the structure and meaning of its parent table but is populated only through the archive/purge process rather than through routine transaction processing.

From a dimensional modeling perspective, the heuristic Data Vault classification supplied in the metadata is standalone, meaning the table does not exhibit the foreign-key density typically associated with a hub or link. A modeling suggestion, therefore, is to treat this object as neither a canonical hub nor a link, but as an archival or history-adjacent structure whose grain mirrors the accumulation header record. Because purge-related identifiers are present, it is best understood as a retention container rather than an integrated entity within a Data Vault model.

Key Information Stored

The table contains 22 documented columns. The most significant fall into three groups: purge/archive control columns, project accumulation business columns, and standard EBS audit columns.

• PURGE_BATCH_ID — identifies the purge batch under which the row was archived; it is the only documented foreign key, referencing PA_PURGE_BATCHES_ALL.
• PURGE_RELEASE and PURGE_PROJECT_ID — capture the release and project context associated with the purge run.
• PROJECT_ACCUM_ID — the accumulation identifier inherited from the main table; this is the closest candidate to a business key for the archived record.
• PROJECT_ID and TASK_ID — the project and task to which the accumulation belongs.
• ACCUM_PERIOD — the accounting period for which the accumulation was computed, a primary driver of reporting queries.
• RESOURCE_ID, RESOURCE_LIST_ID, RESOURCE_LIST_ASSIGNMENT_ID, RESOURCE_LIST_MEMBER_ID — identify the resource and resource-list context of the accumulation.
• TASKS_RESTRUCTURED_FLAG and SUM_EXCEPTION_CODE — flags and exception indicators reflecting task restructuring and summation anomalies.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — standard EBS who/when and concurrent program audit columns.

No surrogate primary key or unique index is documented in the supplied metadata; PROJECT_ACCUM_ID combined with purge context is the most practical business-key candidate for querying.

Common Use Cases and Queries

Typical usage centers on audit, retention, and reconciliation reporting after purge cycles. Because the table is populated by the archive/purge process, queries usually join back to PA_PURGE_BATCHES_ALL to establish when and under what batch the data was archived.

• Retrieving all archived accumulation headers for a project: SELECT * FROM pa.pa_prj_accum_headers_ar WHERE project_id = :project_id;
• Reconciling archive volume by purge batch: SELECT purge_batch_id, COUNT(*) FROM pa.pa_prj_accum_headers_ar GROUP BY purge_batch_id;
• Auditing exception accumulations: SELECT project_id, task_id, accum_period, sum_exception_code FROM pa.pa_prj_accum_headers_ar WHERE sum_exception_code IS NOT NULL;
• Tracing concurrent program provenance: querying by REQUEST_ID, PROGRAM_ID, or PROGRAM_APPLICATION_ID to identify the job that archived the rows.

These patterns support historical trending, purge verification, and internal audit evidence where operational rows no longer exist in the primary accumulation table.

Related Objects

• PA_PURGE_BATCHES_ALL — referenced through the documented foreign key PA_PRJ_ACCUM_HEADERS_AR.PURGE_BATCH_ID → PA_PURGE_BATCHES_ALL.PURGE_BATCH_ID; provides batch-level context.
• The main project accumulation headers table — the source table from which archived rows originate; its column comments define the semantics of this archive table as stated in the metadata.
• PA_PROJECTS_ALL / PA_TASKS — supply PROJECT_ID and TASK_ID business context for archived accumulations.
• PA_RESOURCE_LIST_* tables — relate to RESOURCE_LIST_ID and RESOURCE_LIST_MEMBER_ID columns for resource assignment detail.
• PA_PERIODS / GL periods — relevant to interpreting ACCUM_PERIOD values in reporting.

Because the metadata classifies this object as standalone, reliance on the FK to PA_PURGE_BATCHES_ALL and on the mirrored structure of the main accumulation table represents the principal documented integration path.