CST_COST_INV_ORGS
Product: CSTcontrolThe cost-org to inventory-org bridge — which cost organization costs each inventory org, with dated validity; an inventory org belongs to exactly one cost org
The org columns are COST_ORG_ID and INV_ORG_ID (no plain ORGANIZATION_ID). INV_ORG_ID is unique — many inventory orgs per cost org, never the reverse. MASTER_ORGANIZATION_ID carries the inventory org's item-master org.
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.
- 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 withINVENTORY_ITEM_IDon 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_IDon the GL journal tables), or a named business-unit column (PRC_BU_ID/REQ_BU_IDin 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
LANGUAGEcolumn (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to oneLANGUAGEor a join multiplies rows. - Date-effective
- This is an
_Ftable — one row per entity per effectivity window, withEFFECTIVE_START_DATEandEFFECTIVE_END_DATEpart 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.
Structural facts — how the table is partitioned, not a trap by itself
Join & extract hazards — verify before you rely on this
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.CstCostInvOrgsExtractPVO
Cost Organization / Inventory Organization Relationships data store — keyed on CostOrgId + InvOrgId, mirroring the bridge's key.
Oracle data-store documentation (opens in new tab)
Fields
6 fields · 2 key
6 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | COST_ORG_ID | The cost organization | NUMBER | Key |
| 2 | INV_ORG_ID | The inventory organization it costs — unique, so one cost org per inventory org | NUMBER | Key |
| 3 | COST_INV_ORG_ID | Surrogate id of the association row | NUMBER | |
| 4 | MASTER_ORGANIZATION_ID | The inventory org's item-master org | NUMBER | |
| 5 | FROM_DATE | Association validity start | DATE | |
| 6 | TO_DATE | Association validity end | DATE |
Field provenance: hand-curated. 2 key fields.
Boilerplate SQL
Starting point for reading the BICC-landed copy of CST_COST_INV_ORGS 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.
5 parameters not filled: <catalog>, <schema>, <COST_ORG_ID>, <INV_ORG_ID>, <watermark>
-- ============================================================
-- Table : CST_COST_INV_ORGS — The cost-org to inventory-org bridge — which cost organization costs each inventory org, with dated validity; an inventory org belongs to exactly one cost org
-- Purpose: Column-selected read of CST_COST_INV_ORGS — auto-generated from field metadata
-- Grain : One row per COST_ORG_ID + INV_ORG_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_ORG_ID AS "The cost organization",
t.INV_ORG_ID AS "The inventory organization it costs — unique, so one cost org per inventory org",
t.COST_INV_ORG_ID AS "Surrogate id of the association row",
t.MASTER_ORGANIZATION_ID AS "The inventory org's item-master org",
t.FROM_DATE AS "Association validity start",
t.TO_DATE AS "Association validity end"
FROM <catalog>.<schema>.CST_COST_INV_ORGS t
WHERE
1 = 1 -- no automatic partition anchor on this table; the filters below are optional
-- AND t.COST_ORG_ID = <COST_ORG_ID>
-- AND t.INV_ORG_ID = <INV_ORG_ID>
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- the column incremental BICC extracts key on
ORDER BY t.COST_ORG_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
ON CST_COST_INV_ORGS.INV_ORG_ID = INV_ORG_PARAMETERS.ORGANIZATION_IDON CST_COST_INV_ORGS.COST_ORG_ID = CST_COST_ORGS_V.COST_ORG_ID AND CURRENT_DATE BETWEEN CST_COST_ORGS_V.EFFECTIVE_START_DATE AND CST_COST_ORGS_V.EFFECTIVE_END_DATE -- For outer joins, prefilter date-effective inputs (CST_COST_ORGS_V) in CTEs/subqueries. ON restricts matches but does not remove unmatched historical rows from preserved inputs.
More Cost Management tables
- CST_COST_ORG_BOOKSThe cost org + book association — the working grain of Fusion costing, carrying the ledger, currency, calendar, and whether accounting is created for the combination
- CST_COST_ORGS_VThe delivered view that enumerates cost organizations — the costing scope every CST table's COST_ORG_ID resolves to, with code, effectivity, and owning legal entity
- CST_PERPAVG_COSTThe perpetual average cost history — recomputed transaction by transaction per cost org, book, item, valuation unit, and cost element; the latest row is the current average
- CST_STD_COSTSStandard cost records — the date-effective standard unit cost per cost org, cost book, and item (optionally per valuation unit), with publish status
- CST_TRANSACTION_COSTSThe actual cost attached to each costing transaction — one row per transaction, cost element, and expense pool per effective date; a complete cost history including every adjustment
- CST_TRANSACTIONSThe costed-transaction spine — inventory transactions after import into costing, exploded per cost org-book and stamped with cost status; what distributions and cost rows hang off