CST_COST_TYPES
Schema: BOMcontrolThe cost type master — the seeded Frozen, Average, and Pending types plus user-defined types for rollups and simulations, with the fallback pointer rollups use for missing costs
Effectively global: ORGANIZATION_ID is nullable and seeded/shared types carry NULL, so this catalog does not anchor the table on an org. The conventional numeric ids of the seeded types are not Oracle-attested — resolve them from your own instance.
What the badges mean
- Schema: INV
- Schema: the Oracle product schema that owns the table (INV, ONT, WSH, PO, BOM, WIP, MRP, MSC, AR, AP, GL, HR, APPLSYS) — tells you which product family the object belongs to, not who can query it.
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
- OU-striped (ORG_ID)
- Rows are scoped to an operating unit. A landed extract carries every operating unit’s rows — filter or join on
ORG_ID, and don’t confuse it withORGANIZATION_ID(see the quirks guide). - Per inventory org
- Rows are scoped to an inventory organization (plant or warehouse) via
ORGANIZATION_ID— a different partition from OU-striped tables (see the quirks guide). - Language-striped
- The table carries a
LANGUAGEcolumn (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to oneLANGUAGEor a join multiplies rows (see the quirks guide). - View
- This is an APPS-schema convenience view, not a physical table. Extract the base tables it joins instead — views can be slow at scale and aren't guaranteed stable across patches.
Structural facts — how the table is partitioned, not a trap by itself
Join & extract hazards — verify before you rely on this
Fields
10 fields · 1 key
10 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | COST_TYPE_ID | Surrogate key of the cost type | NUMBER | Primary-key field |
| 2 | COST_TYPE | The cost type name — Frozen, Average, Pending, or user-defined | VARCHAR2 | |
| 3 | DESCRIPTION | Cost type description | VARCHAR2 | |
| 4 | COSTING_METHOD_TYPE | Standard vs average method family — numeric, undecoded | NUMBER | |
| 5 | FROZEN_STANDARD_FLAG | Whether this is the frozen standard type | NUMBER | |
| 6 | DEFAULT_COST_TYPE_ID | The fallback cost type rollups read missing costs from | NUMBER | |
| 7 | ORGANIZATION_ID | Nullable — seeded and shared cost types carry NULL, so don't blanket-filter on it | NUMBER | |
| 8 | ALLOW_UPDATES_FLAG | Whether the type's costs may be edited | NUMBER | |
| 9 | COMPONENT_YIELD_FLAG | Whether rollups apply component yield | NUMBER | |
| 10 | DISABLE_DATE | When the type was disabled — NULL while active | DATE |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading CST_COST_TYPES on Databricks — real DATE columns need no conversion, and the org anchor is already in place. The optional LAST_UPDATE_DATE watermark is included. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.
4 parameters not filled: <catalog>, <schema>, <COST_TYPE_ID>, <watermark>
-- ============================================================
-- Table : CST_COST_TYPES — The cost type master — the seeded Frozen, Average, and Pending types plus user-defined types for rollups and simulations, with the fallback pointer rollups use for missing costs
-- Purpose: Column-selected read of CST_COST_TYPES — auto-generated from field metadata
-- Grain : One row per COST_TYPE_ID
-- Notes : Auto-generated skeleton for Oracle EBS R12 data landed in your lakehouse. Dates are real DATE/TIMESTAMP columns — no conversion needed. WHO audit columns omitted (see the quirks guide); the optional LAST_UPDATE_DATE watermark filter supports incremental extracts.
-- ============================================================
SELECT
t.COST_TYPE_ID AS "Surrogate key of the cost type",
t.COST_TYPE AS "The cost type name — Frozen, Average, Pending, or user-defined",
t.DESCRIPTION AS "Cost type description",
t.COSTING_METHOD_TYPE AS "Standard vs average method family — numeric, undecoded",
t.FROZEN_STANDARD_FLAG AS "Whether this is the frozen standard type",
t.DEFAULT_COST_TYPE_ID AS "The fallback cost type rollups read missing costs from",
t.ORGANIZATION_ID AS "Nullable — seeded and shared cost types carry NULL, so don't blanket-filter on it",
t.ALLOW_UPDATES_FLAG AS "Whether the type's costs may be edited",
t.COMPONENT_YIELD_FLAG AS "Whether rollups apply component yield",
t.DISABLE_DATE AS "When the type was disabled — NULL while active"
FROM <catalog>.<schema>.CST_COST_TYPES t
WHERE
1 = 1 -- no partition column on this table; the filters below are optional
-- AND t.COST_TYPE_ID = <COST_TYPE_ID>
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.COST_TYPE_ID;Verified September 2026
Relationships
Diagram of 1-hop neighbors — join details below. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.
Loading relationship diagram…
Join details
ON CST_ITEM_COSTS.COST_TYPE_ID = CST_COST_TYPES.COST_TYPE_ID- CST_COST_TYPESCST_COST_TYPESforeign key · N:1
ON CST_COST_TYPES1.DEFAULT_COST_TYPE_ID = CST_COST_TYPES2.COST_TYPE_ID
More BOM & Costing tables
- CST_ITEM_COST_DETAILSThe cost-element breakdown under each item cost — one row per element, level, and department/operation/resource contribution; where a rolled-up cost's ingredients live
- CST_ITEM_COSTSThe item cost header — one row per item, organization, and cost type, carrying the total unit cost and its five cost-element buckets plus this-level/previous-level splits
- BOM_BILL_OF_MATERIALSThe compatibility view legacy queries know BOM headers by — a window onto the structures table under the familiar 11i name
- BOM_COMPONENTS_BSingle-level bill components — one row per component per operation per effectivity window, with usage quantity, yield, supply type, and the supply subinventory shop-floor issues pull from
- BOM_DEPARTMENTSThe department (work center) master per inventory organization — the places operations happen, with class, location, and the scrap account
- BOM_INVENTORY_COMPONENTSThe compatibility view legacy queries know BOM components by — an APPS-schema access layer over the physical components table