Search Results completion_locator

Overview

ENG_REVISED_ITEMS_ERV is an Oracle E-Business Suite view owned by the APPS schema in the Engineering (ENG) product module. Its documented description is "Pending and implemented revised items," indicating that it consolidates engineering change order (ECO) revised item records across the full lifecycle — from the point a revision is defined against a change notice through the point it is implemented and closed. The view joins the core revision table ENG_REVISED_ITEMS to item master, bill of materials, routing, work in process, and lookup data, producing a denormalized, report-ready result set. In Oracle EBS 12.1.1 and 12.2.2 the object remains a VALID view in the APPS schema and is typically consumed by Engineering reports, ECO workbenches, and downstream integration extracts rather than by the base application forms.

Underlying Base Objects

Per the documented 12.2.2 metadata, the view is defined over the following referenced base objects:

• ENG_REVISED_ITEMS (SYNONYM) — the driving table, aliased ERI, holding one row per revised item per change notice.
• MTL_SYSTEM_ITEMS_VL (VIEW) — supplies the revised item number, description, and item attributes (aliased MSI), plus the use-up item (MSI2).
• BOM_BILL_OF_MATERIALS (VIEW) and BOM_OPERATIONAL_ROUTINGS (SYNONYM) — provide alternate BOM and routing designators and assembly type.
• WIP_ENTITIES (SYNONYM) — resolves the from and to work orders (WI1, WI2).
• FND_LOOKUP_VALUES (SYNONYM) and MFG_LOOKUPS (VIEW) — decode item type, disposition, and revised item status meanings (FVL, MLU, ML2).
• MTL_ITEM_REVISIONS (SYNONYM) and MTL_ITEM_LOCATIONS_KFV (VIEW) — referenced for revision and location context.
• FND_GLOBAL (PACKAGE) — used for session-level resolution of the operating context.

Key Columns

The view exposes identifiers and descriptive columns consolidated from the base tables. CHANGE_NOTICE, REVISED_ITEM_ID, ORGANIZATION_ID, and REVISED_ITEM_SEQUENCE_ID uniquely identify the revised item record. REVISED_ITEM_NO and REVISED_ITEM_DESCRIPTION come from the concatenated item segments. REVISED_ITEM_STATUS (via MLU.MEANING) and STATUS_TYPE reflect the workflow state. NEW_ITEM_REVISION carries the target revision, while DISPOSITION and DISPOSITION_TYPE describe disposition handling. AUTO_IMPLEMENT_DATE and the derived AUTO_IMPLEMENTED_FLAG signal automatic implementation. BOM and routing context is surfaced through ALTERNATE_BOM_DESIGNATOR and ASSEMBLY_TYPE. USE_UP, USE_UP_ITEM_NO, USE_UP_ITEM_DESC, and USE_UP_PLAN_NAME support use-up item processing. WIP linkage appears in FROM_WORK_ORDER, TO_WORK_ORDER, FROM_CUM_QTY, and LOT_NUMBER. The view also retains the standard ERI.ATTRIBUTE1 through ATTRIBUTE15 descriptive flexfield columns, plus WHO columns (LAST_UPDATE_DATE, CREATED_BY, and related) and concurrent request columns (REQUEST_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE).

Common Use Cases and Queries

Engineering and manufacturing reporting teams query this view to list outstanding ECO revised items, to trace which change notices affect a given assembly, and to report implemented revisions by date. A representative query filtered on the ATTRIBUTE or status columns follows:

SELECT revised_item_no, change_notice, revised_item_status, new_item_revision, auto_implemented_flag, implementation_date FROM apps.eng_revised_items_erv WHERE organization_id = :org_id AND revised_item_status = 'Pending';

A second pattern correlates revised items to work orders and use-up planning:

SELECT change_notice, revised_item_no, from_work_order, to_work_order, use_up_item_no, use_up_plan_name FROM apps.eng_revised_items_erv WHERE change_notice = :change_notice;

Because the view already resolves lookup meanings and item concatenated segments, it eliminates joins typically required when querying ENG_REVISED_ITEMS directly, making it well suited to operational dashboards and integration extracts.