Search Results cst_ap_variance_headers_pk

Overview

CST_AP_VARIANCE_HEADERS is a transaction table owned by the BOM schema in Oracle E-Business Suite, documented as valid in release 12.1.1 and 12.2.2. It stores the variance information calculated for a purchase order distribution, aggregated at the header level for each batch run of the payables variance process. In the procure-to-pay and cost management flow, Accounts Payable invoice price differences against purchase order receipts are captured and posted as cost variances; this table represents the persistent header record of that activity, with the detailed breakdown held in the companion lines table.

Because the table has a surrogate primary key and foreign keys pointing outward to a batch parent and to cost groups, the mined Data Vault classification is satellite-leaning. Under that heuristic, CST_AP_VARIANCE_HEADERS behaves less like an enterprise hub and more like a descriptive satellite attached to the CST_AP_VARIANCE_BATCHES business key, carrying measurable variance amounts and dimensional context.

Key Information Stored

The primary key is the surrogate column VARIANCE_HEADER_ID, enforced by the unique index CST_AP_VARIANCE_HEADERS_PK and duplicated in the alternate unique index CST_AP_VARIANCE_HEADERS_U1. Business-key candidates are documented through CST_AP_VARIANCE_HEADERS_U2, a composite unique index over BATCH_ID, PO_DISTRIBUTION_ID, and COST_GROUP_ID, which guarantees one header row per distribution per cost group within a batch.

• VARIANCE_HEADER_ID – surrogate primary key.
• PO_DISTRIBUTION_ID – the purchase order distribution to which the variance belongs; part of the composite business key.
• COST_GROUP_ID – foreign key to CST_COST_GROUPS, identifying the cost group into which the variance is classified.
• BATCH_ID – foreign key to CST_AP_VARIANCE_BATCHES, linking the header to the specific variance batch run.
• VAR_AMOUNT – the calculated variance amount for the distribution and cost group.
• ORGANIZATION_ID – inventory organization in which the variance is recognized.
• INVENTORY_ITEM_ID – the item associated with the purchase order distribution.
• TRANSACTION_DATE – effective date of the underlying variance transaction.
• Audit columns – CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, plus the concurrent program context REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

Typical reporting reconciles purchase price variances by batch, organization, item, or cost group, and audits specific batch runs for completeness.

• Variance by batch: SELECT b.batch_id, SUM(h.var_amount) FROM cst_ap_variance_headers h JOIN cst_ap_variance_batches b ON h.batch_id = b.batch_id GROUP BY b.batch_id;
• Item-level variance: filter on ORGANIZATION_ID and INVENTORY_ITEM_ID and join CST_AP_VARIANCE_LINES on VARIANCE_HEADER_ID for the line-level detail.
• Cost group analysis: join COST_GROUP_ID to CST_COST_GROUPS to attribute variances to material, overhead, or resource buckets.
• Concurrent request tracing: use REQUEST_ID and PROGRAM_ID to tie a set of headers back to the originating batch program run.

Related Objects

• CST_AP_VARIANCE_BATCHES – parent batch table; join on CST_AP_VARIANCE_HEADERS.BATCH_ID = CST_AP_VARIANCE_BATCHES.BATCH_ID.
• CST_AP_VARIANCE_LINES – child detail table; join on CST_AP_VARIANCE_LINES.VARIANCE_HEADER_ID = CST_AP_VARIANCE_HEADERS.VARIANCE_HEADER_ID.
• CST_COST_GROUPS – referenced by COST_GROUP_ID for variance classification.
• CST_AP_VARIANCE_HEADERS_EFC – EFC/extension table referencing VARIANCE_HEADER_ID.
• CST_AP_VARIANCE_LINES_EFC – line-level EFC table referencing VARIANCE_HEADER_ID.