Skip to content
Fusion Reference

CST_STD_COSTS

Product: CSTtransactionDate-effective

Standard cost records — the date-effective standard unit cost per cost org, cost book, and item (optionally per valuation unit), with publish status

Grain note

Date-effective: the current standard is the row whose EFFECTIVE_END_DATE is open — filter the window or costs multiply across revisions

Notes

Org-column trap: INVENTORY_ORG_ID is the item's MASTER org, ORGANIZATION_ID is the manufacturing plant and populated only for rolled-up costs, and neither is the costing scope (that's COST_ORG_ID) — so no automatic org anchor. TOTAL_COST is the header number; the element breakdown lives in a details table (not yet cataloged).

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.

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.CstStdCostDetailsExtractPVO
    OTBI: Costing - Standard Cost Real Time

    Standard Cost Details data store — grain disclosure: the store keys on the element-detail level (StdCostDetailId) one below this header table; roll it up to the header grain after landing.

    Oracle data-store documentation (opens in new tab)

Fields

14 fields · 1 key

14 fields.

Table fields: position, field name, description, data type, and flags. 14 fields.
#FieldDescriptionTypeFlags
1STD_COST_IDSurrogate key of the standard cost recordNUMBER
Key
2COST_ORG_IDCost organization of the standardNUMBER
3COST_BOOK_IDCost book of the standardNUMBER
4INVENTORY_ITEM_IDThe itemNUMBER
5INVENTORY_ORG_IDThe item's MASTER org — not the plant, not the cost orgNUMBER
6ORGANIZATION_IDThe manufacturing plant — populated only for rolled-up costsNUMBER
7VAL_UNIT_IDValuation unit of the standardNUMBER
8TOTAL_COSTTotal standard unit cost over the effective windowNUMBER
9CURRENCY_CODECurrency of the standardVARCHAR2
10UOM_CODECosting UOMVARCHAR2
11EFFECTIVE_START_DATEDate-effective start of the standardDATE
12EFFECTIVE_END_DATEDate-effective end — open means currentDATE
13STATUS_CODEPublish/processing status of the standardVARCHAR2
14COST_TYPESTANDARD or BUYVARCHAR2

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading the BICC-landed copy of CST_STD_COSTS 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

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

-- ============================================================
-- Table  : CST_STD_COSTS — Standard cost records — the date-effective standard unit cost per cost org, cost book, and item (optionally per valuation unit), with publish status
-- Purpose: Column-selected read of CST_STD_COSTS — auto-generated from field metadata
-- Grain  : One row per STD_COST_ID
-- Caution: Date-effective: the current standard is the row whose EFFECTIVE_END_DATE is open — filter the window or costs multiply across revisions
-- 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.STD_COST_ID AS "Surrogate key of the standard cost record",
  t.COST_ORG_ID AS "Cost organization of the standard",
  t.COST_BOOK_ID AS "Cost book of the standard",
  t.INVENTORY_ITEM_ID AS "The item",
  t.INVENTORY_ORG_ID AS "The item's MASTER org — not the plant, not the cost org",
  t.ORGANIZATION_ID AS "The manufacturing plant — populated only for rolled-up costs",
  t.VAL_UNIT_ID AS "Valuation unit of the standard",
  t.TOTAL_COST AS "Total standard unit cost over the effective window",
  t.CURRENCY_CODE AS "Currency of the standard",
  t.UOM_CODE AS "Costing UOM",
  t.EFFECTIVE_START_DATE AS "Date-effective start of the standard",
  t.EFFECTIVE_END_DATE AS "Date-effective end — open means current",
  t.STATUS_CODE AS "Publish/processing status of the standard",
  t.COST_TYPE AS "STANDARD or BUY"
FROM <catalog>.<schema>.CST_STD_COSTS t
WHERE
  CURRENT_DATE BETWEEN t.EFFECTIVE_START_DATE AND t.EFFECTIVE_END_DATE  -- current row of a date-effective table — see quirks guide #date-effective
  -- AND t.STD_COST_ID = <STD_COST_ID>
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- the column incremental BICC extracts key on
ORDER BY t.STD_COST_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_STD_COSTSEGP_SYSTEM_ITEMS_Bforeign key · N:1
    ON CST_STD_COSTS.INVENTORY_ITEM_ID = EGP_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID AND CST_STD_COSTS.INVENTORY_ORG_ID = EGP_SYSTEM_ITEMS_B.ORGANIZATION_ID AND CURRENT_DATE BETWEEN CST_STD_COSTS.EFFECTIVE_START_DATE AND CST_STD_COSTS.EFFECTIVE_END_DATE -- For outer joins, prefilter date-effective inputs (CST_STD_COSTS) in CTEs/subqueries. ON restricts matches but does not remove unmatched historical rows from preserved inputs.
  • CST_STD_COSTSCST_COST_ORG_BOOKSforeign key · N:1
    ON CST_STD_COSTS.COST_ORG_ID = CST_COST_ORG_BOOKS.COST_ORG_ID AND CST_STD_COSTS.COST_BOOK_ID = CST_COST_ORG_BOOKS.COST_BOOK_ID AND CURRENT_DATE BETWEEN CST_STD_COSTS.EFFECTIVE_START_DATE AND CST_STD_COSTS.EFFECTIVE_END_DATE -- For outer joins, prefilter date-effective inputs (CST_STD_COSTS) in CTEs/subqueries. ON restricts matches but does not remove unmatched historical rows from preserved inputs.

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.