Results for “wip_adj_qty_c”

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

Overview

CST_COST_HISTORY_V is an APPS-owned, VALID database view in Oracle EBS 12.1.1 and 12.2.2, belonging to the BOM — Bills of Material product family and the Cost Management (CST) schema. It exposes elemental item cost and adjustment quantities captured during a standard cost update, delivered as a SINGLE-ORG view. In the standard costing model, a cost update recalculates and freezes item costs for an organization; this view consolidates the resulting header-level standard cost records with their constituent cost elements (material, material overhead, resource, outside processing, and overhead) so that users can report on and reconcile the impact of a cost update item by item.

Because it is a single-organization view, it returns data only for the organization resolved through the costing parameters, making it suitable for organization-specific cost inquiry, audit, and reconciliation rather than cross-org roll-ups. Its primary consumers are cost accountants, inventory valuation analysts, and reporting/integration components that need elemental cost history after a standard cost update.

Underlying Base Objects

The view is defined over the following documented base objects, joined in a single SELECT:

• CST_STANDARD_COSTS (SYNONYM) — aliased twice (CSC and CSC2). CSC provides the item/update/organization driving rows; CSC2 is joined on the costing organization (MTL_PARAMETERS.COST_ORGANIZATION_ID) to supply the corresponding cost-organization record.
• CST_ELEMENTAL_COSTS (SYNONYM) — aliased E, outer-joined to CSC2 on cost update, item, and organization, supplying per-element standard cost amounts.
• CST_COST_UPDATES (SYNONYM) — aliased CCU, outer-joined on cost update and organization, providing the cost update description.
• MTL_PARAMETERS (SYNONYM) — aliased MP, resolving the organization's costing organization and constraining the self-join.
• MTL_ITEM_FLEXFIELDS (VIEW) — aliased MSI, supplying item description, padded item number, and primary UOM.
• FND_DATE and FND_TIMEZONES (PACKAGEs) — used to convert the standard cost revision date into the server/client timezone-adjusted date.

Key Columns

• COST_UPDATE_ID, INVENTORY_ITEM_ID, ORGANIZATION_ID — identification keys linking item, organization, and the specific cost update.
• DESCRIPTION, PADDED_ITEM_NUMBER, PRIMARY_UOM_CODE — item attributes sourced from MTL_ITEM_FLEXFIELDS.
• Elemental standard cost columns — MTL, MTL_OVH, RESC, OP, and OVHD, each derived via SUM(DECODE(E.COST_ELEMENT_ID, …)) over cost elements 1 through 5.
• Adjustment columns — INVENTORY_ADJUSTMENT_VALUE, INTRANSIT_ADJUSTMENT_VALUE, WIP_ADJUSTMENT_VALUE and the corresponding *_ADJUSTMENT_QUANTITY columns, which quantify the value and quantity impact of the update across inventory, intransit, and WIP.
• Aggregates — MAX(CSC.STANDARD_COST), a COUNT(*) of contributing rows, and the timezone-adjusted standard cost revision date.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

Typical scenarios include reviewing the elemental breakdown of a cost update, reconciling adjustment value against adjustment quantity across inventory, intransit, and WIP, and auditing which concurrent request produced a given cost change.

A sample query for the outside processing element for a specific item and organization:

• SELECT inventory_item_id, organization_id, cost_update_id, op AS outside_processing_cost, inventory_adjustment_value, inventory_adjustment_quantity FROM cst_cost_history_v WHERE organization_id = :org_id AND inventory_item_id = :item_id AND cost_update_id = :update_id;

To list all elemental costs for a cost update for reporting:

• SELECT inventory_item_id, description, mtl, mtl_ovh, resc, op, ovhd FROM cst_cost_history_v WHERE cost_update_id = :update_id AND organization_id = :org_id ORDER BY inventory_item_id;

Because the view aggregates on several columns, queries should always constrain by organization and item or cost update to preserve performance and avoid unnecessary full scans of the underlying CST tables.