Search Results old_unit_cost




Overview
Explore in AI Chat

Overview

APPS.CST_STD_WIP_ADJ_VIEW is a reporting and integration view in the Oracle E-Business Suite Cost Management module. It aggregates the financial impact of standard cost changes on Work in Process (WIP) balances. When a standard cost is updated, existing WIP entities are revalued, and the resulting gain or loss must be isolated by cost element and by adjustment direction. This view performs that isolation by summing the difference between the new and old unit cost, multiplied by the adjustment quantity, across the records held in the standard cost adjustment values table.

The view is a critical data source for the Standard Cost Adjustment reconciliation and for any custom report that needs to explain the revaluation of WIP inventory caused by a cost update. Because it presents one row per cost update, organization, WIP entity, and inventory item, it provides the granularity required for both transactional inquiry and downstream general ledger analysis.

Underlying Base Objects

The only documented referenced base object is CST_STD_COST_ADJ_VALUES, accessed through an APPS synonym. The view reads the adjustment quantity, new unit cost, and old unit cost columns from this table and applies a series of DECODE-based aggregations to them. The base table stores the pre-computed adjustment values generated when a standard cost update is processed, so the view is a transformation layer rather than a stored structure. It does not introduce new persistence; it derives a normalized result set from the raw adjustment values.

Key Columns

The view exposes a compact set of grouping keys alongside the aggregated cost amounts:

The LEVEL_TYPE discriminator distinguishes the cost rollup level, while COST_ELEMENT_ID maps to the standard cost elements such as material, material overhead, resource, outside processing, and overhead. The IN_OUT_FLAG separates upward from downward adjustments, ensuring revaluation gains and losses are not netted together.

Common Use Cases and Queries

Typical usage centers on reconciling WIP revaluation after a cost update and on feeding detailed analysis of the old_unit_cost versus new_unit_cost movement. A representative query selecting the core grouping keys and adjustment amounts is:

  • SELECT COST_UPDATE_ID, ORGANIZATION_ID, WIP_ENTITY_ID, INVENTORY_ITEM_ID FROM APPS.CST_STD_WIP_ADJ_VIEW WHERE COST_UPDATE_ID = :p_update_id;
  • SELECT ORGANIZATION_ID, SUM(column1) ... FROM APPS.CST_STD_WIP_ADJ_VIEW GROUP BY ORGANIZATION_ID; to summarize the revaluation by organization.

Analysts also filter by WIP_ENTITY_ID to trace the effect of a single cost update on an individual job, or restrict the aggregation to specific cost element buckets to explain the composition of the revaluation to the general ledger. Because the old_unit_cost term appears only inside the SUM(DECODE(...)) expressions, any inquiry that needs the raw old and new unit costs should query CST_STD_COST_ADJ_VALUES directly; the view itself returns only the net revaluation amounts per bucket.