Results for “base_invoice_price_variance”

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

Overview

The CST_AP_VARIANCE_LINES_EFC table is an archived Oracle EBS data object owned by the BOM (Bills of Material) schema. Its documented description identifies it as the "Euro as a Functional Currency Archive." It belongs to the BOM product family, which encompasses cost management and material control functionality. The table preserves historical accounts payable variance lines whose original records existed prior to a change in functional currency — specifically a move to the Euro — thereby maintaining audit continuity and reporting integrity after currency conversion events.

From a Data Vault modeling perspective, the mined metadata classifies this object as standalone with no downstream dependents, though it carries a single foreign key relationship upward to CST_AP_VARIANCE_HEADERS. This structure suggests the table functions primarily as a satellite-style archive capturing variance amounts and prices at a point in time, keyed to a parent header. It does not behave as a pure hub, as no independent business key registry is documented.

Key Information Stored

The documented physical schema for ETRM 12.2.2 lists five columns under owner BOM. The most significant are described below:

• VARIANCE_LINE_ID — the surrogate primary key uniquely identifying each variance line record.
• VARIANCE_HEADER_ID — foreign key referencing CST_AP_VARIANCE_LINES_EFC.VARIANCE_HEADER_ID → CST_AP_VARIANCE_HEADERS; groups lines under a common variance event.
• VAR_AMOUNT — the monetary variance amount recorded for the line.
• BASE_INVOICE_PRICE_VARIANCE — the invoice price variance expressed in base currency terms.
• SET_OF_BOOKS_ID — identifies the accounting set of books under which the variance was originally recorded, critical for reconciling archived Euro-transition entries.

Because the schema is sparse, direct business-key attributes beyond these identifiers are not documented. The surrogate key is VARIANCE_LINE_ID, while VARIANCE_HEADER_ID plus line sequencing would be the practical business-key candidate.

Common Use Cases and Queries

This archive table is typically queried during historical cost reconciliation, Euro-transition audits, and period-close variance analysis where legacy functional-currency data must be compared against current records. A representative query joining the archive to its header follows:

• Retrieve all archived lines for a given set of books: SELECT VARIANCE_LINE_ID, VAR_AMOUNT, BASE_INVOICE_PRICE_VARIANCE FROM BOM.CST_AP_VARIANCE_LINES_EFC WHERE SET_OF_BOOKS_ID = :p_sob;
• Join to headers to obtain header context: SELECT h.*, l.VAR_AMOUNT FROM BOM.CST_AP_VARIANCE_HEADERS h, BOM.CST_AP_VARIANCE_LINES_EFC l WHERE h.VARIANCE_HEADER_ID = l.VARIANCE_HEADER_ID;
• Aggregate total archived variance per set of books: SELECT SET_OF_BOOKS_ID, SUM(VAR_AMOUNT) FROM BOM.CST_AP_VARIANCE_LINES_EFC GROUP BY SET_OF_BOOKS_ID;

These patterns support audit reporting, migration validation, and comparative analysis between pre- and post-Euro accounting periods.

Related Objects

The most significant related object is the parent header table referenced by the documented foreign key:

• CST_AP_VARIANCE_HEADERS — joined via VARIANCE_HEADER_ID; the primary dependency.
• CST_AP_VARIANCE_LINES — the analogous current (non-archived) transactional table, useful for pre/post comparison.
• GL_SETS_OF_BOOKS — referenced conceptually through SET_OF_BOOKS_ID to resolve book names.
• CST_AP_VARIANCE_LINES_EFC itself is standalone per the Data Vault classification; no child tables reference it.

The sparse documented relationships reinforce its role as a terminal archive rather than an actively joined transactional entity.