Fusion Reference

CST_COST_ELEMENTS_TL

Product: CSTcontrolLanguage-striped

The cost element master's translation companion — per-language element descriptions

Identity

Module: Cost ManagementNot org-partitioned

Notes

Filter to one LANGUAGE or element joins multiply; SOURCE_LANG marks the authored row.

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 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.
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.

Translations

CST_COST_ELEMENTS_TL holds the per-language translation rows for CST_COST_ELEMENTS_B — 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.CostElementTLExtractPVO
Translated Cost Elements data store — documented primary keys CostElementTLPEOLanguage + CostElementTLPEOCostElementId mirror the table's LANGUAGE + COST_ELEMENT_ID key exactly. Snapshot it as a periodic full extract like the other translation stores.
Oracle data-store documentation (opens in new tab)

Fields

4 fields · 2 key

4 fields.

Table fields: position, field name, description, data type, and flags. 4 fields.
#	Field	Description	Type	Flags
1	COST_ELEMENT_ID	The element this translation row belongs to	NUMBER	Key
2	LANGUAGE	Language of this row — filter to one or element joins multiply	VARCHAR2	Key
3	SOURCE_LANG	The language the row was authored in	VARCHAR2
4	COST_ELEMENT_DESC	Element description	VARCHAR2

Field provenance: hand-curated. 2 key fields.

Boilerplate SQL

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

CatalogSchemaLanguage codeCost elementwatermark

Include optional filters (2)

5 parameters not filled: <catalog>, <schema>, <language>, <COST_ELEMENT_ID>, <watermark>

-- ============================================================
-- Table  : CST_COST_ELEMENTS_TL — The cost element master's translation companion — per-language element descriptions
-- Purpose: Column-selected read of CST_COST_ELEMENTS_TL — 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 "The element this translation row belongs to",
  t.LANGUAGE AS "Language of this row — filter to one or element joins multiply",
  t.SOURCE_LANG AS "The language the row was authored in",
  t.COST_ELEMENT_DESC AS "Element description"
FROM <catalog>.<schema>.CST_COST_ELEMENTS_TL t
WHERE
  t.LANGUAGE = '<language>'  -- one language or rows multiply; translations fall back to SOURCE_LANG
  -- 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;

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_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>'

Browse more Cost Management tables