Results for “cst_pm_matl_txns_temp”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

CST_PM_MATL_TXNS_TEMP is a temporary staging table owned by the BOM schema in Oracle E-Business Suite (validated in both 12.1.1 and 12.2.2). As its description states, it is a "Temporary table for use by Cost Collection Manager Concurrent program." Its purpose is to hold material transaction rows that have been extracted from the inventory and Work in Process sub-ledgers so that the Cost Collector can gather costing data, evaluate cost groups, and feed the period-close and cost-rollup process. The table is transient by design: rows are populated and purged within a single concurrent program run, so it should never be treated as a permanent reporting source.

The ETRM heuristic Data Vault classification for this object is standalone. It exhibits no outbound hub-to-link relationship with a conventional corporate master, functioning instead as an operational staging satellite. Treat any hub/link designation as a modeling suggestion rather than an enforced constraint; the physical object is optimized for high-volume inserts and deletes, not for dimensional integrity.

Key Information Stored

The table's 35 documented columns capture the core attributes of each material transaction awaiting cost collection. The most significant include:

• TRANSACTION_ID — surrogate identifier for the staged transaction row; the principal key for DML within the Cost Collector.
• ORGANIZATION_ID — the inventory organization that owns the transaction.
• INVENTORY_ITEM_ID — the item being transacted.
• TRANSACTION_ACTION_ID, TRANSACTION_SOURCE_TYPE_ID, TRANSACTION_SOURCE_ID — classify the movement (issue, receipt, transfer, WIP completion).
• TRANSACTION_DATE, ACCT_PERIOD_ID — the effective date and accounting period to which the cost applies.
• PRIMARY_QUANTITY, PRIMARY_COST_METHOD — the extended quantity and costing method used to derive the value.
• COST_GROUP_ID, TRANSFER_COST_GROUP_ID — FK to CST_COST_GROUPS, linking the row to its costing granularity; the transfer variants support inter-org or inter-group movement.
• PROJECT_ID, TASK_ID, TO_PROJECT_ID, TO_TASK_ID — project and task context for project-manufacturing or project-costing flows.
• TRANSFER_ORGANIZATION_ID, TRANSFER_SUBINVENTORY, SUBINVENTORY_CODE — the source/destination location detail.
• COSTED_FLAG, PM_COST_COLLECTED — status flags indicating whether the row has already been picked up by the collector.
• EXPENDITURE_TYPE, SI_ASSET_YES_NO, INVENTORY_ASSET_FLAG — indicators used to determine capitalized-versus-expensed treatment.

No unique business index is documented outside the FK relationships to MTL_TXN_SOURCE_TYPES and CST_COST_GROUPS; the transactional surrogate is the practical determinant.

Common Use Cases and Queries

Because the table is a staging area, most activity is internal to the Cost Collection Manager. However, support teams frequently query it to diagnose cost rollup and period-close failures. Typical patterns include:

• Identifying rows still pending collection: SELECT * FROM bom.cst_pm_matl_txns_temp WHERE pm_cost_collected = 'N';
• Joining to cost groups to validate costing granularity: ... t.cost_group_id = cg.cost_group_id.
• Grouping uncollected transactions by organization and period to isolate a stuck cost collector run.
• Reviewing the COSTED_FLAG versus PM_COST_COLLECTED divergence to detect partial processing.

These queries are appropriate for troubleshooting only; production reporting should be built on the permanent cost tables populated after collection.

Related Objects

• CST_COST_GROUPS — joined on COST_GROUP_ID; defines costing granularity.
• MTL_TXN_SOURCE_TYPES — joined on TRANSACTION_SOURCE_TYPE_ID; classifies the movement source.
• CST_MTL_TXN_COST_DETAILS — receives the permanent cost detail once collection completes.
• MTL_MATERIAL_TRANSACTIONS — the base transaction table from which rows are staged.
• CST_PERIOD_CLOSE_SUMMARY — period-close aggregate affected by collected costs.

These objects, together with the Cost Collection Manager program itself, form the operational chain that consumes and ultimately persists the temporary rows held in CST_PM_MATL_TXNS_TEMP.