Results for “cst_cost_updates_u1”

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

Overview

BOM.CST_COST_UPDATES is the master control table for the Standard Cost Update process in Oracle E-Business Suite. Each row represents a single Update Standard Cost request submitted through the standard cost update program, capturing the parameters, scope, and financial results of that cost update session. Because standard costing in Oracle Inventory and Work in Process depends on periodic cost rollups and updates, this table serves as the authoritative audit record linking a cost update session to every transactional consequence it produced. The table resides in the APPS_TS_TX_DATA tablespace and is owned by the BOM schema.

In Data Vault modeling terms, the mined foreign-key structure classifies CST_COST_UPDATES as a hub. This is a modeling suggestion: COST_UPDATE_ID functions as the business key around which numerous dependent satellite and link-like tables cluster. The table is therefore best understood as the central anchor for a constellation of cost update artifacts rather than as a transactional detail table.

Key Information Stored

The surrogate primary key is COST_UPDATE_ID (CST_COST_UPDATES_PK), which uniquely identifies each cost update request and is also the leading column of the unique index CST_COST_UPDATES_U1. A second unique index, CST_COST_UPDATES_U2, covers (ORGANIZATION_ID, COST_UPDATE_ID), reflecting that a cost update session is scoped to an inventory organization and serving as a business-key candidate for organization-aware queries.

• COST_UPDATE_ID — Surrogate primary key and the join key to all dependent cost tables.
• ORGANIZATION_ID — The inventory organization whose costs are being updated; the second business-key candidate.
• COST_TYPE_ID — The target cost type (foreign key to CST_COST_TYPES), typically the frozen or standard cost type being revised.
• STATUS — Numeric status of the cost update program, used to distinguish completed from in-progress or failed sessions.
• UPDATE_DATE — Start time of the cost update session, useful for period and timeline reporting.
• RANGE_OPTION, SINGLE_ITEM, ITEM_RANGE_LOW, ITEM_RANGE_HIGH — Define the item scope: all items, a single item, or an item range.
• CATEGORY_ID, CATEGORY_SET_ID — Category-based scope selection, with foreign keys to MTL_CATEGORIES_B and MTL_CATEGORY_SETS_B.
• UPDATE_RESOURCE_OVHD_FLAG, UPDATE_ACTIVITY_FLAG — Control whether resource, overhead, and activity costs are recalculated.
• SNAPSHOT_SAVED_FLAG — Indicates whether adjustment detail was preserved for review.
• INV_ADJUSTMENT_ACCOUNT — The GL code combination for the inventory adjustment, referencing GL_CODE_COMBINATIONS.
• INVENTORY_ADJUSTMENT_VALUE, INTRANSIT_ADJUSTMENT_VALUE, WIP_ADJUSTMENT_VALUE, SCRAP_ADJUSTMENT_VALUE — The financial adjustment totals generated across on-hand inventory, intransit, WIP, and scrap.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID — Concurrent program context for reconciliation with concurrent manager logs.

Note that WIP adjustment values capture standard cost adjustments for items issued and completed from Work in Process; they may not include adjustments for resource or overhead rates.

Common Use Cases and Queries

Cost accountants and technical consultants query this table to audit standard cost update activity, reconcile inventory and WIP valuation adjustments, and trace downstream cost records back to their originating session. A typical lookup by organization and cost type follows these lines:

• Session history: SELECT cost_update_id, status, update_date, description FROM cst_cost_updates WHERE organization_id = :org_id ORDER BY update_date DESC;
• Adjustment reconciliation: Aggregate INVENTORY_ADJUSTMENT_VALUE, WIP_ADJUSTMENT_VALUE, and SCRAP_ADJUSTMENT_VALUE per COST_UPDATE_ID to tie cost updates to the general ledger.
• Traceability: Join COST_UPDATE_ID to CST_ITEM_COSTS or CST_STANDARD_COSTS to identify which item costs resulted from a given update.
• Program monitoring: Use REQUEST_ID to correlate a failed or pending update with the concurrent request and its log output.

Related Objects

CST_COST_UPDATES is heavily referenced. The most significant dependents include:

• CST_ITEM_COSTS and CST_STANDARD_COSTS (which also carries LAST_COST_UPDATE_ID), holding resulting item and standard costs.
• CST_ELEMENTAL_COSTS, providing cost element breakdowns per update.
• CST_STANDARD_COSTS_INTERFACE-related objects including CST_ITEM_COSTS_INTERFACE and CST_ITEM_COSTS_TEMP.
• CST_STD_COST_ADJ_VALUES/_TEMP/_DEBUG, storing computed adjustment values.
• WIP_TRANSACTIONS and WIP_SCRAP_VALUES, linking production activity and scrap to the update.
• MTL_MATERIAL_TRANSACTIONS and MTL_COGS_RECOGNITION_TEMP, connecting inventory movements and COGS recognition.

Parent references include CST_COST_TYPES (COST_TYPE_ID), MTL_CATEGORIES_B (CATEGORY_ID), MTL_CATEGORY_SETS_B (CATEGORY_SET_ID), and GL_CODE_COMBINATIONS (INV_ADJUSTMENT_ACCOUNT). The _EFC suffixed tables indicate the table is included in the E-Business Suite Financials consolidation extracts.