Search Results mrp_item_wip_entities




Overview
Explore in AI Chat

Overview

The MRP_ITEM_WIP_ENTITIES table is a core data object within the Master Scheduling/MRP module of Oracle E-Business Suite (EBS). It serves as a junction or intersection table that establishes a critical relationship between discrete manufacturing jobs (WIP entities) and the items they produce within the context of a specific MRP or Master Scheduling plan. Its primary role is to enable the MRP engine to accurately account for work-in-process (WIP) supply during the planning run. By linking planned items to their specific manufacturing orders, the system can source supply from open jobs, ensuring that material plans reflect real-time production commitments and availability.

Key Information Stored

The table's structure is defined by its composite primary key, which uniquely identifies each record by combining four essential dimensions of the planning data. The key columns are INVENTORY_ITEM_ID and ORGANIZATION_ID, which identify the planned item and its inventory organization. The COMPILE_DESIGNATOR specifies the MRP plan name (e.g., 'MASTER' or a specific planning run) under which this relationship is valid. The WIP_ENTITY_ID is the unique identifier for the discrete job, linking directly to the WIP_ENTITIES table. This minimal schema ensures the table functions efficiently as a relational bridge, with the foreign key constraints enforcing data integrity between the MRP planning foundation tables (MRP_SYSTEM_ITEMS) and the manufacturing execution system (WIP_ENTITIES).

Common Use Cases and Queries

The primary use case is reporting and analyzing the WIP supply considered within an MRP plan. Planners and analysts often query this table to validate which open jobs were sourced by the planning engine. A typical query would join to item and job tables for a readable report. For example, to list all discrete jobs for a specific item in a plan, one might use:

  • SELECT msi.segment1 item_code, we.wip_entity_name job_name, we.status_type job_status
  • FROM mrp_item_wip_entities miwe,
  • mrp_system_items msi,
  • wip_entities we
  • WHERE miwe.inventory_item_id = msi.inventory_item_id
  • AND miwe.organization_id = msi.organization_id
  • AND miwe.compile_designator = msi.compile_designator
  • AND miwe.wip_entity_id = we.wip_entity_id
  • AND miwe.compile_designator = '&plan_name';

This data is also fundamental for troubleshooting plan output, such as understanding why a specific job did not contribute supply, which may involve checking for the job's presence or absence in this table post-compilation.

Related Objects

As indicated by the foreign keys, MRP_ITEM_WIP_ENTITIES sits at the nexus of several important planning and manufacturing tables. It is directly dependent on MRP_SYSTEM_ITEMS (the snapshot of items for a plan) and WIP_ENTITIES (the master table of discrete jobs). Furthermore, it is a parent table to key transactional planning tables. The MRP_RECOMMENDATIONS table references it, meaning planned order recommendations can be tied back to the specific WIP supply they were calculated against. Similarly, MRP_WIP_RESOURCES references it, linking the resource requirements for planned items to their associated jobs. This web of relationships underscores its central role in integrating bill-of-material, routing, and WIP data into the material planning process.