Results for “cst_std_cost_adj_temp”

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

Overview

CST_STD_COST_ADJ_TEMP is a temporary staging table owned by the BOM schema in Oracle E-Business Suite 12.1.1 and 12.2.2. As its name and official description indicate, it serves as a transient workspace for standard cost adjustment processing. During standard cost update and cost rollup activities, Oracle Cost Management generates standard cost adjustment entries that must be validated, aggregated, and posted before they are frozen into the permanent cost tables. This table holds those intermediate entries: quantities and values that will ultimately be applied against inventory, WIP, and intransit balances as part of a standard cost change.

In Data Vault modeling terms, the metadata's heuristic classification identifies this object as a link. This is consistent with its structure: the composite primary key draws together references to a cost update, an organization, an inventory item, a subinventory, and a WIP entity — all of which are independent business concepts joined here to represent a specific standard cost adjustment event. Modelers should treat the table primarily as an associative construct rather than a descriptive hub.

Key Information Stored

The documented primary key CST_STD_COST_ADJ_TEMP_PK is a composite surrogate over COST_UPDATE_ID, ORGANIZATION_ID, INVENTORY_ITEM_ID, SUBINVENTORY, and WIP_ENTITY_ID. These five columns form the business-key backbone of the table.

• COST_UPDATE_ID — identifies the parent standard cost update run that generated the adjustment.
• ORGANIZATION_ID — the inventory organization affected by the adjustment.
• INVENTORY_ITEM_ID — the item whose standard cost is being adjusted.
• SUBINVENTORY — the subinventory where the quantity impact applies.
• WIP_ENTITY_ID — the work-in-process entity for adjustments affecting jobs or repetitive schedules.
• TRANSACTION_TYPE and SOURCE_TYPE — categorize the nature of the adjustment source.
• ADJUSTMENT_QUANTITY — the quantity being revalued.
• BASIS_TYPE, APPLIED_RESOURCE_VALUE — define how the adjustment value is derived and its amount.
• DEPARTMENT_ID, RESOURCE_ID, RESOURCE_SEQ_ID, RESOURCE_SEQ_NUM — cost element context for resource-level adjustments.
• FROM_ORGANIZATION_ID, TO_ORGANIZATION_ID, INTRANSIT_INV_ACCOUNT — support intransit inventory transfers.

Common Use Cases and Queries

This table is most often inspected during troubleshooting of standard cost updates, when users question why a particular item or job was revalued. A typical query joins the staging rows to their parents:

• Report all adjustments for a cost update: SELECT * FROM BOM.CST_STD_COST_ADJ_TEMP WHERE COST_UPDATE_ID = :id;
• Aggregate adjustment value by item and organization: SELECT INVENTORY_ITEM_ID, SUM(APPLIED_RESOURCE_VALUE) FROM BOM.CST_STD_COST_ADJ_TEMP GROUP BY INVENTORY_ITEM_ID;
• Trace WIP-related adjustments by joining WIP_ENTITY_ID to WIP_ENTITIES.

Because the table is temporary, its contents are typically transient and should not be relied upon as a permanent audit source; permanent results reside in the cost update postings.

Related Objects

The foreign keys documented in the ETRM metadata anchor this table to its surrounding cost and manufacturing landscape:

• CST_COST_UPDATES — joined on COST_UPDATE_ID; the parent cost update header.
• WIP_ENTITIES — joined on WIP_ENTITY_ID; the affected job or schedule.
• BOM_DEPARTMENTS — joined on DEPARTMENT_ID; the department context.
• BOM_RESOURCES — joined on RESOURCE_ID; the resource context.
• CST_COST_GROUPS — joined on COST_GROUP_ID; the cost group classification.