Results for “pa_prj_accum_budgets_ar”

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

Overview

PA_PRJ_ACCUM_BUDGETS_AR is an archive companion table in the Oracle Projects (PA) schema, owned by the PA user and valid in Oracle EBS 12.1.1 and 12.2.2. Its documented purpose is archive and purge processing: the ETRM metadata states that "Pa_Project_Accum_Budgets_ar is a table for Archive/Purge. Refer to comments on the columns in the main table." The table therefore mirrors the structure of the production accumulated budgets table and is populated during the Project Archive and Purge cycle, preserving historical accumulated budget balances for projects that have been archived or removed from active reporting.

The documented physical schema contains 66 columns. Under the heuristic Data Vault classification mined from the foreign-key structure, the object is classified as standalone. In Data Vault modeling terms this suggests the table is best treated as an independent satellite-like staging structure rather than a true hub or link. This is consistent with its archive role: it is a copy-oriented, historically scoped repository rather than an entity that participates in referential relationships with the rest of the application model.

Key Information Stored

The table retains the accumulation and budget metrics from the main table, together with the purge-control columns that identify the archive context. The most significant columns include:

• PURGE_BATCH_ID — Identifier of the purge batch that captured the row; the foreign key to PA_PURGE_BATCHES_ALL.
• PURGE_RELEASE — Release designation of the purge event.
• PURGE_PROJECT_ID — The project identifier associated with the archived record.
• PROJECT_ACCUM_ID — The original accumulated budget identifier from the production table.
• BUDGET_TYPE_CODE — The budget type (for example, approved, original, or current) to which the amounts relate.
• BASE_RAW_COST_TOT / ORIG_RAW_COST_TOT — Total raw cost in base and original currency.
• BASE_BURDENED_COST_TOT / ORIG_BURDENED_COST_TOT — Total burdened cost in base and original currency.
• BASE_REVENUE_TOT / ORIG_REVENUE_TOT — Total revenue in base and original currency.
• BASE_QUANTITY_TOT / ORIG_QUANTITY_TOT — Total quantities in base and original units of measure.
• BASE_LABOR_HOURS_TOT / ORIG_LABOR_HOURS_TOT — Total labor hours in base and original terms.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — Concurrent request and program audit context for the archive run.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard Who columns recording row creation and last modification.

The periodic columns (PP, PTD, YTD, ITD) carry the same cost, revenue, quantity, and labor-hour measures at prior period, period-to-date, year-to-date, and inception-to-date granularity. The documented relationship data identifies PURGE_BATCH_ID as the sole foreign key, referencing PA_PURGE_BATCHES_ALL. No surrogate primary key or unique index is documented in the metadata; PROJECT_ACCUM_ID functions as the principal business-key candidate carried over from the source table.

Common Use Cases and Queries

Typical uses center on audit, retention, and historical reporting rather than online transaction processing. Common patterns include:

• Verifying which projects were archived within a given purge batch by joining PURGE_BATCH_ID to PA_PURGE_BATCHES_ALL.
• Reconstructing cumulative project cost, revenue, and labor-hour totals for archived projects using the *_TOT columns.
• Comparing base versus original currency amounts to assess currency fluctuation impact on archived budgets.
• Auditing purge activity by REQUEST_ID and PROGRAM_ID to trace which concurrent program archived the data.

A representative query joins the archive table to the purge batch definition to list archived budget totals for a specific batch:

SELECT b.purge_batch_id, a.purge_project_id, a.budget_type_code, a.base_raw_cost_tot, a.orig_raw_cost_tot, a.base_burdened_cost_tot, a.base_revenue_tot FROM pa_prj_accum_budgets_ar a, pa_purge_batches_all b WHERE a.purge_batch_id = b.purge_batch_id AND a.purge_batch_id = :batch_id;

Reporting teams also query this table for long-horizon trend analysis on completed projects that no longer appear in the production accumulated budgets table.

Related Objects

• PA_PURGE_BATCHES_ALL — Referenced by the PA_PRJ_ACCUM_BUDGETS_AR.PURGE_BATCH_ID foreign key; the parent batch definition table for archive and purge runs.
• PA_PRJ_ACCUM_BUDGETS — The production accumulated budgets table whose columns and semantics are mirrored here; the source of archived rows.
• PA_PROJECTS_ALL — Provides project context for PURGE_PROJECT_ID and PROJECT_ACCUM_ID values.
• PA_BUDGET_TYPES — Defines the BUDGET_TYPE_CODE values stored on each archived row.
• PA_PURGE_PROJECTS — Groups projects eligible for a given purge batch and complements this table's archival records.
• PA_PROJECT_ACCUM_HEADERS — Related accumulation header structure for the underlying project accumulations.

These objects collectively support project archival reporting, purge auditing, and historical budget analysis within the Oracle Projects module.