Results for “remaining_impl_units”

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

Overview

The MRP_PENDING_ENG_CHANGES table is a MRP-schema object in Oracle E-Business Suite Release 12.1.1 and 12.2.2, registered under the Master Scheduling/MRP product family. Oracle's own ETRM documentation describes its purpose tersely as "Not currently used." This means the table is a legacy or dormant artifact: it remains physically present with a valid status and a full column set, but no active concurrent program, planner, or standard workflow in Release 12 relies on it as a functional driver. Consultants encountering the table should treat it as a historical residue rather than a live transactional structure.

Based on the primary-key structure and foreign-key topology documented for the object, the table can be modeled heuristically as a link table in Data Vault terms. Its surrogate key is ECN_ID, and its foreign keys reach outward to item master and engineering change entities, which is the classic pattern of an intersection or association record rather than a hub (which would carry its own natural business key) or a pure satellite (which would carry descriptive attributes hanging off a hub). The table appears intended to associate engineering change notices with affected items and effectivity information within a planning context, though Oracle has never activated that behavior in the shipping product.

Key Information Stored

The documented physical schema contains 28 columns. The most significant are summarized below.

• ECN_ID — The surrogate primary key defined by MRP_PENDING_ENG_CHANGES_PK and reinforced by the unique index MRP_PENDING_ENG_CHANGES_U1. It is the business-key candidate documented for the table.
• INVENTORY_ITEM_ID, ORGANIZATION_ID, COMPILE_DESIGNATOR — The composite item-organization-designator reference pointing back to MRP_SYSTEM_ITEMS, identifying the affected item within a specific organization and MRP compilation context.
• CHANGE_NOTICE — The foreign-key column referencing ENG_ENGINEERING_CHANGES, carrying the engineering change notice (ECN) identifier.
• ENG_CHANGE_USING_ASSY_ID, DRIVING_ITEM_ID — Additional item references, both resolving to MRP_SYSTEM_ITEMS, distinguishing the using assembly from the driving item in a change relationship.
• ENGINEERING_CHANGE_TYPE, REVISION, USE_UP_CODE — Descriptive attributes describing the nature of the change, the resulting revision, and the disposition of existing stock.
• EFFECTIVITY_DATE, SUGGESTED_EFFECTIVITY_DATE, OLD_EFFECTIVITY_DATE — Date fields describing current, proposed, and prior effective dates for the change.
• REMAINING_IMPL_UNITS, ABSOLUTE_QUANTITY — Quantity fields supporting use-up or absolute-quantity change logic.
• OPTIONAL_COMPONENT, WIP_SUPPLY_TYPE, OPERATION_SEQ_NUM, OPERATION_OFFSET_PERCENT — Manufacturing-oriented qualifiers tying the change to a routing operation and component behavior.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Standard concurrent-program audit columns.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard EBS who-columns.

Common Use Cases and Queries

Because the table is documented as not currently used, its practical use cases are limited to archaeology, data migration reconciliation, and impact assessment before any cleanup. Typical patterns include confirming whether rows exist at all, checking for orphaned ECN references, and verifying whether custom code has repurposed the structure.

A basic existence and volume check:

• SELECT COUNT(*) FROM mrp.mrp_pending_eng_changes;

Reconciling the ECN identifier against the engineering change master:

• SELECT p.ecn_id, p.change_notice, p.inventory_item_id, e.change_notice
• FROM mrp.mrp_pending_eng_changes p, eng.eng_engineering_changes e
• WHERE p.change_notice = e.change_notice;

Checking for orphaned item references:

• SELECT p.ecn_id, p.inventory_item_id
• FROM mrp.mrp_pending_eng_changes p
• WHERE NOT EXISTS (SELECT 1 FROM mrp.mrp_system_items s
• WHERE s.inventory_item_id = p.inventory_item_id
• AND s.organization_id = p.organization_id);

Reporting scenarios should generally avoid this table for operational metrics. If historical engineering-change planning data is required, the active sources are the engineering change and item master tables, not this one.

Related Objects

The documented foreign keys identify the principal dependent and referenced objects.

• MRP_SYSTEM_ITEMS — Referenced three times: via INVENTORY_ITEM_ID, ENG_CHANGE_USING_ASSY_ID, and DRIVING_ITEM_ID, each joined with ORGANIZATION_ID and COMPILE_DESIGNATOR.
• ENG_ENGINEERING_CHANGES — Referenced via CHANGE_NOTICE, joined with ORGANIZATION_ID, providing the engineering change notice header.
• MRP_PENDING_ENG_CHANGES_PK / MRP_PENDING_ENG_CHANGES_U1 — The primary and unique indexes on ECN_ID.

Additional objects commonly touched during investigation include the MRP_SYSTEM_ITEMS hierarchy views, engineering change revision and effectivity tables, and the standard EBS concurrent program audit views that resolve REQUEST_ID and PROGRAM_ID. No documented view or public API in the supplied metadata depends on MRP_PENDING_ENG_CHANGES, consistent with its dormant status.