Search Results intransit_adj_qty_c

Overview

APPS.CST_COST_HISTORY_V is a supplementary Oracle E-Business Suite view owned by the APPS schema and registered in FND Design Data under the BOM product (BOM.CST_COST_HISTORY_V). Its documented status is VALID in both EBS 12.1.1 and 12.2.2. The view presents historical cost update results at the item and organization level, exposing the outcome of each cost update session together with the elemental cost components that comprised the item's standard cost after the update. It is classified by Oracle as a "supplementary view used to simplify forms coding," and Oracle explicitly warns that it is not intended for direct customer querying or data modification because its definition may change dramatically in subsequent minor or major releases.

In practice, the view serves reporting and integration roles: cost accountants use it to review the history of standard cost roll-ups and updates, and integrators extract elemental cost breakdowns—material, material overhead, resource, outside processing, and overhead—for downstream analysis or data warehouse loading. Its functional identity is closely tied to the Cost Update and Inventory valuation flows in Oracle Cost Management.

Underlying Base Objects

The documented referenced objects for the 12.2.2 metadata are:

• CST_COST_UPDATES (synonym) — the cost update session header, supplying update identifiers, update descriptions, dates, and organization context.
• CST_ELEMENTAL_COSTS (synonym) — the elemental cost breakdown, supplying the material, material overhead, resource, outside processing, and overhead component amounts.
• CST_STANDARD_COSTS (synonym) — the frozen standard cost per item, organization, and cost type after the update, exposed as STANDARD_COST.
• FND_DATE (package) — used to convert stored date values into display-ready form, notably for UPDATE_DATE.
• FND_TIMEZONES (package) — used for timezone-aware date presentation.
• MTL_ITEM_FLEXFIELDS (view) — supplies the concatenated, padded item number (PADDED_ITEM_NUMBER) and related flexfield-derived item attributes.
• MTL_PARAMETERS (synonym) — supplies organization-level inventory parameters used in the join logic.

The view therefore aggregates three cost tables joined to item and organization reference data. Adjustments are separated into inventory, intransit, and WIP buckets (quantity and value), each surfaced with the "_C" suffix indicating a converted or computed column.

Key Columns

• COST_UPDATE_ID and COST_UPDATE_ID_JOIN — the cost update session identifier; the latter supports the join used by the underlying form.
• INVENTORY_ITEM_ID, ITEM_DESCRIPTION, PADDED_ITEM_NUMBER, UOM — item identification and units of measure.
• ORGANIZATION_ID — the inventory organization in which the cost applies.
• UPDATE_DATE and UPDATE_DESCRIPTION — when the cost update ran and its description.
• STANDARD_COST — the item's standard cost after the cost update.
• INV_ADJ_VAL_C, INTRANSIT_ADJ_VAL_C, WIP_ADJ_VAL_C — total adjustment values for inventory, intransit, and WIP respectively.
• INV_ADJ_QTY_C, INTRANSIT_ADJ_QTY_C, WIP_ADJ_QTY_C — corresponding total adjustment quantities.
• MATERIAL, MATERIAL_OVERHEAD, RESOURCE_COST, OUTSIDE_PROCESSING, OVERHEAD — the elemental cost components of the updated standard cost. MATERIAL_OVERHEAD is the material overhead burden element, distinct from the general OVERHEAD element.
• Standard WHO columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) and concurrent WHO columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE).

Common Use Cases and Queries

The most common requirement is to retrieve the elemental cost history, including material overhead, for an item across cost update sessions:

• Cost audit and variance review: compare STANDARD_COST and each elemental component between successive UPDATE_DATE values for an item and organization.
• Adjustment analysis: report INV_ADJ_VAL_C, INTRANSIT_ADJ_VAL_C, and WIP_ADJ_VAL_C by cost update to quantify the financial impact of a revaluation.
• Integration extracts: supply elemental cost components to external costing or BI systems.

Sample query:

• SELECT h.organization_id, h.inventory_item_id, h.padded_item_number, h.cost_update_id, h.update_date, h.standard_cost, h.material, h.material_overhead, h.resource_cost, h.outside_processing, h.overhead FROM apps.cst_cost_history_v h WHERE h.inventory_item_id = :item_id AND h.organization_id = :org_id ORDER BY h.update_date DESC;

Because the view is documented as unsupported for direct querying, production code should prefer the underlying documented cost tables where stability is required, using CST_COST_HISTORY_V only as the metadata intended—an internal convenience for forms coding.