Skip to content
Fusion Reference

CST_COST_DISTRIBUTION_LINES

Product: CSTtransaction

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

Notes

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.

Structural facts — how the table is partitioned, not a trap by itself

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.

Join & extract hazards — verify before you rely on this

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.
In field listings, the Key chip marks a key field — a member of the documented primary key or of a documented unique index.

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.CostDistributionLinesExtractPVO
    OTBI: 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.

Table fields: position, field name, description, data type, and flags. 14 fields.
#FieldDescriptionTypeFlags
1DISTRIBUTION_LINE_IDSurrogate key of the debit/credit lineNUMBER
Key
2DISTRIBUTION_IDParent distribution headerNUMBER
3LINE_NUMBERLine number within the distributionNUMBER
4ACCOUNTING_LINE_TYPEAccounting line typeVARCHAR2
5DR_CR_SIGNDebit or credit indicatorVARCHAR2
6COST_ELEMENT_IDThe cost element — the element grain lives here, not on the headerNUMBER
7TRANSACTION_COST_IDThe receipt cost row behind the lineNUMBER
8ENTERED_CURRENCY_AMOUNTAmount in the transaction currencyNUMBER
9ENTERED_CURRENCY_CODETransaction currencyVARCHAR2
10LEDGER_AMOUNTAmount in the base/ledger currencyNUMBER
11CODE_COMBINATION_IDUser-entered GL accountNUMBER
12SLA_CODE_COMBINATION_IDFinal SLA-derived GL account — reconcile GL against this oneNUMBER
13GL_DATEAccounting dateDATE
14EVENT_IDSubledger accounting eventNUMBER

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.

Query parameters

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

  • CST_COST_DISTRIBUTIONSCST_COST_DISTRIBUTION_LINESheader line · 1:N
    ON CST_COST_DISTRIBUTIONS.DISTRIBUTION_ID = CST_COST_DISTRIBUTION_LINES.DISTRIBUTION_ID
  • CST_COST_DISTRIBUTION_LINESCST_COST_ELEMENTS_Bforeign key · N:1
    ON CST_COST_DISTRIBUTION_LINES.COST_ELEMENT_ID = CST_COST_ELEMENTS_B.COST_ELEMENT_ID
  • CST_COST_DISTRIBUTION_LINESCST_TRANSACTION_COSTSforeign key · N:1
    ON CST_COST_DISTRIBUTION_LINES.TRANSACTION_COST_ID = CST_TRANSACTION_COSTS.TRANSACTION_COST_ID
  • CST_COST_DISTRIBUTION_LINESGL_CODE_COMBINATIONSforeign key · N:1
    ON CST_COST_DISTRIBUTION_LINES.CODE_COMBINATION_ID = GL_CODE_COMBINATIONS.CODE_COMBINATION_ID
  • CST_COST_DISTRIBUTION_LINESGL_CODE_COMBINATIONSforeign key · N:1
    ON CST_COST_DISTRIBUTION_LINES.SLA_CODE_COMBINATION_ID = GL_CODE_COMBINATIONS.CODE_COMBINATION_ID

Browse more Cost Management tables

More Cost Management tables

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Part of the Summit Analytics reference library.

Work with the practice

Not affiliated with or endorsed by Oracle. Oracle and Oracle Fusion Cloud Applications are registered trademarks of Oracle and/or its affiliates.