Results for “cst_inv_layer_cost_details_v”

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

Overview

The CST_INV_LAYER_COST_DETAILS_V view is an Oracle Applications (APPS) reporting object that consolidates inventory cost layer detail records into a summarized, cost-element-resolved format. It belongs to the Cost Management (CST) functional area within the Oracle E-Business Suite, and is catalogued under the BOM – Bills of Material product grouping in the ETRM data dictionary. In both release 12.1.1 and 12.2.2 the object retains a VALID status and is owned by the APPS schema.

The view answers a recurring functional question: how much cost resides in each inventory layer, broken down by cost element? Because the underlying CST_INV_LAYER_COST_DETAILS table stores cost detail at a granular level, the view applies a GROUP BY aggregation over SUM(CILCD.LAYER_COST) to present a compact, query-ready result set. This makes it suitable for cost layer reporting, reconciliation of perpetual inventory balances, and downstream integration extracts where layer-level cost composition is required.

Underlying Base Objects

The view is defined over four referenced base objects, all resolved through APPS synonyms:

• CST_INV_LAYER_COST_DETAILS — the primary driver table, aliased CILCD, supplying the layer cost amounts, level type, and cost element identifiers.
• CST_INV_LAYERS — aliased CIL, supplying the inventory item and organization context for each layer.
• CST_COST_ELEMENTS — aliased CCE, resolving the cost element identifier to its functional description.
• MFG_LOOKUPS — aliased LU3, a view used with an outer join ((+)) restricted to lookup type CST_LEVEL, translating the LEVEL_TYPE code into a user-facing MEANING.

Joins are established between CILCD.LAYER_ID and CIL.LAYER_ID, and between the matching INV_LAYER_ID columns of both tables. The cost element join is an inner equi-join on COST_ELEMENT_ID. The lookup join is deliberately outer, ensuring no cost rows are lost when a level type code has no corresponding lookup entry.

Key Columns

• INVENTORY_ITEM_ID — the inventory item associated with the layer.
• ORGANIZATION_ID — the inventory organization owning the layer.
• LAYER_ID — the cost layer identifier.
• INV_LAYER_ID — the inventory layer identifier, jointly qualifying the layer with LAYER_ID.
• LEVEL_TYPE — the cost level classification code (e.g., this level, prior level, or level-cost categories), driven by the CST_LEVEL lookup type.
• MEANING — the decoded, display-ready meaning of LEVEL_TYPE.
• LAYER_COST — the summed cost amount for the grouped layer, level type, and cost element combination.
• COST_ELEMENT — the descriptive name of the cost element (material, material overhead, resource, outside processing, overhead, and similar).
• COST_ELEMENT_ID — the numeric identifier of the cost element, retained in the GROUP BY so distinct elements remain separate rows.

Common Use Cases and Queries

Typical usages include reconciling layer balances for a given item and organization, analysing cost composition by element, and feeding valuation or margin analyses. A general query to retrieve all layers for an item in an organization is:

SELECT organization_id, inventory_item_id, layer_id, inv_layer_id,
       level_type, meaning, cost_element, layer_cost
  FROM apps.cst_inv_layer_cost_details_v
 WHERE inventory_item_id = :p_item_id
    AND organization_id = :p_org_id
 ORDER BY layer_id, cost_element_id;

To aggregate cost by cost element across all layers for an item:

SELECT cost_element, SUM(layer_cost) total_cost
  FROM apps.cst_inv_layer_cost_details_v
 WHERE inventory_item_id = :p_item_id
    AND organization_id = :p_org_id
 GROUP BY cost_element;

Because the view performs aggregation internally, callers should not expect one row per detail record. When the underlying detail granularity is required, query CST_INV_LAYER_COST_DETAILS directly.