Search Results eng_revised_components_v




Overview
Explore in AI Chat

Overview

ENG_REVISED_COMPONENTS_V is an Oracle EBS Engineering (ENG) module view owned by the APPS schema. It exposes the full set of pending, implemented, and cancelled revised components associated with engineering change orders (ECOs). Rather than presenting a single static component list, the view consolidates the revision lifecycle: components awaiting implementation, those already implemented, and those cancelled, each identifiable through the IMPL_CB flag and associated date columns. This makes it a critical reporting and integration surface for engineering change analysis, where downstream consumers need one queryable object spanning the entire revision continuum.

Within Oracle EBS 12.1.1 and 12.2.2 the view remains valid and is commonly joined by reports, custom concurrent programs, and integrations that require bill of materials (BOM) component detail at a specific revision and ECO context.

Underlying Base Objects

The documented base objects referenced by this view are BOM_BILL_OF_MATERIALS (VIEW), BOM_INVENTORY_COMPONENTS (VIEW), ENG_REVISED_COMPONENTS (SYNONYM), ENG_REVISED_ITEMS (SYNONYM), FND_COMMON_LOOKUPS (VIEW), FND_GLOBAL (PACKAGE), MFG_LOOKUPS (VIEW), and MTL_SYSTEM_ITEMS (SYNONYM).

The primary driver is ENG_REVISED_COMPONENTS, which supplies the revised component records, joined to ENG_REVISED_ITEMS for the revised item context. MTL_SYSTEM_ITEMS enriches each component with item attributes such as BOM_ITEM_TYPE, PRIMARY_UOM_CODE, DESCRIPTION, ENG_ITEM_FLAG, SHIPPABLE_ITEM_FLAG, and locator/subinventory restriction flags. Lookup views (MFG_LOOKUPS and FND_COMMON_LOOKUPS) translate coded values into descriptive meanings. BOM_BILL_OF_MATERIALS and BOM_INVENTORY_COMPONENTS provide the BOM structure linkage, while FND_GLOBAL supplies session context used for multi-org and user-level filtering.

Key Columns

Common Use Cases and Queries

Typical scenarios include ECO impact analysis, identifying components pending implementation versus those already live, and reconciling supply type and supply subinventory defaults across revisions. A search for "supply_type" typically targets the decoded SUPPLY_TYPE meaning alongside WIP_SUPPLY_TYPE.

Example query listing implemented revised components with supply type meaning:

  • SELECT component_sequence_id, component_item_id, change_notice, wip_supply_type, supply_type, supply_subinventory, implementation_date FROM eng_revised_components_v WHERE impl_cb = 2 ORDER BY change_notice, component_sequence_id;
  • Filter by ECO: WHERE change_notice = :eco_number
  • Filter by supply type: WHERE supply_type = 'Push'

Because the view relies on FND_GLOBAL and item master joins, queries should be run in the appropriate operating unit context and joined to MTL_SYSTEM_ITEMS attributes where organization-specific item detail is required.