Search Results use_up_item_description




Overview
Explore in AI Chat

Overview

The APPS.ENG_REVISED_ITEMS_API_V view exposes pending and implemented engineering revised items within Oracle E-Business Suite Engineering (ENG). It is a reporting and integration access point over the ENG_REVISED_ITEMS entity, joining item master flexfields, manufacturing lookups, and bill of materials data to present a denormalized, human-readable result set. The view carries both the revised item (the new item number produced by a change) and, where applicable, the use-up item (the predecessor item to be consumed before the revision takes effect). This makes it particularly relevant to queries searching on use-up item information, including description attributes.

Because the object is a view rather than a base table, it is read-only and intended for inquiry, extraction, and interface population. It does not itself enforce transaction integrity; all validation is applied by the underlying ENG revised item APIs and base tables.

Underlying Base Objects

The documented base objects referenced by the view are ENG_REVISED_ITEMS (accessed through a synonym), BOM_BILL_OF_MATERIALS (VIEW), MTL_ITEM_FLEXFIELDS (VIEW), and MFG_LOOKUPS (VIEW), with FND_GLOBAL (PACKAGE) also listed as a referenced dependency.

  • ENG_REVISED_ITEMS — the driving entity. It supplies the change notice, organization, revised item identifier, use-up item identifier, status, disposition, implementation and cancellation dates, scheduling dates, and the descriptive flexfield attribute columns.
  • MTL_ITEM_FLEXFIELDS — joined twice, once (MIF1) to resolve the revised item number and description, and once (MIF2) to resolve the use-up item number and description. Both joins are outer joins on organization and inventory item identifiers.
  • BOM_BILL_OF_MATERIALS — an outer join on BILL_SEQUENCE_ID providing the alternate BOM designator and assembly type.
  • MFG_LOOKUPS — joined twice for lookup meaning resolution: ML1 against lookup type ECG_ECN_STATUS for the revised item status, and ML2 against lookup type ECG_MATERIAL_DISPOSITION for the disposition.

Key Columns

Common Use Cases and Queries

A frequent requirement is locating revised items by their use-up item description. The view supports this directly through the outer-joined MIF2 columns.

  • Find revisions whose use-up item description matches a pattern: 
    SELECT change_notice, revised_item, use_up_item, use_up_item_description
FROM   apps.eng_revised_items_api_v
WHERE  use_up_item_description LIKE '%VALVE%';
  • List pending revisions for an organization with decoded status: 
    SELECT revised_item, revised_item_status, disposition,
       implementation_date, scheduled_date
FROM   apps.eng_revised_items_api_v
WHERE  organization_id = :org_id
AND    revised_item_status = 'Pending';
  • Identify impacted use-up items and their plans: 
    SELECT change_notice, use_up_item, use_up_plan_name, new_item_revision
FROM   apps.eng_revised_items_api_v
WHERE  use_up = 'Y';

Because joins to the use-up item and BOM are outer joins, rows without a use-up item return null in the USE_UP_ITEM and USE_UP_ITEM_DESCRIPTION columns; queries filtering on these columns should account for that behavior.