CST_COST_BOOKS_B
Product: CSTcontrolThe cost book master — book codes that attach to cost organizations to give multiple parallel cost representations of the same operations
Deliberately thin: names live on the translation companion (not yet cataloged), and everything operational about a book — ledger, currency, calendar — lives on the org-book association.
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.CostBookExtractPVO
Cost Books data store — keyed on CostBookId. In OTBI the cost book is a dimension across the costing subject areas.
Oracle data-store documentation →
Fields
3 fields · 1 key
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | COST_BOOK_ID | Surrogate key of the cost book | NUMBER | Key |
| 2 | COST_BOOK_CODE | Unique book code | VARCHAR2 | |
| 3 | PERIODIC_AVERAGE_FLAG | The book is a periodic-average book | VARCHAR2 |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading the BICC-landed copy of CST_COST_BOOKS_Bon 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_BOOKS_B — The cost book master — book codes that attach to cost organizations to give multiple parallel cost representations of the same operations
-- Purpose: Column-selected read of CST_COST_BOOKS_B — auto-generated from field metadata
-- Grain : One row per COST_BOOK_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.COST_BOOK_ID AS "Surrogate key of the cost book",
t.COST_BOOK_CODE AS "Unique book code",
t.PERIODIC_AVERAGE_FLAG AS "The book is a periodic-average book"
FROM <catalog>.<schema>.CST_COST_BOOKS_B t
WHERE
1 = 1 -- no partition column on this table; the filters below are optional
-- AND t.COST_BOOK_ID = <COST_BOOK_ID>
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- the column incremental BICC extracts key on
ORDER BY t.COST_BOOK_ID;4 parameters not filled: <catalog>, <schema>, <COST_BOOK_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_ORG_BOOKS.COST_BOOK_ID = CST_COST_BOOKS_B.COST_BOOK_ID