Results for “original_flag”

16 results




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

Overview

PA_BUDGET_VERSIONS_AR is an Oracle Projects (PA) archive/purge table owned by the PA schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It functions as the archive counterpart to the transactional PA_BUDGET_VERSIONS table, holding rows that have been extracted from the production budget-versions structures during an archive or purge operation. As documented in the ETRM metadata, the table exists specifically to support Archive/Purge processing, and its column semantics mirror those of the main table ("Refer to comments on the columns in the main table"). Each record represents an archived project budget version — a discrete, numbered iteration of a project's cost or revenue budget — together with the purge context that identifies the batch and release under which the row was archived.

The heuristic Data Vault classification derived from the foreign-key structure is standalone. This reflects the fact that PA_BUDGET_VERSIONS_AR does not itself act as a hub or link within the derived model; it is better modeled as a type-2 satellite-style history or archival store keyed by its own surrogate identifier, with a single documented outbound foreign key to PA_PURGE_BATCHES_ALL.

Key Information Stored

The table contains 48 documented columns. The most significant are:

Common Use Cases and Queries

Because the table is archival, queries typically support audit, reconciliation, and reporting on purged budget data rather than live transaction processing. A common pattern joins the archive table to the purge batch table to identify what was removed in a specific run:

  • Select all archived budget versions for a purge batch: SELECT * FROM pa.pa_budget_versions_ar WHERE purge_batch_id = :batch_id;
  • Reconcile counts between archive and source: SELECT project_id, COUNT(*) FROM pa.pa_budget_versions_ar GROUP BY project_id;
  • Recover historical measures for a project: SELECT version_number, raw_cost, burdened_cost FROM pa.pa_budget_versions_ar WHERE project_id = :project_id;
  • Audit who baselined archived versions: SELECT baselined_by_person_id, baselined_date FROM pa.pa_budget_versions_ar;

Related Objects

The principal related objects are:

  • PA_PURGE_BATCHES_ALL — Joined via PURGE_BATCH_ID; the parent purge-batch definition.
  • PA_BUDGET_VERSIONS — The live source table from which archived rows originate.
  • PA_BUDGET_LINES and PA_BUDGET_LINES_AR — Line-level details corresponding to each archived version.
  • PA_PROJECTS_ALL — Projects referenced via PROJECT_ID.
  • PA_BUDGET_TYPES — Lookup for BUDGET_TYPE_CODE semantics.
  • PER_ALL_PEOPLE_F — Person details for BASELINED_BY_PERSON_ID.