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
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.
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 →
Fields
14 fields · 1 key
| # | 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_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.
-- ============================================================
-- 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
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