Results for “quantity_source”

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

Overview

PA_BUDGET_LINES_AR is an Oracle Projects (PA) archive table that holds historical budget line records removed from the operational table PA_BUDGET_LINES through the Archive and Purge process. It resides in the PA schema and, like its siblings in the AR family, mirrors the column structure of its parent table so that purged rows remain recoverable for audit, reconciliation, and regulatory retention purposes. According to Oracle's ETRM documentation for release 12.2.2, the table is VALID and consists of 40 columns; the object description explicitly directs readers to the column comments on the main budget lines table, confirming that semantics are shared rather than redefined here.

Archiving and purging in Oracle Projects is a controlled, batch-driven operation. Each purge run is registered in PA_PURGE_BATCHES_ALL, and the PURGE_BATCH_ID foreign key on PA_BUDGET_LINES_AR ties every archived row to the batch that produced it. This makes the table inherently an audit-bearing structure rather than a transactional one. Under a heuristic Data Vault classification inferred from its foreign key topology, PA_BUDGET_LINES_AR would be modeled as a satellite: it is a standalone table (no downstream tables reference it) whose identifying relationship is to the purge batch hub, and it carries descriptive and measure attributes alongside a change-tracking timestamp set.

Key Information Stored

The most business-relevant columns include the budget measure set — RAW_COST, BURDENED_COST, REVENUE, and QUANTITY — each of which has a corresponding *_SOURCE column (RAW_COST_SOURCE, BURDENED_COST_SOURCE, REVENUE_SOURCE, QUANTITY_SOURCE) indicating whether the amount was entered manually or derived by the system. CHANGE_REASON_CODE and DESCRIPTION record why a budget line was modified or removed, and PERIOD_NAME plus START_DATE / END_DATE position the line along the project accounting calendar.

Identity and lineage columns include PURGE_BATCH_ID and PURGE_RELEASE, which together identify the archive event, and PURGE_PROJECT_ID, which preserves the project context after the parent project record may itself have been purged. RESOURCE_ASSIGNMENT_ID and PM_BUDGET_LINE_REFERENCE link the archived line back to its originating resource assignment and to the external project-management reference where applicable. The standard Oracle WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) are retained for auditability. Fifteen ATTRIBUTE columns plus ATTRIBUTE_CATEGORY provide the flexfield (DFF) storage consistent with the Projects product convention. No surrogate primary key is documented in the supplied metadata; the effective grain is the archived budget-line row within a purge batch, and PURGE_BATCH_ID is the only documented foreign key.

Common Use Cases and Queries

The primary use case is post-purge audit and historical reporting: reconstructing what a project budget looked like before archival. A typical query joins the archive lines to the batch header:

• Archived budget totals by purge batch: SELECT a.purge_batch_id, SUM(a.raw_cost), SUM(a.burdened_cost), SUM(a.revenue) FROM pa.pa_budget_lines_ar a GROUP BY a.purge_batch_id;
• Recovery of a specific project's purged lines: SELECT * FROM pa.pa_budget_lines_ar WHERE purge_project_id = :project_id AND purge_batch_id = :batch_id;
• Batch provenance and timing: SELECT a.*, b.* FROM pa.pa_budget_lines_ar a, pa.pa_purge_batches_all b WHERE a.purge_batch_id = b.purge_batch_id;
• Change-reason analysis: SELECT change_reason_code, COUNT(*) FROM pa.pa_budget_lines_ar GROUP BY change_reason_code;

Reporting scenarios include audit trails for government or internal controls, verification that purge scripts completed successfully, and comparisons of archived versus live budget data when a project is re-opened or disputed. Because archiving is irreversible from the application, SQL-level access is generally restricted to DBAs and audit roles.

Related Objects

• PA_PURGE_BATCHES_ALL — referenced via PURGE_BATCH_ID; the batch registry that governs every archive/purge run.
• PA_BUDGET_LINES — the operational source table whose row structure PA_BUDGET_LINES_AR mirrors and from which rows are archived.
• PA_BUDGET_VERSIONS — parent construct defining the budget version to which archived lines belonged.
• PA_PROJECTS_ALL — project master referenced by PURGE_PROJECT_ID for post-purge project identification.
• PA_RESOURCE_ASSIGNMENTS — referenced via RESOURCE_ASSIGNMENT_ID to identify the assigned resource.
• PA_PERIODS_ALL — supplies the accounting period context carried in PERIOD_NAME.
• PA_BUDGET_LINES_AR is not referenced by any dependent table; it is a terminal archive structure, which is why it is classified as standalone within the heuristic model.