CST_TRANSACTIONS
Product: CSTtransactionThe costed-transaction spine — inventory transactions after import into costing, exploded per cost org-book and stamped with cost status; what distributions and cost rows hang off
Every source transaction appears once per cost org-book combination — filter to the primary book before summing quantities
The link back to inventory runs through costing's own transaction copy (CST_INV_TRANSACTIONS, not yet cataloged) — a direct equality to the inventory ledger's TRANSACTION_ID is NOT documented, so this catalog draws no such edge. COST_STATUS runs new → pending → costed.
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.CstTransactionsExtractPVO
Costing Transactions data store — keyed on TransactionId; the per-org-book exploded spine.
Oracle data-store documentation →
Fields
13 fields · 1 key
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | TRANSACTION_ID | Surrogate key of the costing transaction | NUMBER | Key |
| 2 | COST_ORG_ID | Cost organization | NUMBER | |
| 3 | COST_BOOK_ID | Cost book — the explode-per-book grain | NUMBER | |
| 4 | INVENTORY_ITEM_ID | The item | NUMBER | |
| 5 | INVENTORY_ORG_ID | Inventory org of the source transaction | NUMBER | |
| 6 | COST_TRANSACTION_TYPE | Issue or receipt | VARCHAR2 | |
| 7 | TRANSACTION_DATE | Source transaction date | TIMESTAMP | |
| 8 | COST_DATE | Date costing processed it | TIMESTAMP | |
| 9 | TRANSACTION_QTY | Transacted quantity | NUMBER | |
| 10 | TRANSACTION_UOM_CODE | UOM of the quantity | VARCHAR2 | |
| 11 | COSTED_QTY | Quantity costed so far | NUMBER | |
| 12 | COST_STATUS | New, pending, costed, or error | VARCHAR2 | |
| 13 | CST_INV_TRANSACTION_ID | Costing's own copy of the inventory transaction — the documented chain stops there | NUMBER |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading the BICC-landed copy of CST_TRANSACTIONSon 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_TRANSACTIONS — The costed-transaction spine — inventory transactions after import into costing, exploded per cost org-book and stamped with cost status; what distributions and cost rows hang off
-- Purpose: Column-selected read of CST_TRANSACTIONS — auto-generated from field metadata
-- Grain : One row per TRANSACTION_ID
-- Caution: Every source transaction appears once per cost org-book combination — filter to the primary book before summing quantities
-- 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_ID AS "Surrogate key of the costing transaction",
t.COST_ORG_ID AS "Cost organization",
t.COST_BOOK_ID AS "Cost book — the explode-per-book grain",
t.INVENTORY_ITEM_ID AS "The item",
t.INVENTORY_ORG_ID AS "Inventory org of the source transaction",
t.COST_TRANSACTION_TYPE AS "Issue or receipt",
t.TRANSACTION_DATE AS "Source transaction date",
t.COST_DATE AS "Date costing processed it",
t.TRANSACTION_QTY AS "Transacted quantity",
t.TRANSACTION_UOM_CODE AS "UOM of the quantity",
t.COSTED_QTY AS "Quantity costed so far",
t.COST_STATUS AS "New, pending, costed, or error",
t.CST_INV_TRANSACTION_ID AS "Costing's own copy of the inventory transaction — the documented chain stops there"
FROM <catalog>.<schema>.CST_TRANSACTIONS t
WHERE
1 = 1 -- no partition column on this table; the filters below are optional
-- AND t.TRANSACTION_ID = <TRANSACTION_ID>
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- the column incremental BICC extracts key on
ORDER BY t.TRANSACTION_ID;4 parameters not filled: <catalog>, <schema>, <TRANSACTION_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_PERPAVG_COST.TRANSACTION_ID = CST_TRANSACTIONS.TRANSACTION_IDON CST_COST_DISTRIBUTIONS.TRANSACTION_ID = CST_TRANSACTIONS.TRANSACTION_IDON CST_TRANSACTIONS.INVENTORY_ITEM_ID = EGP_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID AND CST_TRANSACTIONS.INVENTORY_ORG_ID = EGP_SYSTEM_ITEMS_B.ORGANIZATION_IDON CST_TRANSACTION_COSTS.TRANSACTION_ID = CST_TRANSACTIONS.TRANSACTION_ID