CST_COST_ORGS_V
Product: CSTviewDate-effectiveViewThe 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
A Fusion cost organization has NO base table — it is an HR organization unit carrying the CST classification, and this view filters the HR org tables to those rows. COST_ORG_ID IS an HR ORGANIZATION_ID; names come from here or the HR org master. The classification rows are date-effective (EFFECTIVE_START/END_DATE), so the generated SQL pins the current window. No PVO fronts this view itself — the delivered BICC store for the cost-org layer is CostOrgParametersExtractPVO (Cost Organization Parameters, keyed on a mirror of COST_ORG_ID) in the 26B SCM extract book; land that store, or the HR org base data, rather than expecting the view.
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
Fields
7 fields · 1 key
7 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | COST_ORG_ID | The cost organization's id — literally an HR organization id carrying the CST classification | NUMBER | Key |
| 2 | COST_ORG_NAME | Cost organization name | VARCHAR2 | |
| 3 | COST_ORG_CODE | Cost organization code | VARCHAR2 | |
| 4 | EFFECTIVE_START_DATE | Classification effectivity start | DATE | |
| 5 | EFFECTIVE_END_DATE | Classification effectivity end | DATE | |
| 6 | STATUS | Classification status — the view filters to active | VARCHAR2 | |
| 7 | LEGAL_ENTITY_ID | Owning legal entity | NUMBER |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading the BICC-landed copy of CST_COST_ORGS_V 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.
4 parameters not filled: <catalog>, <schema>, <COST_ORG_ID>, <watermark>
-- ============================================================
-- Table : CST_COST_ORGS_V — The 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
-- Purpose: Column-selected read of CST_COST_ORGS_V — auto-generated from field metadata
-- Grain : One row per COST_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. Documented view — land its base tables for extraction; see the table notes.
-- ============================================================
SELECT
t.COST_ORG_ID AS "The cost organization's id — literally an HR organization id carrying the CST classification",
t.COST_ORG_NAME AS "Cost organization name",
t.COST_ORG_CODE AS "Cost organization code",
t.EFFECTIVE_START_DATE AS "Classification effectivity start",
t.EFFECTIVE_END_DATE AS "Classification effectivity end",
t.STATUS AS "Classification status — the view filters to active",
t.LEGAL_ENTITY_ID AS "Owning legal entity"
FROM <catalog>.<schema>.CST_COST_ORGS_V 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.COST_ORG_ID = <COST_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.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.ON CST_COST_ORGS_V.COST_ORG_ID = HR_ALL_ORGANIZATION_UNITS_F.ORGANIZATION_ID AND CURRENT_DATE BETWEEN CST_COST_ORGS_V.EFFECTIVE_START_DATE AND CST_COST_ORGS_V.EFFECTIVE_END_DATE AND CURRENT_DATE BETWEEN HR_ALL_ORGANIZATION_UNITS_F.EFFECTIVE_START_DATE AND HR_ALL_ORGANIZATION_UNITS_F.EFFECTIVE_END_DATE -- For outer joins, prefilter date-effective inputs (CST_COST_ORGS_V, HR_ALL_ORGANIZATION_UNITS_F) in CTEs/subqueries. ON restricts matches but does not remove unmatched historical rows from preserved inputs.ON CST_COST_ORG_BOOKS.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.
CST_COST_ORGS_V is a documented convenience view. Extract through the BICC data store that fronts its base objects instead of assuming the view lands as-is — see the table notes for where the physical rows live.
More Cost Management tables
- 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
- CST_COST_BOOKS_BThe cost book master — book codes that attach to cost organizations to give multiple parallel cost representations of the same operations
- CST_COST_DISTRIBUTION_LINESThe debit and credit lines under each cost distribution — per cost element, with entered and ledger amounts and both the user-entered and final SLA-derived GL accounts