Results for “cst_cost_code_type”

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

Overview

APPS.CST_DETAIL_COST_VIEW is a reporting and integration view in Oracle E-Business Suite that consolidates item cost detail records with their descriptive and contextual attributes. It joins the transactional cost detail table CST_ITEM_COST_DETAILS to lookup meanings, cost elements, activities, resources, departments, and operation sequences, producing a denormalized, human-readable projection of manufacturing and cost rollup information. In both 12.1.1 and 12.2.2, the view is owned by the APPS schema and is exposed through the ETRM (E-Business Suite Technical Reference Manual) as a documented object with a fixed, preformatted view text. Its principal value lies in translating internal numeric identifiers and short codes into meaningful descriptions, which simplifies ad hoc reporting, custom concurrent programs, and downstream integration extract loads without requiring the developer to reproduce the full set of outer joins and lookup translations manually.

Underlying Base Objects

The view is defined over seven referenced base objects, all accessed through APPS synonyms: BOM_DEPARTMENTS, BOM_OPERATION_SEQUENCES, BOM_RESOURCES, CST_ACTIVITIES, CST_COST_ELEMENTS, CST_ITEM_COST_DETAILS, and the MFG_LOOKUPS view. CST_ITEM_COST_DETAILS is the driving table, supplying inventory_item_id, organization_id, cost_type_id, operation_seq_num, resource_rate, usage_rate_or_amount, basis_factor, net_yield_or_shrinkage_factor, item_units, activity_units, item_cost, level_type, and the foreign key columns activity_id, resource_id, department_id, cost_element_id, operation_sequence_id, basis_type, and rollup_source_type. Every one of the supporting joins is an outer join (indicated by the (+) operator), so cost detail rows are preserved even when the corresponding activity, resource, department, operation sequence, cost element, or lookup value is absent. Four separate aliases of MFG_LOOKUPS (ml1 through ml4) resolve lookup meanings for cost element/cost code type (lookup_type CST_COST_CODE_TYPE), level type (CST_LEVEL), basis type (CST_BASIS_SHORT), and rollup source type (CST_SOURCE_TYPE) respectively.

Key Columns

The projection begins with the item/organization/cost-type keys and the meaning of the basis type (ml3.meaning), followed by a cost-element meaning (ml1.meaning) and cost_element_id with its description. It then exposes the level type meaning (ml2.meaning), the activity code and description, the resource code and description, the operation sequence number with its operation_description, and the department code and description. Numeric costing columns include resource_rate, usage_rate_or_amount, basis_factor, net_yield_or_shrinkage_factor, item_units, activity_units, and item_cost. Unit-of-measure columns include ca.output_uom and br.unit_of_measure, alongside the value_added_activity_flag and the rollup source meaning (ml4.meaning). The view also carries the full attribute1 through attribute15 descriptive flexfield columns for both CST_ACTIVITIES and BOM_RESOURCES, and terminates with level_type. Notably, the CST_COST_CODE_TYPE lookup is joined on cicd.cost_element_id, which is why searches for "cst_cost_code_type" surface this view: the ml1 join supplies the meaning associated with that lookup type.

Common Use Cases and Queries

Typical uses include cost rollup diagnostics, where frozen or pending item costs are inspected at the resource and operation level, and integration extracts that require lookup-resolved descriptions rather than raw codes. Because the view spans every organization and cost type, filters on organization_id and cost_type_id are essential for performance and correctness.

• Query cost details for a specific item, organization, and cost type, joining only through the view.
• Reconcile resource rates and usage rates against BOM resources for a given operation sequence.
• Report activity value-added flags and output UOMs for capacity planning analysis.
• Extract cost element and level type meanings for exception and variance reporting.

A representative query is: SELECT inventory_item_id, cost_type_id, cost_element_id, item_cost, resource_rate, operation_seq_num FROM apps.cst_detail_cost_view WHERE organization_id = :org_id AND inventory_item_id = :item_id AND cost_type_id = :cost_type ORDER BY operation_seq_num. Additional filters on meaning columns (for example, cost element meaning or CST_COST_CODE_TYPE-derived codes) are supported directly against the view's projected lookup meanings.