Search Results mrp_gross_requirements




Overview
Explore in AI Chat

Overview

The MRP_GROSS_REQUIREMENTS table is a core transactional data store within the Oracle E-Business Suite (EBS) Master Scheduling/MRP module. It serves as the primary repository for all gross requirement records generated during a Material Requirements Planning (MRP) or Master Production Schedule (MPS) run. A gross requirement represents the total demand for a component item before considering any available inventory, scheduled receipts, or safety stock. This table is fundamental to the planning engine's logic, as it holds the foundational demand data against which netting and planning calculations are performed to generate supply recommendations.

Key Information Stored

The table stores detailed records for each demand instance. Its primary key is the DEMAND_ID, which uniquely identifies each gross requirement record. Critical foreign key relationships define the context of the demand. These include links to the MRP_SYSTEM_ITEMS table (via INVENTORY_ITEM_ID, ORGANIZATION_ID, and COMPILE_DESIGNATOR) to identify the demanded component item, and to the same table for the USING_ASSEMBLY_ITEM_ID to identify the parent assembly creating the demand. The DISPOSITION_ID column links to the MRP_RECOMMENDATIONS table, connecting the raw demand to the planned order or schedule that was generated to fulfill it. Other essential columns typically include the requirement quantity, the date the demand is needed, and identifiers for the specific planning run (COMPILE_DESIGNATOR) and organization (ORGANIZATION_ID).

Common Use Cases and Queries

This table is central to demand analysis, pegging inquiries, and troubleshooting planning output. A common use case is tracing the source of demand for a specific component. For example, a planner might query to see all gross requirements for an item in a given plan to understand total demand volume. Another critical scenario involves pegging analysis, where the relationship between a supply recommendation and its originating demand is examined. The foreign key to MRP_FULL_PEGGING facilitates this. A typical analytical query would join MRP_GROSS_REQUIREMENTS with MRP_SYSTEM_ITEMS and filter by ITEM, ORGANIZATION, and PLAN.

  • Sample Query Pattern: SELECT mgr.*, msi.segment1 item_code FROM mrp_gross_requirements mgr, mrp_system_items msi WHERE mgr.inventory_item_id = msi.inventory_item_id AND mgr.organization_id = msi.organization_id AND mgr.compile_designator = msi.compile_designator AND msi.segment1 = '&ITEM' AND mgr.compile_designator = '&PLAN';

Related Objects

The MRP_GROSS_REQUIREMENTS table has integral relationships with several other key MRP tables. Its primary foreign key dependencies, as documented, are:

  • MRP_RECOMMENDATIONS: Linked via DISPOSITION_ID, this relationship connects a demand to the planned order, purchase requisition, or work order recommended to satisfy it.
  • MRP_SYSTEM_ITEMS: Linked twice—for the component item being demanded and for the parent assembly creating the demand. This provides all item master attributes for the planning context.
  • MRP_FULL_PEGGING: The DEMAND_ID is referenced by this table, which provides detailed hierarchical pegging information to trace demand back to its ultimate source (e.g., a sales order or forecast).

These relationships make MRP_GROSS_REQUIREMENTS a critical junction point for understanding the complete flow from source demand to planned supply within the planning engine.