Results for “cst_mtl_item_type”

12 results




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

Overview

APPS.CST_ITEM_OVERHEAD_DEFAULTS_V is a reporting and integration view in the Oracle E-Business Suite Cost Management (CST) module that presents item-level overhead default definitions together with their decoded descriptive values. It is defined in the APPS schema and is available in both Oracle EBS 12.1.1 and 12.2.2, where it is used primarily for inquiry, reporting, and interface extraction of overhead setup data.

The view is especially relevant to users searching on cst_mtl_item_type, because that lookup type drives one of its decoded columns. The underlying base table CST_ITEM_OVERHEAD_DEFAULTS stores the actual overhead assignment rules, but stores the item type and basis type as lookup codes. This view resolves those codes to human-readable meanings by joining to MFG_LOOKUPS, making the output directly suitable for reports and integrations that require meaningful descriptions rather than raw codes.

Underlying Base Objects

The view is defined on four referenced objects, all accessed through APPS synonyms or views:

  • CST_ITEM_OVERHEAD_DEFAULTS — the driving table, aliased CIOD, holding the overhead default rows, including organization, category, item type, activity, basis, and rate/amount values.
  • BOM_RESOURCES — aliased BR, joined on BR.RESOURCE_ID = CIOD.MATERIAL_OVERHEAD_ID (outer join) to bring the material overhead resource code.
  • CST_ACTIVITIES — aliased CA, joined on CA.ACTIVITY_ID = CIOD.ACTIVITY_ID (outer join) to supply the activity name.
  • MFG_LOOKUPS — a view used twice, aliased LU1 for the item type lookup (lookup type 'CST_MTL_ITEM_TYPE') and LU2 for the basis lookup (lookup type 'CST_BASIS'). Both joins are outer joins keyed on LOOKUP_CODE = the respective code column.

Because these are outer joins, rows are returned for all overhead default records even when no matching resource, activity, or lookup meaning exists, which is important when interpreting incomplete setup data.

Key Columns

Common Use Cases and Queries

Typical uses include auditing overhead defaults by organization and category, verifying item type and basis decoding, and extracting setup data for integration or reconciliation. The following example retrieves overhead defaults for a given organization and joins the decoded item type meaning:

  • SELECT organization_id, category_id, resource_code, item_type, item_type_meaning, basis_type, usage_rate_or_amount FROM cst_item_overhead_defaults_v WHERE organization_id = :p_org_id;
  • SELECT resource_code, activity, item_type, basis_type, usage_rate_or_amount FROM cst_item_overhead_defaults_v WHERE item_type = :p_item_type;
  • SELECT category_set_id, category_id, basis_type, COUNT(*) FROM cst_item_overhead_defaults_v GROUP BY category_set_id, category_id, basis_type;

These queries support cost setup validation, category-level overhead analysis, and reporting where decoded values are required in place of lookup codes. The presence of audit columns also makes the view suitable for incremental interface extracts and for reconciling changes to overhead defaults over time.