Results for “eng_revised_items_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The ENG_REVISED_ITEMS_V view (owned by the APPS schema, status VALID) belongs to the Oracle Engineering (ENG) module. Its documented purpose is to expose pending and implemented revised items — that is, the engineering change order (ECO) revisions recorded against items as they move through the engineering change lifecycle. In Oracle EBS 12.1.1 and 12.2.2, this view is the reporting and integration surface over the underlying ENG_REVISED_ITEMS table, denormalizing the revision header with descriptive item attributes, bill of material and routing context, workflow/WIP associations, and status lookups.

Where the base ENG_REVISED_ITEMS table stores only identifiers and codes, this view resolves those keys into meaningful values: item descriptions, item type, revised item status, disposition meaning, and work order names. It also derives computed flags such as AUTO_IMPLEMENTED_FLAG from the presence or absence of an auto-implement date. This makes the view suitable for engineering change reports, ECO dashboards, revision status extracts, and integration payloads that must communicate human-readable revision state rather than raw codes.

Underlying Base Objects

The view is built over the following documented base objects:

• ENG_REVISED_ITEMS (synonym) — the driving table, aliased ERI; supplies revision, change notice, disposition, status, and attribute columns.
• MTL_SYSTEM_ITEMS and MTL_SYSTEM_ITEMS_TL (synonyms) — item master and translations, providing BOM_ITEM_TYPE, component flags, and translated description.
• MTL_ITEM_REVISIONS_B and MTL_ITEM_REVISIONS_TL (synonyms) — item revision definitions and their translations.
• BOM_BILL_OF_MATERIALS (view) and BOM_OPERATIONAL_ROUTINGS (synonym) — supply assembly type, bill sequence, and alternate BOM/routing designators.
• WIP_ENTITIES (synonym) — resolves FROM_WIP_ENTITY_ID and TO_WIP_ENTITY_ID to work order names.
• FND_LOOKUP_VALUES, MFG_LOOKUPS, and FND_GLOBAL — provide meaning translations and session context.

The joins are largely outer joins keyed on organization and inventory item, allowing revisions to be reported even where no bill, routing, or work order is associated.

Key Columns

• CHANGE_NOTICE — the ECO that introduced the revision.
• ORGANIZATION_ID, REVISED_ITEM_ID — inventory organization and the revised item key.
• REVISED_ITEM_DESCRIPTION, ITEM_TYPE, BOM_ITEM_TYPE — descriptive item context.
• NEW_ITEM_REVISION — the revision value being applied.
• REVISED_ITEM_STATUS (from STATUS_TYPE) and DISPOSITION (DISPOSITION_TYPE) — lifecycle state and change disposition meaning.
• IMPLEMENTATION_DATE, AUTO_IMPLEMENT_DATE, AUTO_IMPLEMENTED_FLAG, SCHEDULED_DATE, EARLY_SCHEDULE_DATE, CANCELLATION_DATE — scheduling and implementation timestamps.
• ALTERNATE_BOM_DESIGNATOR, ASSEMBLY_TYPE — BOM context derived via DECODE from bill and routing sequences.
• FROM_WORK_ORDER, TO_WORK_ORDER, FROM_END_ITEM_UNIT_NUMBER, FROM_CUM_QTY, LOT_NUMBER — WIP and lot effectivity detail.
• USE_UP, USE_UP_ITEM_ID, USE_UP_PLAN_NAME — use-up (disposition) planning.
• Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE) and ATTRIBUTE1–ATTRIBUTE15 for extensibility.

Common Use Cases and Queries

Typical scenarios include listing pending revisions awaiting implementation, reporting implemented revisions by change notice, and extracting ECO details for downstream systems. A representative query for open (pending) revised items in an organization follows:

• SELECT change_notice, revised_item_id, revised_item_description, new_item_revision, revised_item_status, scheduled_date FROM eng_revised_items_v WHERE organization_id = :org_id AND revised_item_status = 'Pending' ORDER BY scheduled_date;
• SELECT change_notice, revised_item_id, new_item_revision, implementation_date, from_work_order, to_work_order FROM eng_revised_items_v WHERE change_notice = :eco AND implementation_date IS NOT NULL;
• Filtering on AUTO_IMPLEMENTED_FLAG = 1 isolates revisions implemented through automatic scheduling; combining DISPOSITION and USE_UP columns supports effectivity and use-up analysis.

Because the view resolves codes to meanings, it is well suited to concurrent-program extracts and BI Publisher reports, avoiding additional lookup joins in custom SQL.