Results for “cst_detail_cost_view”

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

Overview

CST_DETAIL_COST_VIEW is a single-organization reporting view owned by the APPS schema and shipped as part of the Oracle E-Business Suite Bills of Material (BOM) product family. It is defined as a denormalized projection over the cost management and manufacturing foundation tables, and its stated purpose in the ETRM metadata is to provide "detail cost for reports." The view joins item cost detail records to their cost elements, activities, resources, departments, operation sequences, and lookup translations, producing a wide, human-readable row set suitable for cost rollup, bill of material cost analysis, and manufacturing variance reporting.

Because it is a view rather than a table, it carries no independent storage and reflects the current state of the underlying cost and routing data at query time. Its "SINGLE-ORG" designation indicates that rows are scoped by ORGANIZATION_ID and that the caller is expected to filter on a specific inventory organization rather than aggregating across organizations.

Underlying Base Objects

The view is defined over the following documented base objects, accessed through APPS synonyms:

• CST_ITEM_COST_DETAILS — the driving table; supplies item, organization, cost type, resource rate, usage rate or amount, basis factor, net yield or shrinkage factor, item units, activity units, item cost, and level type.
• CST_COST_ELEMENTS — the cost element master, providing the element identifier and description.
• CST_ACTIVITIES — cost activities, providing activity name, output UOM, value-added flag, and descriptive attributes.
• BOM_RESOURCES — resource master, providing resource code, description, unit of measure, and descriptive attributes.
• BOM_DEPARTMENTS — department master, providing department code and description.
• BOM_OPERATION_SEQUENCES — routing operation sequences, providing the operation description.
• MFG_LOOKUPS — a lookup view joined four times (aliases ML1 through ML4) to translate coded values into meanings.

All joins to the dimension objects are outer joins (marked with the (+) operator), so cost detail rows are preserved even when a matching activity, resource, department, operation sequence, cost element, or lookup translation is absent. The BOM_DEPARTMENTS and BOM_RESOURCES joins are further qualified by ORGANIZATION_ID, reinforcing the single-organization scope.

Key Columns

The most significant columns exposed by the view include INVENTORY_ITEM_ID and ORGANIZATION_ID, which identify the item and the inventory organization; COST_TYPE_ID, which identifies the cost type (for example, Frozen, Average, or a user-defined type) under which the detail was recorded; and COST_ELEMENT_ID and its DESCRIPTION, which classify the cost as material, material overhead, resource, outside processing, or overhead.

ML1.MEANING is derived from a lookup of type CST_COST_CODE_TYPE keyed on COST_ELEMENT_ID, making the searched term "cst_cost_code_type" directly relevant to this view. Similarly, ML2.MEANING resolves the lookup type CST_LEVEL against LEVEL_TYPE, and ML3.MEANING resolves the lookup type CST_BASIS_SHORT against BASIS_TYPE. The fourth lookup, ML4, supplies an additional translated meaning carried alongside the cost element. Rate and quantity columns include RESOURCE_RATE, USAGE_RATE_OR_AMOUNT, BASIS_FACTOR, NET_YIELD_OR_SHRINKAGE_FACTOR, ITEM_UNITS, ACTIVITY_UNITS, and ITEM_COST, while ACTIVITY, RESOURCE_CODE, DEPARTMENT_CODE, and OPERATION_SEQ_NUM provide the routing context. Attribute columns 1 through 15 are exposed for both the activity and the resource records.

Common Use Cases and Queries

The view is typically queried to build detailed cost reports, to reconcile item costs against cost elements, and to trace how resource rates and usage rates contribute to an item's unit cost. A typical query filters by organization and cost type:

• SELECT inventory_item_id, cost_element_id, meaning, resource_code, operation_seq_num, item_cost FROM cst_detail_cost_view WHERE organization_id = :org_id AND cost_type_id = :cost_type_id ORDER BY inventory_item_id, operation_seq_num;
• SELECT cost_element_id, meaning, SUM(item_cost) FROM cst_detail_cost_view WHERE organization_id = :org_id GROUP BY cost_element_id, meaning;
• SELECT inventory_item_id, activity, resource_code, usage_rate_or_amount, basis_factor, item_cost FROM cst_detail_cost_view WHERE organization_id = :org_id AND level_type = :level;

Because the "CST_COST_CODE_TYPE" lookup mapping is embedded in the view text, the "meaning" column is the most direct route to reporting on cost code types without re-joining MFG_LOOKUPS manually.