Search Results base_description

Overview

APPS.ENG_REVISED_ITEMS_INTERFACE_V is a reporting and integration view in the Oracle E-Business Suite Engineering (ENG) module. It exposes the contents of the mass change revised items interface table, ENG_REVISED_ITEMS_INTERFACE, joined to descriptive master data so that rows can be interpreted without additional lookups. In EBS 12.1.1 and 12.2.2 the view is owned by APPS and is reported as VALID in the ETRM repository.

The view presents mass change details: the change notice driving a revision, the organization, the base item being revised, the replacement or use-up item, revision increment behavior, and the disposition controls that determine how existing supply and work in process are treated (MRP_ACTIVE, UPDATE_WIP, USE_UP). Its primary role is to support diagnostics, reconciliation, and reporting against mass change interface rows prior to, during, or after they are processed by the Engineering mass change programs, and to provide a denormalized source for custom concurrent programs and inquiry screens.

Underlying Base Objects

The view is defined over five documented objects:

• ENG_REVISED_ITEMS_INTERFACE (SYNONYM) — the driving interface table supplying the primary columns.
• MTL_SYSTEM_ITEMS_VL (VIEW) — joined twice, once for the base item and once for the use-up item.
• MTL_CATEGORY_SETS (SYNONYM) — supplies the category set name.
• FND_COMMON_LOOKUPS (VIEW) — supplies the item type meaning for lookup type ITEM_TYPE and application 401 (Engineering).
• FND_GLOBAL (PACKAGE) — referenced for session context.

All joins are outer joins (the (+) operator), so interface rows survive even when the base item, use-up item, category set, or item type lookup is unresolved. This is intentional: engineers and support analysts use the view precisely to detect rows whose master data references are missing or invalid. The base item is linked via ERII.BASE_ITEM_ID to MTL_SYSTEM_ITEMS_VL.INVENTORY_ITEM_ID with ORGANIZATION_ID as the second correlation key. The use-up item is linked identically through ERII.USE_UP_ITEM_ID.

Key Columns

• ROW_ID — the ROWID of the underlying interface row, useful for targeted DML.
• CHANGE_NOTICE — the ECO/change order number that governs the mass change.
• ORGANIZATION_ID — the inventory organization in which the revision applies.
• BASE_ITEM_ID, BASE_DESCRIPTION, BASE_MODEL — the item being revised, its concatenated segments and description.
• USE_UP_ITEM_ID, USE_UP_ITEM_NO, USE_UP_ITEM_DESCRIPTION — the item designated for use-up consumption. USE_UP_ITEM_ID is the foreign key referenced by the user search term.
• USE_UP — flag indicating whether use-up logic applies to the change.
• USE_UP_PLAN_NAME — identifies the named use-up plan associated with the row.
• MRP_ACTIVE, UPDATE_WIP — controls for planning activity and work in process updates.
• ITEM_FROM, ITEM_TO, CATEGORY_FROM, CATEGORY_TO — mass change selection ranges.
• INCREMENT_REV, ITEM_TYPE, ITEM_TYPE_NAME, ALTERNATE_SELECTION_CODE, STRUCTURE_ID — revision and structure attributes.
• CATEGORY_SET_ID, CATEGORY_SET_NAME — the catalog context for the mass change.
• SCHEDULED_DATE, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — auditing and scheduling columns.

Common Use Cases and Queries

Typical uses include reconciling use-up items before submitting mass change, verifying that item type lookups resolve, and tracing which use-up plan a change notice will consume.

List mass change rows with a defined use-up item:

• SELECT change_notice, organization_id, base_item_id, use_up_item_no, use_up_item_description FROM apps.eng_revised_items_interface_v WHERE use_up = 'Y' AND use_up_item_id IS NOT NULL;

Detect unresolved use-up item references (join failure on USE_UP_ITEM_ID):

• SELECT row_id, change_notice, organization_id, use_up_item_id FROM apps.eng_revised_items_interface_v WHERE use_up_item_id IS NOT NULL AND use_up_item_no IS NULL;

Group by change notice to summarize use-up planning:

• SELECT change_notice, use_up_plan_name, COUNT(*) FROM apps.eng_revised_items_interface_v GROUP BY change_notice, use_up_plan_name;

Filter by item type lookup meaning to isolate specific revision classes. All queries should be executed with the APPS schema or a synonym and appropriate read privileges on the underlying objects.