Search Results mrp_system_items

Overview

The MRP_SYSTEM_ITEMS table is the central item master for the Master Scheduling and Material Requirements Planning (MRP) modules within Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It serves as a planning-specific snapshot or extension of the core inventory item definition, storing item attributes and control parameters that are critical for generating a material plan. Unlike the foundational MTL_SYSTEM_ITEMS_B table, which holds universal item definitions, MRP_SYSTEM_ITEMS organizes item data by a specific COMPILE_DESIGNATOR, allowing for multiple, concurrent planning scenarios (e.g., different forecast sets or planning methods) for the same item within an organization. Its primary role is to provide the item-level planning data consumed by the MRP engine during a plan run.

Key Information Stored

The table's composite primary key (INVENTORY_ITEM_ID, ORGANIZATION_ID, COMPILE_DESIGNATOR) uniquely identifies a planning item record. Key columns include planning-specific flags and parameters that drive the MRP calculation. These typically encompass planning method (e.g., MRP, MPS, DRP), planning time fence, lot-sizing rules, safety stock levels, shrinkage rates, and yield information. The table also maintains foreign key relationships to critical reference data, including the BUYER_ID (from PO_AGENTS), PLANNING_EXCEPTION_SET, CATEGORY_ID, ABC_CLASS, and the item's REVISION. The self-referential foreign key on BASE_ITEM_ID supports planning for configured items.

Common Use Cases and Queries

A primary use case is extracting a list of all items included in a specific MRP plan to validate planning parameters before a plan run. Developers and analysts frequently query this table to troubleshoot planning output by comparing item settings against generated planned orders. Common SQL patterns involve joining to MTL_SYSTEM_ITEMS_B for descriptive item details and filtering by the COMPILE_DESIGNATOR.

• Sample Query: Items in a Specific Plan
  SELECT msi.segment1 Item, msi.description, mrp.planning_make_buy_code
FROM mrp_system_items mrp, mtl_system_items_b msi
WHERE mrp.inventory_item_id = msi.inventory_item_id
AND mrp.organization_id = msi.organization_id
AND mrp.compile_designator = 'MAIN_PLAN';
• Reporting Use Case: Generating a parameter report that lists critical planning attributes (lot size, lead time, planning method) for all MPS items within a plan.

Related Objects

As the core planning item master, MRP_SYSTEM_ITEMS has extensive relationships. It is fundamentally sourced from MTL_SYSTEM_ITEMS_B and references MTL_CATEGORIES_B, PO_AGENTS, and MRP_PLANNING_EXCEPTION_SETS. Crucially, it is the parent table for numerous key planning detail tables. These child tables, which store the plan's output, include MRP_RECOMMENDATIONS, MRP_FORECAST_DATES, MRP_BOM_COMPONENTS, MRP_ASSEMBLY_OPERATIONS, MRP_AVAILABLE_TO_PROMISE, and MRP_AGGREGATE_RATES. Any plan data for a specific item is always qualified by the same triplet of keys that define its parent record in MRP_SYSTEM_ITEMS.