Search Results cst_layer_cost_details




Overview
Explore in AI Chat

Overview

The CST_LAYER_COST_DETAILS table is a core transactional data object within the Oracle E-Business Suite Bills of Material (BOM) module, specifically for the Cost Management functionality. It serves as the detailed repository for storing and tracking inventory costs by cost element and level for each quantity layer of an item. Its primary role is to support the perpetual costing methodology, enabling the system to maintain a complete historical cost profile for inventory items. This detailed breakdown is essential for accurate inventory valuation, cost roll-up calculations, and generating precise gross margin analysis on transactions.

Key Information Stored

The table stores a granular decomposition of costs associated with a specific inventory quantity layer. Each record is uniquely identified by the combination of LAYER_ID, COST_ELEMENT_ID, and LEVEL_TYPE, which forms its primary key. The LAYER_ID links the cost detail to a specific quantity layer in the CST_QUANTITY_LAYERS table. The COST_ELEMENT_ID references the CST_COST_ELEMENTS table, classifying the cost as Material, Material Overhead, Resource, Overhead, or Outside Processing. The LEVEL_TYPE indicates whether the cost is incurred at the "Item" level (purchased or finished good) or the "Lot" level (batch-specific costs). Key transactional columns typically include the actual cost amount, potentially broken into various components such as base cost, usage rate, and absorbed amounts, depending on the element type and costing method configuration.

Common Use Cases and Queries

This table is central to cost inquiry and reconciliation processes. A common use case is analyzing the complete cost composition of an item's on-hand inventory by summarizing costs across all its open quantity layers. Financial analysts use this data to validate inventory valuations for month-end closing. Support personnel query it to investigate cost variances or discrepancies in transaction costs. A typical reporting query involves joining to CST_QUANTITY_LAYERS (for item and layer date), CST_COST_ELEMENTS (for element name), and MTL_SYSTEM_ITEMS (for item details).

  • Sample Query Pattern: SELECT clcd.layer_id, clcd.cost_element_id, cce.cost_element, clcd.level_type, clcd.item_cost FROM bom.cst_layer_cost_details clcd JOIN bom.cst_cost_elements cce ON clcd.cost_element_id = cce.cost_element_id WHERE clcd.layer_id IN (SELECT layer_id FROM bom.cst_quantity_layers WHERE inventory_item_id = :p_item_id AND organization_id = :p_org_id);

Related Objects

The CST_LAYER_COST_DETAILS table has defined foreign key relationships with two fundamental costing tables, as per the provided metadata. These relationships are critical for data integrity and query construction.

  • CST_QUANTITY_LAYERS: Foreign key from CST_LAYER_COST_DETAILS.LAYER_ID to CST_QUANTITY_LAYERS.LAYER_ID. This links the cost details to the specific inventory layer, which holds quantity, transaction date, and item information.
  • CST_COST_ELEMENTS: Foreign key from CST_LAYER_COST_DETAILS.COST_ELEMENT_ID to CST_COST_ELEMENTS.COST_ELEMENT_ID. This ensures the cost detail is associated with a valid, predefined cost element.

This table is also a key source for various cost inquiry forms and underlying views within the Cost Management application.