Results for “single_item”

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

Overview

CST_COST_UPDATES is a cost management table owned by the BOM schema (the schema historically used for Bills of Material and Cost Management objects in Oracle E-Business Suite). Its documented description is cost update history: each row records a single cost update event — the execution of a standard cost update, average cost recalculation, or cost adjustment process — for a given inventory organization and cost type. The table functions as the audit header for cost roll-up and cost update activity, holding the run context (organization, cost type, date, range restrictions, adjustment accounts) that is referenced by the detail tables holding the actual item-level and elemental-level results.

Under the supplied heuristic Data Vault classification, CST_COST_UPDATES is modeled as a hub. This is consistent with its position in the schema: it owns a surrogate primary key and is referenced by numerous downstream detail and interface tables, making it the stable business key anchor around which cost detail satellites are organized. In a Data Vault representation it would serve as the hub of cost update events, with CST_ITEM_COSTS, CST_ELEMENTAL_COSTS, and related tables acting as satellites or dependent links.

Key Information Stored

The table contains 29 documented columns. The most operationally significant are:

• COST_UPDATE_ID — surrogate primary key (CST_COST_UPDATES_PK); also carried as a unique index (CST_COST_UPDATES_U1) and as part of the alternate unique key CST_COST_UPDATES_U2 together with ORGANIZATION_ID.
• ORGANIZATION_ID — inventory organization to which the cost update applies; part of the CST_COST_UPDATES_U2 business-key candidate along with UPDATE_DATE in the documented alternate key.
• COST_TYPE_ID — the cost type being updated (FK to CST_COST_TYPES), i.e. Frozen, Standard, or Average.
• UPDATE_DATE — the effective date of the cost update event; a business-key candidate alongside organization.
• STATUS — processing state of the update (e.g. pending, in process, complete).
• DESCRIPTION — user-facing description of the update.
• RANGE_OPTION, ITEM_RANGE_LOW, ITEM_RANGE_HIGH, SINGLE_ITEM — define the item scope of the update when a range or single item is selected.
• CATEGORY_ID and CATEGORY_SET_ID — category-based scope when the update targets a category (FKs to MTL_CATEGORIES_B and MTL_CATEGORY_SETS_B).
• UPDATE_RESOURCE_OVHD_FLAG and UPDATE_ACTIVITY_FLAG — control whether resource overhead and activity costs are refreshed during the update.
• INV_ADJUSTMENT_ACCOUNT — the general ledger account used for the inventory revaluation adjustment (FK to GL_CODE_COMBINATIONS).
• INVENTORY_ADJUSTMENT_VALUE, INTRANSIT_ADJUSTMENT_VALUE, WIP_ADJUSTMENT_VALUE, SCRAP_ADJUSTMENT_VALUE — the revaluation amounts posted for inventory, intransit, WIP, and scrap balances.
• Standard WHO/audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — plus concurrent request tracking via REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE.

Secondary columns include SNAPSHOT_SAVED_FLAG and LAST_UPDATE_LOGIN. Note that STATUS, REQUEST_ID, and related program columns link the update to its concurrent manager execution.

Common Use Cases and Queries

Typical uses centre on reconciliation, audit trails, and revaluation reporting for cost updates executed through the Cost Management module.

• List recent cost updates for an organization:
• SELECT COST_UPDATE_ID, UPDATE_DATE, STATUS, DESCRIPTION FROM BOM.CST_COST_UPDATES WHERE ORGANIZATION_ID = :org ORDER BY UPDATE_DATE DESC;
• Join to cost types to determine which cost type was updated:
• SELECT cu.COST_UPDATE_ID, ct.COST_TYPE, cu.UPDATE_DATE FROM BOM.CST_COST_UPDATES cu JOIN BOM.CST_COST_TYPES ct ON cu.COST_TYPE_ID = ct.COST_TYPE_ID;
• Revaluation reporting by account and organization, joining to GL_CODE_COMBINATIONS to resolve the adjustment account and summing the four adjustment value columns.
• Reconcile the header to the item-level detail through CST_ITEM_COSTS.COST_UPDATE_ID and CST_ELEMENTAL_COSTS.COST_UPDATE_ID.
• Correlate a cost update to the concurrent request log via REQUEST_ID and PROGRAM_APPLICATION_ID to diagnose failures or long runs.
• Determine scope of an update using RANGE_OPTION, SINGLE_ITEM, and the range columns, or the CATEGORY_ID/CATEGORY_SET_ID pair.

Related Objects

The table is a hub with substantial upstream and downstream linkage:

• CST_COST_TYPES — referenced via COST_TYPE_ID; identifies the cost type updated.
• MTL_CATEGORIES_B and MTL_CATEGORY_SETS_B — referenced via CATEGORY_ID and CATEGORY_SET_ID; scope by category.
• GL_CODE_COMBINATIONS — referenced via INV_ADJUSTMENT_ACCOUNT; revaluation account.
• CST_ITEM_COSTS — child via COST_UPDATE_ID; item-level costs resulting from the update.
• CST_ELEMENTAL_COSTS — child via COST_UPDATE_ID; elemental cost breakdown.
• CST_STANDARD_COSTS — child via COST_UPDATE_ID and LAST_COST_UPDATE_ID; the standard cost set produced.
• CST_ITEM_COSTS_INTERFACE — interface staging that references COST_UPDATE_ID.
• CST_STD_COST_ADJ_VALUES and CST_STD_COST_ADJ_TEMP — standard cost adjustment working and result tables.
• WIP_SCRAP_VALUES — scrap revaluation detail linked by COST_UPDATE_ID.
• Transaction tables MTL_MATERIAL_TRANSACTIONS and WIP_TRANSACTIONS — reference COST_UPDATE_ID to identify which cost update affected a transaction's valuation.

These relationships establish CST_COST_UPDATES as the central audit anchor for cost update and revaluation activity across the Cost Management, Inventory, and WIP modules.