CST_COST_ELEMENTS_TL
Product: CSTcontrolLanguage-stripedThe cost element master's translation companion — per-language element descriptions
Filter to one LANGUAGE or element joins multiply; SOURCE_LANG marks the authored row.
What the badges mean
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.
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.
Fields
4 fields · 2 key
| # | 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_TLon 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_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;5 parameters not filled: <catalog>, <schema>, <language>, <COST_ELEMENT_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_ELEMENTS_B.COST_ELEMENT_ID = CST_COST_ELEMENTS_TL.COST_ELEMENT_ID AND CST_COST_ELEMENTS_TL.LANGUAGE = '<language>'