Search Results cst_std_cost_adj_temp_pk

Overview

The CST_STD_COST_ADJ_TEMP table is a temporary data store within the Oracle E-Business Suite (EBS) Bills of Material (BOM) module. Its primary role is to serve as a staging area for data during the execution of the Standard Cost Update process. This process is critical for organizations that use standard costing, as it allows for the adjustment of item costs and the revaluation of on-hand inventory and work in process (WIP) balances. The table holds detailed transaction-level records that are processed to calculate the financial impact of cost changes before permanent updates are committed to the general ledger and inventory valuation accounts.

Key Information Stored

The table's structure is designed to capture the granular details necessary for cost adjustment calculations. Its composite primary key (CST_STD_COST_ADJ_TEMP_PK) uniquely identifies each temporary record using a combination of: COST_UPDATE_ID, ORGANIZATION_ID, INVENTORY_ITEM_ID, SUBINVENTORY, and WIP_ENTITY_ID. Key columns include the COST_UPDATE_ID, which links the data to a specific cost update run via the CST_COST_UPDATES table. The ORGANIZATION_ID and INVENTORY_ITEM_ID specify the location and item being revalued. The SUBINVENTORY and WIP_ENTITY_ID columns differentiate between on-hand inventory and work in process. Additional foreign key columns like DEPARTMENT_ID and RESOURCE_ID link to the BOM_DEPARTMENTS and BOM_RESOURCES tables, enabling the adjustment of departmental overhead and resource costs associated with WIP jobs.

Common Use Cases and Queries

The primary use case is the "Standard Cost Update" concurrent program. Data is populated into this table during the program's execution to stage the net change amounts for each affected item and transaction type. Common queries involve analyzing the pending adjustments before final posting. For instance, to review all staged adjustments for a specific cost update run, one might use: SELECT ORGANIZATION_ID, INVENTORY_ITEM_ID, SUBINVENTORY, WIP_ENTITY_ID, NEW_COST, OLD_COST FROM BOM.CST_STD_COST_ADJ_TEMP WHERE COST_UPDATE_ID = :p_update_id ORDER BY ORGANIZATION_ID, INVENTORY_ITEM_ID;. Reporting use cases include validating the scope of the cost update and reconciling the total revaluation impact by subinventory or WIP job before the program completes and clears the temporary data.

Related Objects

CST_STD_COST_ADJ_TEMP has defined foreign key relationships with several core EBS tables, centralizing its role in the cost update workflow. The documented relationships are:

• CST_COST_UPDATES: Linked via CST_STD_COST_ADJ_TEMP.COST_UPDATE_ID. This is the parent table controlling the cost update transaction.
• WIP_ENTITIES: Linked via CST_STD_COST_ADJ_TEMP.WIP_ENTITY_ID. This allows the cost update to identify and revalue specific discrete jobs or repetitive schedules.
• BOM_DEPARTMENTS: Linked via CST_STD_COST_ADJ_TEMP.DEPARTMENT_ID. This associates WIP cost adjustments with the specific manufacturing department.
• BOM_RESOURCES: Linked via CST_STD_COST_ADJ_TEMP.RESOURCE_ID. This associates adjustments with specific manufacturing resources or overheads.

These relationships ensure referential integrity and enable the cost update engine to correctly attribute value changes across the manufacturing and inventory accounting structures.