Results for “pa_prj_accum_commit_ar”

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

Overview

PA_PRJ_ACCUM_COMMIT_AR is an archive and purge staging table owned by the PA (Projects) schema in Oracle EBS 12.1.1 and 12.2.2. Its name mirrors the operational table PA_PRJ_ACCUM_COMMIT, and the trailing "_AR" suffix conventionally denotes an "Archive" companion object used by the Oracle Projects Archive and Purge process. The table stores project commitment accumulation balances captured at the moment a purge batch is executed, allowing historical commitment data to be preserved after the corresponding transactional rows are removed from the live tables. Per the ETRM documentation, the object is described as a table for archive/purge, and column semantics are inherited directly from the main table, with the note to refer to comments on the columns in the main table.

Under a heuristic Data Vault classification (mined purely from the foreign-key structure), PA_PRJ_ACCUM_COMMIT_AR resolves as a standalone object rather than a hub, link, or satellite. In Data Vault terms, this suggests the table should be modeled as a self-contained record set keyed by its own surrogate identifier, with no enforced parent hub relationship in the documented schema. Its only documented foreign key, PURGE_BATCH_ID, references PA_PURGE_BATCHES_ALL, tying each archived row back to the batch run that produced it.

Key Information Stored

The documented physical schema contains 26 columns in the PA schema. The most significant are summarized below.

• PURGE_BATCH_ID — the purge batch identifier; the sole documented foreign key, linking to PA_PURGE_BATCHES_ALL.
• PURGE_RELEASE — the release identifier associated with the purge run.
• PURGE_PROJECT_ID — the project identifier captured for the archived record.
• PROJECT_ACCUM_ID — the accumulation identifier linking the archived row to the original accumulation record; a strong business-key candidate.
• CMT_RAW_COST_ITD / _YTD / _PP / _PTD — raw commitment cost balances for inception-to-date, year-to-date, prior period, and period-to-date.
• CMT_BURDENED_COST_ITD / _YTD / _PP / _PTD — burdened commitment cost balances across the same four time horizons.
• CMT_QUANTITY_ITD / _YTD / _PP / _PTD — commitment quantities for each period basis.
• CMT_UNIT_OF_MEASURE — the unit of measure for the stored quantities.
• LAST_UPDATE_DATE, CREATION_DATE, LAST_UPDATED_BY, CREATED_BY, LAST_UPDATE_LOGIN — standard EBS WHO columns providing audit lineage.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program context identifying the request that staged the row.

The metadata does not document a named single-column surrogate primary key, but PURGE_BATCH_ID combined with PROJECT_ACCUM_ID is the natural composite key for locating a specific archived accumulation within a batch.

Common Use Cases and Queries

Typical usage centers on purge auditing and historical commitment reporting after transactions have been removed from live tables. A common query joins the archive table to its purge batch:

• Audit a purge run: SELECT * FROM pa.pa_prj_accum_commit_ar WHERE purge_batch_id = :batch_id;
• Reconcile a project's archived commitment balances across periods using CMT_RAW_COST_ITD and CMT_BURDENED_COST_ITD grouped by PURGE_PROJECT_ID.
• Trace the originating concurrent request via PROGRAM_ID and REQUEST_ID to confirm which process staged the archive rows.
• Compare archived versus live balances by joining on PROJECT_ACCUM_ID where the live row still exists.

Related Objects

• PA_PURGE_BATCHES_ALL — referenced by PURGE_BATCH_ID; the parent purge batch definition.
• PA_PRJ_ACCUM_COMMIT — the main (non-archive) accumulation table whose column semantics this object mirrors.
• PA_PURGE_BATCH_ENTITIES — entity-level purge tracking aligned to the same batch.
• PA_PROJECTS_ALL — source of PURGE_PROJECT_ID project context.
• FND_CONCURRENT_REQUESTS — join on REQUEST_ID for concurrent program diagnostics.
• PA_ARCHIVE_PURGE_APIS / PRC:Archive and Purge — the process that populates and consumes this table.