CST_COST_DISTRIBUTION_LINES
Product: CSTtransactionThe 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
Two account columns: CODE_COMBINATION_ID is the user-entered account, SLA_CODE_COMBINATION_ID the final subledger-derived one — reconcile GL against the SLA column. The element-grain money lives here, not on the header.
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
Header & line
CST_COST_DISTRIBUTION_LINES lines join back to their header CST_COST_DISTRIBUTIONS — and the org column — so a line never fans out.
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.CostDistributionLinesExtractPVOOTBI: Costing - Cost Accounting Real Time
Cost Distribution Lines data store — keyed on DistributionLineId; the debit/credit element-grain amounts.
Oracle data-store documentation (opens in new tab)
Fields
14 fields · 1 key
14 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | DISTRIBUTION_LINE_ID | Surrogate key of the debit/credit line | NUMBER | Key |
| 2 | DISTRIBUTION_ID | Parent distribution header | NUMBER | |
| 3 | LINE_NUMBER | Line number within the distribution | NUMBER | |
| 4 | ACCOUNTING_LINE_TYPE | Accounting line type | VARCHAR2 | |
| 5 | DR_CR_SIGN | Debit or credit indicator | VARCHAR2 | |
| 6 | COST_ELEMENT_ID | The cost element — the element grain lives here, not on the header | NUMBER | |
| 7 | TRANSACTION_COST_ID | The receipt cost row behind the line | NUMBER | |
| 8 | ENTERED_CURRENCY_AMOUNT | Amount in the transaction currency | NUMBER | |
| 9 | ENTERED_CURRENCY_CODE | Transaction currency | VARCHAR2 | |
| 10 | LEDGER_AMOUNT | Amount in the base/ledger currency | NUMBER | |
| 11 | CODE_COMBINATION_ID | User-entered GL account | NUMBER | |
| 12 | SLA_CODE_COMBINATION_ID | Final SLA-derived GL account — reconcile GL against this one | NUMBER | |
| 13 | GL_DATE | Accounting date | DATE | |
| 14 | EVENT_ID | Subledger accounting event | NUMBER |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading the BICC-landed copy of CST_COST_DISTRIBUTION_LINES 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>, <DISTRIBUTION_LINE_ID>, <watermark>
-- ============================================================
-- Table : CST_COST_DISTRIBUTION_LINES — The 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
-- Purpose: Column-selected read of CST_COST_DISTRIBUTION_LINES — auto-generated from field metadata
-- Grain : One row per DISTRIBUTION_LINE_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.DISTRIBUTION_LINE_ID AS "Surrogate key of the debit/credit line",
t.DISTRIBUTION_ID AS "Parent distribution header",
t.LINE_NUMBER AS "Line number within the distribution",
t.ACCOUNTING_LINE_TYPE AS "Accounting line type",
t.DR_CR_SIGN AS "Debit or credit indicator",
t.COST_ELEMENT_ID AS "The cost element — the element grain lives here, not on the header",
t.TRANSACTION_COST_ID AS "The receipt cost row behind the line",
t.ENTERED_CURRENCY_AMOUNT AS "Amount in the transaction currency",
t.ENTERED_CURRENCY_CODE AS "Transaction currency",
t.LEDGER_AMOUNT AS "Amount in the base/ledger currency",
t.CODE_COMBINATION_ID AS "User-entered GL account",
t.SLA_CODE_COMBINATION_ID AS "Final SLA-derived GL account — reconcile GL against this one",
t.GL_DATE AS "Accounting date",
t.EVENT_ID AS "Subledger accounting event"
FROM <catalog>.<schema>.CST_COST_DISTRIBUTION_LINES t
WHERE
1 = 1 -- no automatic partition anchor on this table; the filters below are optional
-- AND t.DISTRIBUTION_LINE_ID = <DISTRIBUTION_LINE_ID>
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- the column incremental BICC extracts key on
ORDER BY t.DISTRIBUTION_LINE_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_DISTRIBUTIONS.DISTRIBUTION_ID = CST_COST_DISTRIBUTION_LINES.DISTRIBUTION_IDON CST_COST_DISTRIBUTION_LINES.COST_ELEMENT_ID = CST_COST_ELEMENTS_B.COST_ELEMENT_IDON CST_COST_DISTRIBUTION_LINES.TRANSACTION_COST_ID = CST_TRANSACTION_COSTS.TRANSACTION_COST_IDON CST_COST_DISTRIBUTION_LINES.CODE_COMBINATION_ID = GL_CODE_COMBINATIONS.CODE_COMBINATION_IDON CST_COST_DISTRIBUTION_LINES.SLA_CODE_COMBINATION_ID = GL_CODE_COMBINATIONS.CODE_COMBINATION_ID
More Cost Management tables
- CST_COST_DISTRIBUTIONSCost distribution headers — one per costed transaction event, carrying the cost org/book, item, event class, GL date, and accounting state ahead of subledger accounting
- CST_COST_ELEMENTS_BThe cost element master — the buckets (material, overhead, and so on) item cost decomposes into, striped by reference data set
- CST_COST_ELEMENTS_TLThe cost element master's translation companion — per-language element descriptions
- CST_COST_INV_ORGSThe 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
- 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