Results for “cst_quantity_layers_v”

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

Overview

CST_QUANTITY_LAYERS_V is an APPS-owned reporting view within the Oracle E-Business Suite cost management schema, delivered under the BOM — Bills of Material product family. Its documented purpose is to present item costs for each cost layer, broken down by cost element and by level. In EBS 12.1.1 and 12.2.2 the view functions as a denormalized pivot of the underlying layer cost detail data, aggregating elemental and total costs for every layer identifier so that downstream reports, inquiries, and integrations do not need to reproduce the cost element pivoting logic themselves.

The view is significant for users searching on cost_element_id because that column is the pivot key around which the entire view is constructed. The view text applies nested DECODE expressions to COST_ELEMENT_ID to route the ITEM_COST value into the correct output column, and the LEVEL_TYPE discriminator to separate this-level costs from prior-level (rolled-up) costs. The result is a fixed, wide column layout that is convenient for tabular reporting but hides the dynamic nature of the underlying elemental detail.

Underlying Base Objects

The view is defined exclusively over CST_LAYER_COST_DETAILS, exposed to APPS as a synonym. All columns returned by the view are derived from that single source object; there are no joins to item master, cost element definitions, or layer header tables within the view definition itself. Consequently, attributes such as item identifiers, cost group, organization, and layer creation dates must be obtained by joining CST_QUANTITY_LAYERS_V back to its parent layer table (CST_QUANTITY_LAYERS) or related inventory and costing entities on LAYER_ID.

Because the source table carries one row per layer, per level type, and per cost element, the view must aggregate. The GROUP BY LAYER_ID clause collapses all detail rows for a layer into a single output row, with each SUM(DECODE(...)) expression isolating a particular element/level combination.

Key Columns

• LAYER_ID — Primary grouping key; identifies the cost layer and provides the join path to layer header and item-level information.
• PL_MATERIAL, PL_MATERIAL_OVERHEAD, PL_RESOURCE, PL_OUTSIDE_PROCESSING, PL_OVERHEAD — Prior-level (LEVEL_TYPE = 1) costs by cost element, corresponding to COST_ELEMENT_ID values 1 through 5.
• TL_MATERIAL, TL_MATERIAL_OVERHEAD, TL_RESOURCE, TL_OUTSIDE_PROCESSING, TL_OVERHEAD — This-level (LEVEL_TYPE = 2) costs by cost element.
• MATERIAL_COST, MATERIAL_OVERHEAD_COST, RESOURCE_COST, OUTSIDE_PROCESSING_COST, OVERHEAD_COST — Element totals summed across both level types.
• PL_ITEM_COST, TL_ITEM_COST, ITEM_COST — Aggregate prior-level, this-level, and overall item cost for the layer.
• UNBURDENED_COST and BURDEN_COST — Derived sums isolating burdened and unburdened portions, with the burden expression treating element 2 (material overhead) specially across levels.

Common Use Cases and Queries

Typical scenarios include elemental cost layer reporting, reconciliation of this-level versus prior-level buildup, and feeds into custom costing dashboards. A standard query retrieves all layer costs:

• SELECT layer_id, item_cost, material_cost, resource_cost, overhead_cost FROM apps.cst_quantity_layers_v WHERE layer_id = :p_layer_id;
• SELECT layer_id, tl_item_cost, pl_item_cost, unburdened_cost, burden_cost FROM apps.cst_quantity_layers_v ORDER BY layer_id;
• SELECT q.layer_id, q.item_cost, l.inventory_item_id, l.organization_id FROM apps.cst_quantity_layers_v q, apps.cst_quantity_layers l WHERE q.layer_id = l.layer_id;

Because COST_ELEMENT_ID is consumed internally by the view and not exposed as an output column, users who need element-level filtering at query time must either select the pre-pivoted columns or query CST_LAYER_COST_DETAILS directly, where cost_element_id remains available as a filterable attribute.