Skip to content
Fusion Reference

CST_COST_ELEMENTS_B

Product: CSTcontrol

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
master
Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.
In field listings, K marks a primary-key field.

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.

  • FscmTopModelAM.ScmExtractAM.CstBiccExtractAM.CostElementExtractPVO

    Cost Elements data store — keyed on CostElementId. Translated descriptions ride a separate TL store whose full key isn't page-verified.

    Oracle data-store documentation →

Fields

5 fields · 1 key

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-stripedNUMBER
5INV_ORG_IDInventory org identifier — nullable, not a partitionNUMBER

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading the BICC-landed copy of CST_COST_ELEMENTS_Bon 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
-- ============================================================
-- 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
-- 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.COST_ELEMENT_CODE AS "Element code",
  t.COST_ELEMENT_TYPE AS "Element type — material, overhead, and so on",
  t.SET_ID AS "Reference data set — elements are set-striped, not org-striped",
  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
  1 = 1  -- no partition column on this table; the filters below are optional
  -- 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;

5 parameters not filled: <catalog>, <schema>, <language>, <COST_ELEMENT_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_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 Managementtables →

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.