Search Results cst_inv_cost_temp




Overview
Explore in AI Chat

Overview

CST_INV_COST_TEMP is a transient staging table owned by the BOM (Bills of Material) schema in Oracle EBS 12.1.1 and 12.2.2. Its stated purpose is to hold intermediate results produced during period close summarization and during the generation of inventory valuation reports. Rather than persisting a permanent record of item costs, the table acts as a scratchpad: cost management processes populate it, downstream valuation and summarization logic reads from it, and the contents are refreshed or purged on subsequent runs. Because it lives in the BOM schema rather than in CST (Cost Management), DBAs and developers frequently encounter it when troubleshooting cost processor or inventory valuation concurrent programs that report unexpectedly long runtimes, high temporary tablespace consumption, or lock contention.

Under the heuristic Data Vault classification mined from its foreign key structure, the table is modeled as standalone. In Data Vault terms this is best treated as a modeling suggestion only: it carries no parent-child link semantics to other hubs and therefore behaves more like a staging or snapshot structure than a conformed hub, link, or satellite. Its two documented foreign keys — to CST_COST_TYPES and CST_COST_GROUPS — are reference lookups rather than indicators of a link table.

Key Information Stored

The documented physical schema comprises 13 columns in the 12.2.2 ETRM metadata. The most significant are:

The metadata does not document a surrogate primary key or unique index for this object; it is a working table without a defined single-column business key. In practice, uniqueness is implied by the combination of organization, item, cost type, cost group, and source transaction rather than enforced declaratively.

Common Use Cases and Queries

The primary use cases are period close diagnostics, cost rollup verification, and reconciliation between the cost processor output and general ledger inventory balances. A typical investigative query filters by organization and cost type:

  • SELECT organization_id, inventory_item_id, cost_type_id, cost_group_id, item_cost FROM bom.cst_inv_cost_temp WHERE organization_id = :org AND cost_type_id = :ctype;
  • Joining to CST_COST_TYPES to resolve cost method names for reporting.
  • Comparing element-level sums (material, resource, overhead) against ITEM_COST to detect incomplete rollups before period close.
  • Identifying receipt-driven rows through RCV_TRANSACTION_ID to trace valuation back to receiving.

Because contents are transient, reports should be run immediately after the populating concurrent program completes and before the next run clears the table.

Related Objects

The most significant related objects are the two documented foreign key targets plus the surrounding cost and inventory tables:

  • CST_COST_TYPES — joined on COST_TYPE_ID.
  • CST_COST_GROUPS — joined on COST_GROUP_ID.
  • MTL_SYSTEM_ITEMS_B — item master, joined on INVENTORY_ITEM_ID and ORGANIZATION_ID.
  • MTL_PARAMETERS — organization definition, joined on ORGANIZATION_ID.
  • CST_ITEM_COSTS — the permanent item cost table that valuation reports ultimately compare against.
  • CST_TRANSACTIONS / MTL_MATERIAL_TRANSACTIONS — source transaction detail reconciled through RCV_TRANSACTION_ID.
  • ORG_ORGANIZATION_DEFINITIONS — organization context for reporting joins.
  • Cost Management period close concurrent programs — the processes that populate and consume this table.