Search Results cst_ap_variance_headers_efc

Overview

CST_AP_VARIANCE_HEADERS_EFC is an Oracle E-Business Suite archive table residing in the BOM schema and associated with the Bills of Material product family. Its documented description, "Euro as a Functional Currency Archive," identifies its purpose precisely: it belongs to the family of _EFC (Euro Functional Currency) objects created to preserve data extracted during the euro conversion process, when affected implementations migrated their functional currency reporting. The table stores header-level Accounts Payable variance amounts captured against a set of books during that conversion window.

From a Data Vault modeling perspective, the mined relationship data classifies this object heuristically as standalone. This suggests it is best modeled as a satellite or standalone reference structure rather than a hub or link, because its only documented foreign key points inward to the operational parent table rather than outward to independent business entities. In practice, CST_AP_VARIANCE_HEADERS_EFC acts as a historical, read-mostly companion to the live variance header table, and it is rarely referenced by production application logic. Its presence in a 12.1.1 or 12.2.2 environment is typically a legacy artifact retained for audit or reconciliation purposes, and its data volume is generally static.

Key Information Stored

The documented physical schema for 12.2.2 is intentionally narrow, comprising only three columns in the BOM schema. The most significant of these are:

• VARIANCE_HEADER_ID — The surrogate primary key and the join key back to the operational parent, CST_AP_VARIANCE_HEADERS. Each row in the archive preserves the identifier of the corresponding live variance header record.
• VAR_AMOUNT — The variance amount captured for the header. Because the object is a euro functional currency archive, this value reflects the amount as recorded under the converted functional currency context.
• SET_OF_BOOKS_ID — Identifies the set of books (ledger) against which the variance was recorded, providing the accounting context for the archived amount.

No unique business-key indexes separate from the primary key are documented in the available metadata; consequently VARIANCE_HEADER_ID functions as both the surrogate key and the effective business identifier for archive purposes. The composite of VARIANCE_HEADER_ID and SET_OF_BOOKS_ID is the natural grain for reconciliation queries against the parent, since a variance header may be relevant across multiple sets of books in multi-org, multi-ledger configurations. Because only three columns are documented, consumers should assume that descriptive attributes such as variance type, period, or currency code were not duplicated into the archive and must be resolved through the parent table.

Common Use Cases and Queries

Typical usage centers on euro-conversion audit, historical reconciliation, and data-retention reporting rather than day-to-day AP variance processing. A representative join returns archived amounts alongside their live header counterparts:

• Reconciliation of archived versus live variance headers: join CST_AP_VARIANCE_HEADERS_EFC efc to CST_AP_VARIANCE_HEADERS h on efc.VARIANCE_HEADER_ID = h.VARIANCE_HEADER_ID, comparing efc.VAR_AMOUNT to the current header amount to detect conversion discrepancies.
• Ledger-scoped variance reporting: filter by SET_OF_BOOKS_ID to isolate the euro-conversion variance impact for a specific set of books, then aggregate SUM(VAR_AMOUNT) for management or statutory reporting.
• Orphan detection: identify archived rows whose VARIANCE_HEADER_ID no longer exists in the parent table, which commonly occurs after purges or organizational restructuring and is useful for data-cleanup initiatives.
• Retention and audit evidence: extract the complete archive for external auditors or for migration planning when decommissioning legacy euro-conversion artifacts.

Because the table is small and its data is essentially frozen, queries should be tuned simply for the join to the parent rather than for large-scale aggregation.

Related Objects

The most significant related objects, based on the documented foreign-key structure and product context, include:

• CST_AP_VARIANCE_HEADERS — The operational parent table; joined on VARIANCE_HEADER_ID. This is the sole documented foreign-key relationship and the primary source of descriptive variance attributes.
• GL_SETS_OF_BOOKS — Resolves SET_OF_BOOKS_ID to ledger name, currency, and chart of accounts context.
• CST_AP_VARIANCE_LINES — Likely companion line-level variance detail, joinable indirectly through the parent header identifier.
• CST_AP_VARIANCE_HEADERS_EFA / related _EFC objects — Sibling euro-conversion archive artifacts that share the same conversion scope and retention policy.
• AP invoice distribution and CST cost adjustment interfaces — Upstream processes that originally generated AP variance headers now represented in this archive.

Together these objects provide the full lineage from live variance accounting back to the euro-conversion archive maintained in CST_AP_VARIANCE_HEADERS_EFC.