Results for “pn_var_vol_arch_all”

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

Overview

PN_VAR_VOL_ARCH_ALL is a Property Manager (PN) archive table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores volume data modified during batch import. It functions as a historical snapshot of volume records processed through batch operations, preserving both current and historical attributes so that Property Manager can audit, reconcile, and report on changes made during bulk loading. The table resides in the PN schema and is present in both the 12.1.1 and 12.2.2 releases with 52 documented columns.

From a Data Vault modeling perspective, the metadata classifies this object heuristically as standalone, meaning it does not act as a strict hub or link in the mined foreign-key graph. In practical terms, it behaves like a satellite capturing descriptive and historical attributes keyed by the surrogate VOL_ARCH_ID, with soft associations to the volume history and group dates structures. Treating it as a satellite suggests it should be joined to its parent volume history rather than used as an independent fact source.

Key Information Stored

The table is centered on volume archiving, with the following columns carrying the most analytical and operational weight.

• VOL_ARCH_ID — the surrogate primary key defined by PN_VAR_VOL_ARCH_PK and also the sole column in unique index PN_VAR_VOL_ARCH_U1, effectively serving as the business-key candidate.
• VOL_HIST_ID and VOL_HIST_NUM — the foreign key to PN_VAR_VOL_HIST_ALL and the associated history number, linking each archived row to its originating volume history record.
• GRP_DATE_ID and GROUP_DATE — the group date reference (foreign key to PN_VAR_GRP_DATES_ALL) and its display value, used for period grouping.
• PERIOD_ID, START_DATE, END_DATE — period identification and the effective date range of the volume record.
• REPORTING_DATE, DUE_DATE, INVOICING_DATE — milestone dates driving reporting and obligation tracking.
• ACTUAL_GL_ACCOUNT_ID, ACTUAL_AMOUNT, FOR_GL_ACCOUNT_ID, FORECASTED_AMOUNT — actual versus forecasted accounting amounts and their GL accounts.
• VOL_HIST_STATUS_CODE, REPORT_TYPE_CODE, CERTIFIED_BY — status, report classification, and certification owner.
• ORG_ID and HIST_ORG_ID — multi-org operating unit context for both the current and historical record.

Common Use Cases and Queries

Typical applications include reconciling batch-imported volumes against source systems, auditing changes to forecasted and actual amounts, and producing period-based volume reports. A representative query joining archive data to volume history might read:

• SELECT a.VOL_ARCH_ID, a.VOL_HIST_ID, a.PERIOD_ID, a.ACTUAL_AMOUNT, a.FORECASTED_AMOUNT FROM PN_VAR_VOL_ARCH_ALL a WHERE a.ORG_ID = :org_id AND a.PERIOD_ID = :period_id;
• SELECT a.VOL_ARCH_ID, h.VOL_HIST_NUM, g.GROUP_DATE FROM PN_VAR_VOL_ARCH_ALL a JOIN PN_VAR_VOL_HIST_ALL h ON a.VOL_HIST_ID = h.VOL_HIST_ID JOIN PN_VAR_GRP_DATES_ALL g ON a.GRP_DATE_ID = g.GRP_DATE_ID;

Report developers frequently filter on VOL_HIST_STATUS_CODE and REPORT_TYPE_CODE to isolate certified or forecast volumes, and compare ACTUAL_AMOUNT against FORECASTED_AMOUNT to compute variances for variance reporting.

Related Objects

The most significant related objects, derived from documented foreign-key relationships, are:

• PN_VAR_VOL_HIST_ALL — referenced via VOL_HIST_ID; provides the parent volume history record for each archived row.
• PN_VAR_GRP_DATES_ALL — referenced via GRP_DATE_ID; supplies group date definitions and period grouping.
• PN_VAR_VOL_ARCH_PK — the primary key constraint on VOL_ARCH_ID.
• PN_VAR_VOL_ARCH_U1 — the unique index on VOL_ARCH_ID acting as the business-key candidate.
• PN.VAR_VOL (current volume tables) — the operational source from which archived rows are generated during batch import.
• PN standard concurrent programs and APIs for volume batch import that populate and maintain this archive table.

Because the table is classified as standalone with soft FK associations, joins should rely on the documented columns VOL_HIST_ID and GRP_DATE_ID rather than assuming enforced referential constraints.