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
master
Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.
In field listings, K marks a primary-key field.

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 →

Fields

14 fields · 1 key

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_LINESon 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
-- ============================================================
-- 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 partition column 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;

4 parameters not filled: <catalog>, <schema>, <DISTRIBUTION_LINE_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

  • 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 Managementtables →

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.