Search Results mtl_planning_make_buy




Overview
Explore in AI Chat

Overview

APPS.CST_ITEM_COST_TYPE_V is a cost-management reporting view in Oracle E-Business Suite (validated in 12.1.1 and 12.2.2). It presents item cost records joined to their owning cost types, organization, item descriptive attributes, item category assignment, and the planning make/buy lookup — all in a single flattened result set. The view is owned by the APPS schema and is documented in ETRM 12.2.2. Its role is primarily reporting and integration: cost analysts, planners, and interface developers use it to retrieve, for each inventory item and cost type, the current cost rollup components (material, resource, overhead, outside processing) alongside the cost type's control flags, without having to re-create the multi-table joins themselves.

Because the view includes the MTL_PLANNING_MAKE_BUY lookup, a common search term associated with this object, it is frequently used to correlate item costs with the make/buy planning classification.

Underlying Base Objects

The view is defined over the following documented base objects referenced in the ETRM metadata and the view text:

All joins are inner joins except the item-category and lookup joins, which use Oracle outer-join syntax ((+)).

Key Columns

Common Use Cases and Queries

Typical uses include cost-inquiry reports, frozen-versus-pending cost comparisons, make/buy analysis, and data extraction for downstream costing or planning systems. A representative query filters cost-enabled items in a target organization and cost type:

  • SELECT concatenated_segments, cost_type, item_cost, material_cost, resource_cost, overhead_cost, meaning FROM apps.cst_item_cost_type_v WHERE organization_id = :org_id AND cost_type = 'Frozen' ORDER BY concatenated_segments;
  • Make/buy correlation: SELECT concatenated_segments, cost_type, item_cost, meaning FROM apps.cst_item_cost_type_v WHERE organization_id = :org_id AND meaning = 'Buy';
  • Comparing assigned cost against the cost type's default: join the view's cost_type and the cct2.cost_type-derived default column to flag variances between pending and frozen costs.

Because the view already restricts to costing-enabled items and resolves the make/buy lookup, it is generally preferred over querying CST_ITEM_COSTS directly for ad hoc cost reporting.