Results for “to_wip_entity_id”

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

Overview

ENG_REVISED_ITEMS is a core Engineering (ENG) module table in Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It stores the set of pending and implemented revised items that result from engineering change orders (ECOs). Each row represents a single revised-item record tied to a change notice, capturing the item being revised, the effective revision, schedule and implementation details, disposition and use-up information, and the transfer or copy instructions applied when the change is executed.

The table acts as the central staging and history repository linking an engineering change notice to the affected item, bills of material, routings, and components. The ETRM relationship analysis classifies this object as satellite-leaning. Read as a modeling suggestion, this indicates that ENG_REVISED_ITEMS behaves primarily as a descriptive satellite keyed by a surrogate sequence, with a modest number of outgoing references rather than serving as a pure hub or a connector link. Its identity is anchored on REVISED_ITEM_SEQUENCE_ID, and most dependent engineering data hangs off that key.

Key Information Stored

The surrogate primary key is REVISED_ITEM_SEQUENCE_ID, enforced through the unique index ENG_REVISED_ITEMS_U2 and the ENG_REVISED_ITEMS_PK constraint. Because the same column is used as a business-key candidate by the unique index, integrators should treat it as the stable join key rather than assuming a natural composite key. The documented physical schema contains 94 columns; the most functionally significant include:

• CHANGE_NOTICE — the ECO that drives the revision; joins to ENG_ENGINEERING_CHANGES.
• REVISED_ITEM_ID — the item being revised; references MTL_SYSTEM_ITEMS_B.
• ORGANIZATION_ID — the inventory organization context for the revision.
• BILL_SEQUENCE_ID — the bill of material structure affected; references BOM_STRUCTURES_B.
• NEW_ITEM_REVISION and NEW_REVISION_LABEL — the revision the item will move to.
• STATUS_TYPE / STATUS_CODE — whether the revised item is pending or implemented.
• IMPLEMENTATION_DATE, AUTO_IMPLEMENT_DATE, SCHEDULED_DATE, EARLY_SCHEDULE_DATE — timing controls for automated implementation.
• DISPOSITION_TYPE, USE_UP, USE_UP_ITEM_ID, USE_UP_PLAN_NAME — disposition and use-up strategy for residual stock.
• TRANSFER_OR_COPY, COPY_TO_ITEM, TRANSFER_OR_COPY_BILL, TRANSFER_OR_COPY_ROUTING — copy/transfer behavior for the change.
• NEW_ROUTING_REVISION, ROUTING_SEQUENCE_ID, NEW_STRUCTURE_REVISION — routing and structure revision targets.
• CANCELLATION_DATE, CANCEL_COMMENTS, IMPLEMENTED_ONLY — lifecycle and cancellation state.
• Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY) plus the 15 ATTRIBUTE flex columns.

Common Use Cases and Queries

Engineering and manufacturing teams query this table to track open ECOs, verify pending revisions before implementation, and report on disposition and use-up planning. A typical pattern lists pending revised items for a given organization:

• SELECT revised_item_sequence_id, change_notice, revised_item_id, new_item_revision, status_type
• FROM eng.eng_revised_items
• WHERE organization_id = :org_id AND status_type = 'PENDING'
• ORDER BY scheduled_date;

Engineers also join to MTL_SYSTEM_ITEMS_B to resolve item numbers and descriptions, and to ENG_ENGINEERING_CHANGES to report ECO status. Implementation auditing commonly filters on IMPLEMENTATION_DATE to reconcile revisions actually applied within a period. Because many downstream tables carry REVISED_ITEM_SEQUENCE_ID, a single row can be exploded to view its components, operations, and scheduled dates.

Related Objects

The table participates in a dense web of relationships. The most significant referencing objects, all joined on REVISED_ITEM_SEQUENCE_ID, include:

• ENG_REVISED_COMPONENTS — component-level changes for the revised item.
• ENG_REVISED_OPERATIONS — operation-level changes for the revised routing.
• ENG_CURRENT_SCHEDULED_DATES — scheduled and effective dates per revised item.
• BOM_COMPONENTS_B and BOM_INVENTORY_COMPONENTS — bill of material component revisions.
• ENG_CHANGE_LOGS_B and ENG_ATTACHMENT_CHANGES — change history and attachment tracking.
• ENG_REVISED_ITEMS_INTERFACE and MTL_ITEM_REVISIONS_INTERFACE — open interface staging.
• ENG_CHANGE_PROPAGATION_MAPS — propagation mapping across affected structures.
• BOM_OPERATION_SEQUENCES and MTL_RTG_ITEM_REVISIONS — routing revisions tied to the item.

Outbound foreign keys reference BOM_STRUCTURES_B, MTL_SYSTEM_ITEMS_B, ENG_ENGINEERING_CHANGES, and HR_ALL_ORGANIZATION_UNITS. This combination of inbound dependents and outbound references confirms the table's role as the anchor satellite for engineering revision processing across both EBS releases.