Search Results use_up_item_no




Overview
Explore in AI Chat

Overview

APPS.ENG_REVISED_ITEMS_INTERFACE_V is a supplementary Oracle E-Business Suite view owned by the APPS schema and registered under the FND Design Data reference ENG.ENG_REVISED_ITEMS_INTERFACE_V. Its documented status is VALID. Oracle classifies the object as a view of the type used to simplify Oracle Forms coding rather than as a supported reporting interface, and the documentation explicitly warns that querying or altering data through this view is not recommended because its definition may change dramatically in subsequent minor or major releases. The view presents the engineering revised items interface — the staging area through which engineering change order (ECO) revisions to items are validated and processed before they are applied to production engineering and manufacturing data — enriched with lookups, organization-specific item information, and category set information. In practice it supports the ECO entry and mass change forms that let planners and engineers define revised item attributes such as effective dates, MRP activity, WIP update behavior, and use-up processing. Its relationship to the user search term "use_up_item_no" is direct: the view is the presentation layer over which use-up item logic is surfaced during revised item maintenance, though the underlying column is exposed here as USE_UP_ITEM_ID rather than a descriptive use-up item number.

Underlying Base Objects

The view is defined over the following documented base objects: ENG_REVISED_ITEMS_INTERFACE (SYNONYM), FND_COMMON_LOOKUPS (VIEW), FND_GLOBAL (PACKAGE), MTL_CATEGORY_SETS (SYNONYM), and MTL_SYSTEM_ITEMS_VL (VIEW). ENG_REVISED_ITEMS_INTERFACE is the primary source of revised item rows and supplies ROW_ID as the rowid of that table, together with the change notice, sequence identifier, scheduling, and use-up columns. MTL_SYSTEM_ITEMS_VL provides organization-specific item validation and descriptive item information for the revised item and its use-up item, keyed by ORGANIZATION_ID consistent with the multi-org structure of the interface table. MTL_CATEGORY_SETS supplies category set context used by mass change when it generates ECOs. FND_COMMON_LOOKUPS supplies decoded lookup meanings for the various flag and type columns, and FND_GLOBAL supplies session context such as the current user, responsibility, and organization. The join structure is therefore an interface-table root augmented by reference data, which is characteristic of a Forms simplification view.

Key Columns

  • ROW_ID — Rowid of the corresponding ENG_REVISED_ITEMS_INTERFACE row; the view's unique row handle.
  • CHANGE_NOTICE — Engineering change order number the revised item belongs to.
  • ORGANIZATION_ID — Organization identifier for the revised item.
  • REVISED_ITEM_SEQUENCE_ID — Unique identifier of a revised item.
  • SCHEDULED_DATE — Effective date of the revised item.
  • MRP_ACTIVE — Flag indicating whether the revised item is available to MRP.
  • UPDATE_WIP — Flag indicating whether repetitive schedules and unreleased discrete jobs are updated in WIP when the revised item is implemented.
  • USE_UP — Flag indicating whether the use-up date for an item is used as the effective date for the revised item.
  • USE_UP_ITEM_ID — Identifier of the use-up item; this is the column associated with the user's "use_up_item_no" search. Because only the identifier is stored, a descriptive use-up item number must be resolved against MTL_SYSTEM_ITEMS_VL.
  • ALTERNATE_BOM_DESIGNATOR, CATEGORY_SET_ID, STRUCTURE_ID, ITEM_FROM, ITEM_TO, CATEGORY_FROM, CATEGORY_TO — Mass change criteria used to create ECOs, describing alternate BOM designator, category set and structure, and item and category range boundaries.
  • Standard Who columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical scenarios include reviewing staged revised items for a pending ECO before validation, confirming which interface rows carry use-up dates versus explicit scheduled dates, and verifying the mass change ranges that will drive ECO generation. A representative query retrieving staged revised items with their use-up item details is:

  • SELECT v.CHANGE_NOTICE, v.ORGANIZATION_ID, v.REVISED_ITEM_SEQUENCE_ID, v.SCHEDULED_DATE, v.USE_UP, v.USE_UP_ITEM_ID, msi.SEGMENT1 use_up_item_no FROM APPS.ENG_REVISED_ITEMS_INTERFACE_V v, APPS.MTL_SYSTEM_ITEMS_VL msi WHERE msi.INVENTORY_ITEM_ID = v.USE_UP_ITEM_ID AND msi.ORGANIZATION_ID = v.ORGANIZATION_ID AND v.CHANGE_NOTICE = :p_change_notice;
  • SELECT CHANGE_NOTICE, ORGANIZATION_ID, REVISED_ITEM_SEQUENCE_ID, SCHEDULED_DATE FROM APPS.ENG_REVISED_ITEMS_INTERFACE_V WHERE USE_UP = 1 AND ORGANIZATION_ID = :p_org_id;
  • SELECT CHANGE_NOTICE, ALTERNATE_BOM_DESIGNATOR, CATEGORY_SET_ID, CATEGORY_STRUCTURE_ID, ITEM_FROM, ITEM_TO FROM APPS.ENG_REVISED_ITEMS_INTERFACE_V WHERE ITEM_FROM IS NOT NULL;

Because Oracle documents this as a Forms support view whose definition may change without notice, the supported alternative for programmatic integration is to query the base ENG_REVISED_ITEMS_INTERFACE table directly and resolve USE_UP_ITEM_ID against MTL_SYSTEM_ITEMS_VL when a use-up item number is required.