Results for “cst_inv_layer_cost_details”

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

Overview

The CST_INV_LAYER_COST_DETAILS table, owned by the BOM schema, stores the granular cost composition of inventory cost layers maintained by Oracle Cost Management. While the primary CST_INV_LAYER_COSTS table records the aggregate value and quantity of a given inventory layer, this companion table decomposes each layer into its constituent cost elements—material, material overhead, resource, outside processing, overhead, and so on. It is this decomposition that allows Oracle EBS to support period-end revaluation, cost element–level reporting, and inventory valuation reconciliation by element in the subledger and general ledger.

From a Data Vault modeling perspective, the mined relationship structure classifies this object heuristically as standalone, indicating no enforced foreign keys to parent structures within the documented constraint set. In practice, it functions as a satellite-style detail table: it holds descriptive, non-key attribute measures (LAYER_COST) keyed by the combination of a layer, an inventory layer, a cost element, and a level type.

Key Information Stored

The primary key CST_INV_LAYER_COST_DETAILS_PK is composed of four columns: LAYER_ID, INV_LAYER_ID, COST_ELEMENT_ID, and LEVEL_TYPE. A unique index, CST_INV_LAYER_COST_DETAILS_U1, spans the same four columns in a differing order (INV_LAYER_ID, LAYER_ID, COST_ELEMENT_ID, LEVEL_TYPE), and serves as the business-key candidate for the layer-to-element combination.

• LAYER_ID / INV_LAYER_ID — Surrogate identifiers linking the detail record to its parent layer and to the associated inventory layer transaction or valuation context.
• COST_ELEMENT_ID — References the cost element being decomposed (e.g., material, overhead, resource), enabling per-element valuation reporting.
• LEVEL_TYPE — Distinguishes the cost roll-up level (e.g., this-level versus cumulative/level cost), permitting both accumulated and incremental component views.
• LAYER_COST — The monetary amount stored for this element/level combination; the principal measure of the table.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN provide standard EBS who-did-what-and-when tracking.
• Concurrent program columns — REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE identify the cost processor or valuation job that generated the row, which is valuable for traceability and re-run diagnostics.

Common Use Cases and Queries

Cost accountants and technical consultants query this table whenever element-level inventory valuation is required. Typical scenarios include reconciling the inventory subledger to the general ledger by cost element, investigating revaluation or layer build-up differences, and validating period-close cost processor output.

• Element breakdown for a layer:
  SELECT INV_LAYER_ID, COST_ELEMENT_ID, LEVEL_TYPE, SUM(LAYER_COST)
FROM CST_INV_LAYER_COST_DETAILS
WHERE INV_LAYER_ID = :layer_id
GROUP BY INV_LAYER_ID, COST_ELEMENT_ID, LEVEL_TYPE;
• Traceability of a cost run: filter by REQUEST_ID or PROGRAM_ID to identify rows produced by a specific cost processor execution.
• Period reconciliation: aggregate LAYER_COST by COST_ELEMENT_ID across all layers to reconcile element-level balances against the general ledger.

Related Objects

Because the documented relationship data classifies this table as standalone, joins are logical rather than enforced by foreign keys. The most significant related objects are:

• CST_INV_LAYER_COSTS — Parent aggregate layer table; join on the layer identifier (LAYER_ID / INV_LAYER_ID) to compare summarized versus element-level layer cost.
• CST_COST_ELEMENTS — Lookup for COST_ELEMENT_ID, supplying the element name and description.
• CST_INVENTORY_VALUATION / CST_LAYER_COST_HISTORY — Valuation and historical layer tables that consume the same element decomposition.
• MTL_CST_* layer and transaction tables — Transaction-level costing tables whose output feeds layer creation.
• Cost processor concurrent programs — The costing and revaluation programs that populate the PROGRAM_ID / REQUEST_ID audit columns.