Skip to content
EBS Reference

CST_ITEM_COST_DETAILS

Schema: BOMmasterPer inventory org

The 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

Module: BOM & CostingInventory-org partitioned (ORGANIZATION_ID)
Grain note

No unique key — this is a multi-row breakdown; SUM ITEM_COST at your grain and never join it to the cost header expecting one row

Notes

The header's total is the sum of these rows' ITEM_COST contributions for the same item, org, and cost type.

What the badges mean
master
Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
In field listings, K marks a primary-key field.

Fields

15 fields

Table fields: position, field name, description, data type, and flags. 15 fields.
#FieldDescriptionTypeFlags
1INVENTORY_ITEM_IDItem id — part of the working key with org and cost type; no unique key exists on this tableNUMBER
2ORGANIZATION_IDInventory organizationNUMBER
3COST_TYPE_IDThe cost type the breakdown belongs toNUMBER
4COST_ELEMENT_IDWhich of the five cost elements the row contributes toNUMBER
5LEVEL_TYPEThis level vs previous level (rolled up from components)NUMBER
6OPERATION_SEQUENCE_IDThe routing operation behind resource rowsNUMBER
7OPERATION_SEQ_NUMThe operation numberNUMBER
8DEPARTMENT_IDThe department behind resource rowsNUMBER
9RESOURCE_IDThe resource or sub-element chargedNUMBER
10RESOURCE_RATEThe resource rate usedNUMBER
11USAGE_RATE_OR_AMOUNTUsage rate or amount behind the contributionNUMBER
12BASIS_TYPEItem vs lot basisNUMBER
13BASIS_FACTORBasis factor appliedNUMBER
14ITEM_COSTThis row's contribution to the unit cost — SUM at your grainNUMBER
15ROLLUP_SOURCE_TYPEUser-defined, defaulted, or rolled-up rowNUMBER

Field provenance: hand-curated.

Boilerplate SQL

Starting point for reading CST_ITEM_COST_DETAILSon Databricks — real DATE columns need no conversion, and the org anchor and the LAST_UPDATE_DATE watermark are already in place. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.

Query parameters
-- ============================================================
-- Table  : CST_ITEM_COST_DETAILS — The 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
-- Purpose: Column-selected read of CST_ITEM_COST_DETAILS — auto-generated from field metadata
-- Grain  : One row per inventory org (ORGANIZATION_ID) — see the Fields section for the full key
-- Caution: No unique key — this is a multi-row breakdown; SUM ITEM_COST at your grain and never join it to the cost header expecting one row
-- 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.INVENTORY_ITEM_ID AS "Item id — part of the working key with org and cost type; no unique key exists on this table",
  t.ORGANIZATION_ID AS "Inventory organization",
  t.COST_TYPE_ID AS "The cost type the breakdown belongs to",
  t.COST_ELEMENT_ID AS "Which of the five cost elements the row contributes to",
  t.LEVEL_TYPE AS "This level vs previous level (rolled up from components)",
  t.OPERATION_SEQUENCE_ID AS "The routing operation behind resource rows",
  t.OPERATION_SEQ_NUM AS "The operation number",
  t.DEPARTMENT_ID AS "The department behind resource rows",
  t.RESOURCE_ID AS "The resource or sub-element charged",
  t.RESOURCE_RATE AS "The resource rate used",
  t.USAGE_RATE_OR_AMOUNT AS "Usage rate or amount behind the contribution",
  t.BASIS_TYPE AS "Item vs lot basis",
  t.BASIS_FACTOR AS "Basis factor applied",
  t.ITEM_COST AS "This row's contribution to the unit cost — SUM at your grain",
  t.ROLLUP_SOURCE_TYPE AS "User-defined, defaulted, or rolled-up row"
FROM <catalog>.<schema>.CST_ITEM_COST_DETAILS t
WHERE
  t.ORGANIZATION_ID = <inventory_org_id>  -- inventory org, NOT the operating unit — see quirks guide #two-orgs
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
;

4 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <watermark>

Relationships

1-hop neighbors — click a table to navigate there. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.

Join details

  • CST_ITEM_COST_DETAILSCST_ITEM_COSTSforeign key · N:1
    ON CST_ITEM_COST_DETAILS.INVENTORY_ITEM_ID = CST_ITEM_COSTS.INVENTORY_ITEM_ID AND CST_ITEM_COST_DETAILS.ORGANIZATION_ID = CST_ITEM_COSTS.ORGANIZATION_ID AND CST_ITEM_COST_DETAILS.COST_TYPE_ID = CST_ITEM_COSTS.COST_TYPE_ID
  • CST_ITEM_COST_DETAILSBOM_DEPARTMENTSforeign key · N:1
    ON CST_ITEM_COST_DETAILS.DEPARTMENT_ID = BOM_DEPARTMENTS.DEPARTMENT_ID AND CST_ITEM_COST_DETAILS.ORGANIZATION_ID = BOM_DEPARTMENTS.ORGANIZATION_ID
  • CST_ITEM_COST_DETAILSBOM_RESOURCESforeign key · N:1
    ON CST_ITEM_COST_DETAILS.RESOURCE_ID = BOM_RESOURCES.RESOURCE_ID AND CST_ITEM_COST_DETAILS.ORGANIZATION_ID = BOM_RESOURCES.ORGANIZATION_ID
  • CST_ITEM_COST_DETAILSBOM_OPERATION_SEQUENCESforeign key · N:1
    ON CST_ITEM_COST_DETAILS.OPERATION_SEQUENCE_ID = BOM_OPERATION_SEQUENCES.OPERATION_SEQUENCE_ID

Browse more BOM & Costingtables →

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Part of the Summit Analytics reference library.

Work with the practice →

Not affiliated with or endorsed by Oracle. Oracle and Oracle E-Business Suite are registered trademarks of Oracle and/or its affiliates.