Results for “cst_std_cost_adj_values”

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

Overview

The CST_STD_COST_ADJ_VALUES table, owned by the BOM schema, stores the detailed standard cost adjustment values computed during a standard cost update in Oracle E-Business Suite. Its documented description is precise: a "standard cost adjustment value computed by standard cost update." When a standard cost update program is executed in the Cost Management module, the differences between old and new standard costs must be captured, revalued, and posted to the general ledger. This table holds the granular, line-level detail of those adjustments across inventory, subinventory, and work in process (WIP) contexts, forming the transactional backing for the revaluation and accounting entries produced by the cost update process.

The table operates in the intersection of the Bills of Material/Inventory costing area and Work in Process. It is populated as an outcome of the standard cost update, and its records reference not only the cost update run but also the items, resources, departments, and WIP entities affected by the revaluation. The heuristic Data Vault classification mined from the foreign key structure is link. This is an apt modeling suggestion: the table principally resolves relationships between a cost update event, an organization, a cost element, an inventory item, and a WIP entity, together with their associated from/to organization transfer context. It behaves as an associative (link) construct capturing measured adjustment quantities and cost deltas rather than as a standalone hub of a business entity.

Key Information Stored

The table contains 33 documented columns. The most significant for functional and reporting purposes are the following.

• COST_UPDATE_ID — Identifies the standard cost update run that produced the adjustment; foreign key to CST_COST_UPDATES.
• ORGANIZATION_ID — The inventory organization in which the revaluation applies.
• COST_ELEMENT_ID — The cost element (material, material overhead, resource, overhead, outside processing) affected; foreign key to CST_COST_ELEMENTS.
• INVENTORY_ITEM_ID — The item whose cost is being adjusted.
• OLD_UNIT_COST and NEW_UNIT_COST — The prior and resulting unit costs, whose difference drives the adjustment value.
• ADJUSTMENT_QUANTITY — The quantity to which the cost delta is applied.
• TRANSACTION_TYPE and BASIS_TYPE — Classify the nature and basis of the adjustment.
• LEVEL_TYPE and IN_OUT_FLAG — Indicate the costing level and direction (in/out) of the valuation.
• SUBINVENTORY — The subinventory location, where applicable.
• WIP_ENTITY_ID — The work in process job affected; foreign key to WIP_ENTITIES.
• RESOURCE_ID and DEPARTMENT_ID — The resource and department associated with WIP-related adjustments; foreign keys to BOM_RESOURCES and BOM_DEPARTMENTS.
• FROM_ORGANIZATION_ID and TO_ORGANIZATION_ID — The transfer context for inter-organization adjustments.
• COST_GROUP_ID — The cost group; foreign key to CST_COST_GROUPS.
• INTRANSIT_INV_ACCOUNT — The intransit inventory account used for transfer accounting.

The documented primary key is CST_STD_COST_ADJ_VALUES_PK, comprising the composite of COST_UPDATE_ID, ORGANIZATION_ID, COST_ELEMENT_ID, INVENTORY_ITEM_ID, SUBINVENTORY, WIP_ENTITY_ID, OPERATION_SEQ_NUM, FROM_ORGANIZATION_ID, and TO_ORGANIZATION_ID. This composite serves as the surrogate/technical key rather than a single-column identifier; the constituent columns collectively represent the business-key candidate that uniquely distinguishes each adjustment line. Audit columns (LAST_UPDATE_DATE, CREATED_BY, REQUEST_ID, PROGRAM_ID, and similar) provide concurrency and concurrent-program traceability.

Common Use Cases and Queries

Typical purposes include reconciling the total revaluation produced by a standard cost update, analyzing adjustments by cost element or organization, and deriving the accounting impact of new standard costs on inventory and WIP balances.

A representative query aggregates adjustment value by organization and cost element for a given run:

• SELECT organization_id, cost_element_id, SUM((new_unit_cost - old_unit_cost) * adjustment_quantity) adj_value FROM cst_std_cost_adj_values WHERE cost_update_id = :update_id GROUP BY organization_id, cost_element_id;

Another common pattern joins to CST_COST_ELEMENTS to label elements and to CST_COST_UPDATES to obtain run metadata such as update date and status. Item-level drill-downs join INVENTORY_ITEM_ID to the item master, while WIP-focused queries join WIP_ENTITY_ID to work in process entities to trace job-level revaluation.

Related Objects

The following objects are the most significant dependents and references, based on the documented foreign key relationships.

• CST_COST_UPDATES — joined on COST_UPDATE_ID; parent of the cost update run.
• CST_COST_ELEMENTS — joined on COST_ELEMENT_ID; supplies cost element detail.
• CST_COST_GROUPS — joined on COST_GROUP_ID; groups cost elements for valuation.
• BOM_RESOURCES — joined on RESOURCE_ID; defines resources used in WIP costing.
• BOM_DEPARTMENTS — joined on DEPARTMENT_ID; defines departments for WIP adjustments.
• WIP_ENTITIES — joined on WIP_ENTITY_ID; defines the WIP job affected.
• CST_ITEM_COSTS and the standard cost update concurrent programs in Cost Management — functionally dependent for cost computation and posting.