Search Results cst_default_cost_view




Overview
Explore in AI Chat

Overview

CST_DEFAULT_COST_VIEW is an Oracle E-Business Suite database view owned by the APPS schema and registered under the BOM (Bills of Material) product family. Its documented description is "Default item cost : SINGLE-ORG view." The view resolves the effective default cost record for an inventory item within a single organization, returning the applicable cost type alongside a comprehensive set of cost, level-type, burden, and rollup attributes. It is a convenience layer over the Cost Management item cost tables, allowing callers to query the "defaulted" cost row without having to re-encode the defaulting logic themselves.

The user search term defaulted_flag corresponds to a column exposed by this view (sourced from CST_ITEM_COSTS.DEFAULTED_FLAG). This flag indicates whether the cost rows were established by the cost defaulting mechanism rather than through an explicit user or interface-driven cost entry. Together with the resolved COST_TYPE_ID and the alternate ACTUAL_COST_TYPE_ID, it allows reporting and integration queries to distinguish defaulted costs from deliberately maintained costs.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through synonyms:

  • CST_COST_TYPES (synonym) — aliased as CCT in the view text. Supplies cost type definitions and the DEFAULT_COST_TYPE_ID used by the defaulting rule.
  • CST_ITEM_COSTS (synonym) — aliased as CIC. Supplies item-level cost records across cost types and organizations.

The join relationship is CIC.ORGANIZATION_ID = NVL(CCT.ORGANIZATION_ID, CIC.ORGANIZATION_ID), which lets a global (organization-null) cost type definition apply to item cost rows for any organization. The defaulting predicate is expressed as a disjunction: a row is returned when either (a) CIC.COST_TYPE_ID = CCT.DEFAULT_COST_TYPE_ID and no matching CST_ITEM_COSTS row exists for the item/organization at CCT.COST_TYPE_ID (the NOT EXISTS subquery against CIC2), or (b) CIC.COST_TYPE_ID = CCT.COST_TYPE_ID directly. In effect, the view yields the explicitly maintained cost type row when present, otherwise the default cost type row.

Key Columns

Common Use Cases and Queries

Typical scenarios include cost reporting for an item/organization, verifying which cost type a transaction or valuation will resolve to, and integration programs that need the defaulted cost without re-implementing the defaulting rule.

To retrieve defaulted cost records for a specific item and organization:

  • SELECT inventory_item_id, organization_id, cost_type_id, item_cost, defaulted_flag FROM cst_default_cost_view WHERE organization_id = :org_id AND inventory_item_id = :item_id;

To isolate rows established by defaulting:

  • SELECT cost_type_id, inventory_item_id, organization_id, material_cost, resource_cost, overhead_cost FROM cst_default_cost_view WHERE defaulted_flag = 'Y' AND organization_id = :org_id;

To compare resolved versus actual cost type for diagnostics:

  • SELECT inventory_item_id, organization_id, cost_type_id, actual_cost_type_id, defaulted_flag FROM cst_default_cost_view WHERE cost_type_id <> actual_cost_type_id;

Because the view is documented as SINGLE-ORG, callers should filter or partition by ORGANIZATION_ID to obtain organization-specific costing results.