CST_COST_ORGS_V
Product: CSTviewViewThe 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.
What the badges mean
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.
Fields
7 fields · 1 key
| # | 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_Von 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.
-- ============================================================
-- 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
1 = 1 -- no partition column on this table; the filters below are optional
-- 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;4 parameters not filled: <catalog>, <schema>, <COST_ORG_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
ON CST_COST_INV_ORGS.COST_ORG_ID = CST_COST_ORGS_V.COST_ORG_IDON CST_COST_ORGS_V.COST_ORG_ID = HR_ALL_ORGANIZATION_UNITS_F.ORGANIZATION_IDON CST_COST_ORG_BOOKS.COST_ORG_ID = CST_COST_ORGS_V.COST_ORG_ID
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.