CST_TRANSACTION_COSTS
Product: CSTtransactionThe actual cost attached to each costing transaction — one row per transaction, cost element, and expense pool per effective date; a complete cost history including every adjustment
Adjustments rewrite the FULL cost as fresh rows — take the latest EFF_DATE per transaction + element + pool or costs overstate
No item column — join up to the costing transaction spine for the item. COST_SOURCE says where the cost came from (PO, AP…); VALID_COST_FLAG gates use in inventory valuation.
What the badges mean
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.
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.CstTransactionCostsExtractPVOOTBI: Costing - Transaction Cost Real Time
Transaction Costs data store — keyed on TransactionCostId; the complete adjustment history rides along, so dedupe to the latest effective date after landing.
Oracle data-store documentation →
Fields
14 fields · 1 key
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | TRANSACTION_COST_ID | Surrogate key of the cost row | NUMBER | Key |
| 2 | TRANSACTION_ID | The costing transaction — join up for the item; there is no item column here | NUMBER | |
| 3 | COST_ELEMENT_ID | Cost element of this slice | NUMBER | |
| 4 | EXPENSE_POOL_ID | Expense pool of the slice | NUMBER | |
| 5 | COST_ORG_ID | Cost organization | NUMBER | |
| 6 | COST_BOOK_ID | Cost book | NUMBER | |
| 7 | UNIT_COST | Unit cost for this element in the costing currency | NUMBER | |
| 8 | CURRENCY_CODE | Costing currency | VARCHAR2 | |
| 9 | EFF_DATE | When this cost became effective — take the latest per transaction + element + pool | TIMESTAMP | |
| 10 | COST_DATE | Cost date | TIMESTAMP | |
| 11 | COST_SOURCE | Where the cost came from (PO, AP…) | VARCHAR2 | |
| 12 | COSTED_QTY | Quantity costed | NUMBER | |
| 13 | POSTED_FLAG | Whether the cost propagated to the layer/average tables | VARCHAR2 | |
| 14 | VALID_COST_FLAG | Usable for inventory valuation | VARCHAR2 |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading the BICC-landed copy of CST_TRANSACTION_COSTSon 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_TRANSACTION_COSTS — The actual cost attached to each costing transaction — one row per transaction, cost element, and expense pool per effective date; a complete cost history including every adjustment
-- Purpose: Column-selected read of CST_TRANSACTION_COSTS — auto-generated from field metadata
-- Grain : One row per TRANSACTION_COST_ID
-- Caution: Adjustments rewrite the FULL cost as fresh rows — take the latest EFF_DATE per transaction + element + pool or costs overstate
-- 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.TRANSACTION_COST_ID AS "Surrogate key of the cost row",
t.TRANSACTION_ID AS "The costing transaction — join up for the item; there is no item column here",
t.COST_ELEMENT_ID AS "Cost element of this slice",
t.EXPENSE_POOL_ID AS "Expense pool of the slice",
t.COST_ORG_ID AS "Cost organization",
t.COST_BOOK_ID AS "Cost book",
t.UNIT_COST AS "Unit cost for this element in the costing currency",
t.CURRENCY_CODE AS "Costing currency",
t.EFF_DATE AS "When this cost became effective — take the latest per transaction + element + pool",
t.COST_DATE AS "Cost date",
t.COST_SOURCE AS "Where the cost came from (PO, AP…)",
t.COSTED_QTY AS "Quantity costed",
t.POSTED_FLAG AS "Whether the cost propagated to the layer/average tables",
t.VALID_COST_FLAG AS "Usable for inventory valuation"
FROM <catalog>.<schema>.CST_TRANSACTION_COSTS t
WHERE
1 = 1 -- no partition column on this table; the filters below are optional
-- AND t.TRANSACTION_COST_ID = <TRANSACTION_COST_ID>
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- the column incremental BICC extracts key on
ORDER BY t.TRANSACTION_COST_ID;4 parameters not filled: <catalog>, <schema>, <TRANSACTION_COST_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_DISTRIBUTION_LINES.TRANSACTION_COST_ID = CST_TRANSACTION_COSTS.TRANSACTION_COST_IDON CST_TRANSACTION_COSTS.TRANSACTION_ID = CST_TRANSACTIONS.TRANSACTION_IDON CST_TRANSACTION_COSTS.COST_ELEMENT_ID = CST_COST_ELEMENTS_B.COST_ELEMENT_ID