Search Results eng_revised_items_interface

Overview

ENG_REVISED_ITEMS_INTERFACE is an Engineering (ENG) module interface table in Oracle E-Business Suite 12.1.1 and 12.2.2. It serves as the staging and processing interface for mass change transactions against revised items — the engineering change order (ECO) and mass change objects managed by Oracle Engineering. The table is owned by the ENG schema and is documented as VALID, containing 82 columns in the ETRM 12.2.2 physical schema. Its documented description is "Mass change details," reflecting its role as the record set that drives bulk revision updates, use-up processing, and BOM revision propagation before validated rows are promoted into the base engineering tables.

ETRM's heuristic Data Vault classification for this object is standalone. From a dimensional modeling perspective, this suggests the table behaves as an independent staging or work entity rather than a classic hub, link, or satellite. It references only one parent — ENG_REVISED_ITEMS via REVISED_ITEM_SEQUENCE_ID — so it is best modeled as a satellite-like detail structure attached to the revised item, carrying the transactional attributes of each mass change run.

Key Information Stored

The columns below are the most operationally significant of the 82 documented. Where a surrogate key is implied, note that the table's primary key is not explicitly enumerated in the metadata, but ENG_REVISED_ITEMS_IFCE_KEY and REVISED_ITEM_SEQUENCE_ID operate as the principal identifying and foreign-key columns.

• REVISED_ITEM_SEQUENCE_ID — foreign key to ENG_REVISED_ITEMS; links each interface row to its parent revised item record.
• CHANGE_NOTICE — the ECO or change order driving the mass change.
• ORGANIZATION_ID / ORGANIZATION_CODE — inventory organization context for the change.
• REVISED_ITEM_ID / REVISED_ITEM_NUMBER / PARENT_REVISED_ITEM_NAME — the item being revised and its parent in a BOM hierarchy.
• NEW_ITEM_REVISION / NEW_REVISION_LABEL / NEW_REVISION_REASON — the target revision values applied by the mass change.
• STATUS_TYPE / PROCESS_FLAG — lifecycle and processing state of each interface row.
• IMPLEMENTATION_DATE / SCHEDULED_DATE / NEW_SCHEDULED_DATE / AUTO_IMPLEMENT_DATE / EARLY_SCHEDULE_DATE — timing and scheduling attributes.
• DISPOSITION_TYPE / USE_UP / USE_UP_ITEM_ID / USE_UP_PLAN_NAME — use-up and disposition handling for superseded items.
• ALTERNATE_BOM_DESIGNATOR / STRUCTURE_ID / ALTERNATE_SELECTION_CODE — BOM structure and alternate selection context.
• ITEM_FROM / ITEM_TO / CATEGORY_FROM / CATEGORY_TO — mass substitution and reclassification pairs.
• REQUEST_ID / PROGRAM_ID / PROGRAM_APPLICATION_ID — concurrent program provenance for the interface run.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — the standard EBS descriptive flexfield block.
• LAST_UPDATE_DATE / LAST_UPDATED_BY / CREATION_DATE / CREATED_BY — standard WHO audit columns.

Common Use Cases and Queries

Primary use cases include monitoring mass change interface processing, auditing which ECOs applied to which items, diagnosing stuck or errored rows, and reconciling interface contents against ENG_REVISED_ITEMS before and after the workflow promotes them.

Typical patterns:

• Identify unprocessed rows: SELECT * FROM ENG.ENG_REVISED_ITEMS_INTERFACE WHERE PROCESS_FLAG IS NULL OR PROCESS_FLAG = 'N';
• Trace a change notice: filter on CHANGE_NOTICE and join to ENG_REVISED_ITEMS on REVISED_ITEM_SEQUENCE_ID.
• Organization-scoped reporting: group by ORGANIZATION_ID, STATUS_TYPE, and DISPOSITION_TYPE.
• Concurrent request audit: join REQUEST_ID to FND_CONCURRENT_REQUESTS to see which program loaded a batch.
• Use-up analysis: filter on USE_UP = 'Y' and inspect USE_UP_ITEM_ID, USE_UP_PLAN_NAME.

Because the table is an interface, production reporting should generally read the base tables post-processing; the interface is most valuable for validation, exception handling, and audit trails.

Related Objects

• ENG_REVISED_ITEMS — parent table; join via REVISED_ITEM_SEQUENCE_ID.
• ENG_CHANGES / ENG_CHANGES_IFCE — change order headers; linked via ENG_CHANGES_IFCE_KEY and CHANGE_NOTICE.
• ENG_REVISED_COMPONENTS_INTERFACE — sibling interface for component-level mass change rows.
• MTL_SYSTEM_ITEMS_B — item master; join via REVISED_ITEM_ID, ITEM_TO, USE_UP_ITEM_ID.
• BOM_STRUCTURES_B / BOM_BILL_OF_MATERIALS — BOM structure context via STRUCTURE_ID, BILL_SEQUENCE_ID.
• FND_CONCURRENT_REQUESTS — join on REQUEST_ID for program provenance.
• FND_FLEX_VALUES / FND_DESCR_FLEX_COL_USAGE — supporting the ATTRIBUTE1–15 DFF.

Together these objects form the Engineering mass change pipeline, with ENG_REVISED_ITEMS_INTERFACE acting as the transactional staging layer between ECO definition and implemented revisions.