Search Results cstbv_item_std_cst_update_adj




Overview
Explore in AI Chat

Overview

The CSTBV_ITEM_STD_CST_UPDATE_ADJ view is a BOM (Bills of Material) module object residing in the APPS schema with a VALID status. Its description in the ETRM metadata is recorded simply as "Retrofitted," indicating that the view was carried forward or re-implemented as part of a release or patch retrofitting effort rather than documented with a functional description. In Oracle EBS 12.1.1 and 12.2.2, this view serves as a business-intelligence and reporting façade over the standardized cost adjustment values captured during item cost update processing.

Functionally, the view exposes the adjustment-level detail of standard cost update transactions, combining the raw adjustment values with human-readable lookups and resolved foreign key descriptions. This makes it suitable for reporting, data extraction, and integration scenarios where users require denormalized, presentation-ready cost update adjustment data rather than the normalized underlying transaction records.

Underlying Base Objects

The view is defined over the following documented base objects, all accessed via APPS synonyms:

  • CST_STD_COST_ADJ_VALUES — the driving table (aliased CSCAV), supplying all adjustment-level transactional columns.
  • CST_COST_UPDATES — provides the cost update description.
  • CST_COST_ELEMENTS — provides the cost element name.
  • MTL_SYSTEM_ITEMS — the inventory item master, joined for item context.
  • WIP_ENTITIES — supplies the WIP entity name for work-in-process associations.
  • MTL_PARAMETERS — joined three times (MP, MP1, MP2) to resolve organization codes for the organization, from-organization, and to-organization.
  • HR_ALL_ORGANIZATION_UNITS — joined three times (HAOU, HAOU1, HAOU2) to resolve organization names.

The joins on FROM_ORGANIZATION_ID and TO_ORGANIZATION_ID are outer joins, because those columns are nullable, whereas ORGANIZATION_ID is a primary key and not null.

Key Columns

Common Use Cases and Queries

Typical use cases include auditing standard cost update adjustments, reconciling adjustment values against item and organization hierarchies, and feeding downstream reporting or integration extracts.

Example query listing adjustments for an organization:

  • SELECT cost_update_id, inventory_item_id, organization_id, adjustment_quantity, old_unit_cost, new_unit_cost, cost_element FROM cstbv_item_std_cst_update_adj WHERE organization_id = :org_id;

Example query joining to items for descriptive context:

  • SELECT a.inventory_item_id, msi.segment1, a.old_unit_cost, a.new_unit_cost, a.transaction_type FROM cstbv_item_std_cst_update_adj a, mtl_system_items_vl msi WHERE a.inventory_item_id = msi.inventory_item_id;