Skip to content
Fusion Reference

CST_COST_ELEMENTS_B

Product: CSTcontrolSet-striped (SET_ID)

The cost element master — the buckets (material, overhead, and so on) item cost decomposes into, striped by reference data set

Notes

SET-striped, not org-striped (SET_ID; the nullable INV_ORG_ID is not a partition). Descriptions live on the translation companion.

What the badges mean
Product: EGP
Product: the Oracle product family that owns the object — the short code Oracle's Tables and Views documentation lists as the object owner. Fusion is SaaS, so this isn't a database schema; there's no SQL path to the tables at all (see the quirks guide).
master
Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.

Structural facts — how the table is partitioned, not a trap by itself

BU-striped (ORG_ID)
Rows are scoped to a business unit. The column is still named ORG_ID, but in Fusion it means business unit, not the EBS operating unit — treat any migrated “operating unit” filter as suspect (see the quirks guide).
Per inventory org
Rows are scoped to an inventory organization via ORGANIZATION_ID — always pair it with INVENTORY_ITEM_ID on item-level joins (see the quirks guide).
Set / ledger / named-BU striped
Some tables stripe by a named column instead of ORG_ID: reference data set (SET_ID — see the quirks guide), ledger (LEDGER_ID on the GL journal tables), or a named business-unit column (PRC_BU_ID / REQ_BU_ID in procurement). The table page’s partition line names the column, and the generated SQL anchors on it — never treat these tables as unpartitioned.
Language-striped
The table carries a LANGUAGE column (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to one LANGUAGE or a join multiplies rows.

Join & extract hazards — verify before you rely on this

Date-effective
This is an _F table — one row per entity per effectivity window, with EFFECTIVE_START_DATE and EFFECTIVE_END_DATE part of the key. Join without a window filter and every fact multiplies by history (see the quirks guide).
View
This is a documented convenience view, not a physical table. Extract through the BICC data store that fronts its base objects instead of assuming the view lands as-is.
In field listings, the Key chip marks a key field — a member of the documented primary key or of a documented unique index.

Translations

CST_COST_ELEMENTS_B is the base table for its translations in CST_COST_ELEMENTS_TL — base ↔ translations, one row per LANGUAGE. Filter to one LANGUAGE or rows multiply.

Extract access

The delivered surfaces that reach this table — the BICC extract data store (PVO) for bulk extraction and the OTBI subject areas for real-time queries. There is no SQL path to the SaaS database.

Fields

5 fields · 2 key

5 fields.

Table fields: position, field name, description, data type, and flags. 5 fields.
#FieldDescriptionTypeFlags
1COST_ELEMENT_IDSurrogate key of the cost elementNUMBER
Key
2COST_ELEMENT_CODEElement codeVARCHAR2
3COST_ELEMENT_TYPEElement type — material, overhead, and so onVARCHAR2
4SET_IDReference data set — elements are set-striped, not org-striped; part of the documented unique key (SET_ID + COST_ELEMENT_CODE)NUMBER
Key
5INV_ORG_IDInventory org identifier — nullable, not a partitionNUMBER

Field provenance: hand-curated. 2 key fields.

Boilerplate SQL

Starting point for reading the BICC-landed copy of CST_COST_ELEMENTS_B on Databricks — real DATE columns need no conversion, and the org anchor and the LAST_UPDATE_DATE watermark (the column incremental BICC extracts key on) 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

6 parameters not filled: <catalog>, <schema>, <language>, <SET_ID>, <COST_ELEMENT_ID>, <watermark>

-- ============================================================
-- Table  : CST_COST_ELEMENTS_B — The cost element master — the buckets (material, overhead, and so on) item cost decomposes into, striped by reference data set
-- Purpose: Column-selected read of CST_COST_ELEMENTS_B — auto-generated from field metadata
-- Grain  : One row per COST_ELEMENT_ID + SET_ID
-- Notes  : Auto-generated skeleton for Oracle Fusion Cloud data landed in your lakehouse by a BICC extract — there is no SQL path to the SaaS database. Column names follow Oracle's table documentation — if your landed data still carries PVO attribute headers, map names first; see quirks #pvo-drift. 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_ELEMENT_ID AS "Surrogate key of the cost element",
  t.SET_ID AS "Reference data set — elements are set-striped, not org-striped; part of the documented unique key (SET_ID + COST_ELEMENT_CODE)",
  t.COST_ELEMENT_CODE AS "Element code",
  t.COST_ELEMENT_TYPE AS "Element type — material, overhead, and so on",
  t.INV_ORG_ID AS "Inventory org identifier — nullable, not a partition",
  tl.COST_ELEMENT_DESC AS "Element description"
FROM <catalog>.<schema>.CST_COST_ELEMENTS_B t
LEFT JOIN <catalog>.<schema>.CST_COST_ELEMENTS_TL tl
  ON tl.COST_ELEMENT_ID = t.COST_ELEMENT_ID
 AND tl.LANGUAGE = '<language>'  -- one language or rows multiply
WHERE
  t.SET_ID = <SET_ID>  -- reference data set — the stripe that replaced the org stripe; one set or codes double-load; see quirks guide #set-id
  -- AND t.COST_ELEMENT_ID = <COST_ELEMENT_ID>
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- the column incremental BICC extracts key on
ORDER BY t.COST_ELEMENT_ID;

Verified September 2026 · docs release 26C

Column names differ in BICC extracts — see PVO header drift.

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.

Join details

  • CST_PERPAVG_COSTCST_COST_ELEMENTS_Bforeign key · N:1
    ON CST_PERPAVG_COST.COST_ELEMENT_ID = CST_COST_ELEMENTS_B.COST_ELEMENT_ID
  • CST_COST_ELEMENTS_BCST_COST_ELEMENTS_TLtranslation · 1:N
    ON CST_COST_ELEMENTS_B.COST_ELEMENT_ID = CST_COST_ELEMENTS_TL.COST_ELEMENT_ID AND CST_COST_ELEMENTS_TL.LANGUAGE = '<language>'
  • CST_COST_DISTRIBUTION_LINESCST_COST_ELEMENTS_Bforeign key · N:1
    ON CST_COST_DISTRIBUTION_LINES.COST_ELEMENT_ID = CST_COST_ELEMENTS_B.COST_ELEMENT_ID
  • CST_TRANSACTION_COSTSCST_COST_ELEMENTS_Bforeign key · N:1
    ON CST_TRANSACTION_COSTS.COST_ELEMENT_ID = CST_COST_ELEMENTS_B.COST_ELEMENT_ID

Browse more Cost Management tables

More Cost Management tables

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 Fusion Cloud Applications are registered trademarks of Oracle and/or its affiliates.