Results for “cst_layer_cost_details”

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

Overview

The CST_LAYER_COST_DETAILS table is a cost management object owned by the BOM schema in Oracle E-Business Suite (validated across 12.1.1 and 12.2.2). It stores the detailed, element-level cost breakdown of each inventory cost layer produced by the Cost Management (CST) and Bills of Material (BOM) cost rollup processes. While the parent table CST_QUANTITY_LAYERS records the quantity and aggregate value of a valuation layer, CST_LAYER_COST_DETAILS decomposes that layer into its constituent cost elements (material, material overhead, resource, outside processing, overhead, and so on) and, where applicable, the cost level at which each element was accumulated. This decomposition supports period-end valuation, cost element reporting, margin analysis, and reconciliation between subledger and general ledger balances.

From a Data Vault modeling perspective, the metadata suggests classifying this object as a link. The heuristic is derived from its foreign-key structure: the table resolves the association between a quantity layer and the cost elements that compose it, with LAYER_ID and COST_ELEMENT_ID acting as the connecting keys and LEVEL_TYPE qualifying the relationship. It carries its own descriptive and audit attributes (for example ITEM_COST and the standard WHO columns), placing it close to a link carrying descriptive context rather than a pure hub or satellite.

Key Information Stored

The primary key CST_LAYER_COST_DETAILS_PK is a composite surrogate over three columns: LAYER_ID, COST_ELEMENT_ID, and LEVEL_TYPE. A unique index, CST_LAYER_COST_DETAILS_U1, mirrors these same three columns, confirming them as the business-key candidate that enforces one row per layer, element, and level combination.

• LAYER_ID — Foreign key to CST_QUANTITY_LAYERS; identifies the parent valuation layer being detailed.
• COST_ELEMENT_ID — Foreign key to CST_COST_ELEMENTS; identifies which cost element (material, overhead, resource) this detailed amount belongs to.
• LEVEL_TYPE — Qualifies the level at which the element cost was accumulated, distinguishing this row within the composite key.
• ITEM_COST — The detailed element-level cost amount for the given layer, element, and level.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program audit columns identifying the process that created or last updated the row.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns.

Common Use Cases and Queries

Typical scenarios include cost element analysis of inventory layers, subledger-to-GL reconciliation, and detailed valuation reporting. A representative join reconstructs layer-level element detail:

• Reporting cost element composition for a specific layer or item cost run.
• Reconciling detailed element costs back to the aggregate in CST_QUANTITY_LAYERS.
• Analyzing cost by element for margin, absorption, and variance analysis.

A common SQL pattern joins the three keyed tables:

• SELECT d.LAYER_ID, d.COST_ELEMENT_ID, d.LEVEL_TYPE, d.ITEM_COST, e.COST_ELEMENT, ql.ITEM_ID FROM bom.cst_layer_cost_details d, bom.cst_cost_elements e, bom.cst_quantity_layers ql WHERE d.COST_ELEMENT_ID = e.COST_ELEMENT_ID AND d.LAYER_ID = ql.LAYER_ID AND d.LAYER_ID = :p_layer_id;

Related Objects

• CST_QUANTITY_LAYERS — Parent layer table; joined via CST_LAYER_COST_DETAILS.LAYER_ID = CST_QUANTITY_LAYERS.LAYER_ID.
• CST_COST_ELEMENTS — Cost element definition; joined via CST_LAYER_COST_DETAILS.COST_ELEMENT_ID = CST_COST_ELEMENTS.COST_ELEMENT_ID.
• CST_LAYER_COST_DETAILS_PK and CST_LAYER_COST_DETAILS_U1 — Primary and unique indexes enforcing the composite key.
• Cost Management cost rollup and valuation concurrent programs that populate the item cost by request and program identifiers.
• Inquiry and report views in the CST/BOM modules that present element-level layer detail to end users.