Search Results mrp_wip_components




Overview
Explore in AI Chat

Overview

The MRP_WIP_COMPONENTS table is a core data repository within the Oracle E-Business Suite (EBS) Master Scheduling/MRP module. It serves as the primary transactional table for storing component-level requirements for discrete work in process (WIP) jobs. During an MRP or Master Scheduling (MPS) compilation, the engine populates this table with detailed demand data derived from open and scheduled discrete jobs. This data is fundamental for the MRP engine's netting logic, which calculates component-level net requirements by subtracting on-hand and scheduled receipts from the gross requirements stored in this table. Its role is critical for generating planned orders and ensuring material availability aligns with the production schedule.

Key Information Stored

The table's structure is designed to uniquely identify a specific component requirement for a manufacturing job. Its primary key columns define this granularity: INVENTORY_ITEM_ID and ORGANIZATION_ID identify the component item; COMPILE_DESIGNATOR specifies the MRP plan name; WIP_ENTITY_ID points to the specific discrete job; and OPERATION_SEQ_NUM indicates the operation where the component is required. The JOB_REFERENCE_ITEM_ID is a foreign key to the item being manufactured (the assembly). While the provided metadata does not list all columns, typical supporting columns would include requirement dates, required quantities, allocated quantities, and supply types, enabling the MRP engine to perform time-phased planning.

Common Use Cases and Queries

The primary use case is analyzing component demand sourced from the shop floor for MRP reporting and diagnostics. Common queries involve listing all component requirements for a specific plan or job, identifying components with shortages, or reconciling WIP demand. For example, to find all component requirements for a specific MRP plan and assembly item, one might query:

  • SELECT wip.WIP_ENTITY_ID, wip.INVENTORY_ITEM_ID, msif.CONCATENATED_SEGMENTS, wip.OPERATION_SEQ_NUM FROM MRP_WIP_COMPONENTS wip, MRP_SYSTEM_ITEMS msi, MTL_SYSTEM_ITEMS_B_KFV msif WHERE wip.COMPILE_DESIGNATOR = '<PLAN_NAME>' AND wip.JOB_REFERENCE_ITEM_ID = <ASSEMBLY_ITEM_ID> AND wip.INVENTORY_ITEM_ID = msi.INVENTORY_ITEM_ID AND wip.ORGANIZATION_ID = msi.ORGANIZATION_ID AND msi.INVENTORY_ITEM_ID = msif.INVENTORY_ITEM_ID AND msi.ORGANIZATION_ID = msif.ORGANIZATION_ID;

This data is essential for custom reports that drill into WIP-sourced demand, separate from independent demand or purchase order requirements.

Related Objects

MRP_WIP_COMPONENTS has defined foreign key relationships with the MRP_SYSTEM_ITEMS table, which is a plan-specific snapshot of item master data. Two key relationships exist:

  • Foreign Key to MRP_SYSTEM_ITEMS (for Component Item): The columns MRP_WIP_COMPONENTS.INVENTORY_ITEM_ID, ORGANIZATION_ID, and COMPILE_DESIGNATOR reference MRP_SYSTEM_ITEMS. This validates the component item within the context of the specific MRP plan.
  • Foreign Key to MRP_SYSTEM_ITEMS (for Assembly Item): The columns MRP_WIP_COMPONENTS.JOB_REFERENCE_ITEM_ID, ORGANIZATION_ID, and COMPILE_DESIGNATOR reference MRP_SYSTEM_ITEMS. This validates the assembly item being built by the WIP job within the plan.

This table is also intrinsically linked to WIP entities (WIP_DISCRETE_JOBS) and the main planning table MRP_RECOMMENDATIONS, which consumes its demand data to generate supply suggestions.