Search Results mrp_gross_requirements




The MRP_GROSS_REQUIREMENTS table in Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2 is a critical data repository within the Manufacturing Planning (MRP) module. It stores gross requirement data generated during Material Requirements Planning (MRP) runs, serving as the foundation for demand calculation, procurement planning, and production scheduling. This table is part of Oracle's Advanced Supply Chain Planning (ASCP) architecture and integrates with inventory, purchasing, and production modules to ensure accurate material planning.

Table Structure and Key Columns

The MRP_GROSS_REQUIREMENTS table contains the following key columns:
  • PLAN_ID: Links to the MRP plan definition in MRP_PLANS.
  • ORGANIZATION_ID: Identifies the inventory organization.
  • INVENTORY_ITEM_ID: References MTL_SYSTEM_ITEMS_B for item details.
  • SR_INSTANCE_ID: Source instance identifier for distributed planning.
  • QUANTITY: The gross requirement quantity.
  • REQUIREMENT_DATE: Date when material is needed.
  • ORDER_TYPE: Classifies requirement sources (Sales Order, Forecast, etc.).
  • DEMAND_SOURCE_HEADER_ID: Links to originating documents (OE_ORDER_HEADERS_ALL for sales orders).

Functional Role in MRP Process

During an MRP run, the system:
  1. Aggregates demand from sales orders, forecasts, and interplant transfers
  2. Calculates gross requirements by time period
  3. Stores results in MRP_GROSS_REQUIREMENTS
  4. Uses this data for netting against available inventory
  5. Generates planned orders and purchase requisitions

Integration Points

The table interfaces with:
  • MRP_RECOMMENDATIONS: Converts requirements into actionable plans
  • MRP_SCHEDULE_DATES: Provides scheduling context
  • MTL_DEMAND: Feeds inventory management system
  • PO_REQUISITIONS_INTERFACE: Initiates procurement when external sourcing is needed

Technical Considerations

Key technical aspects include:
  • Table is populated during MRP.WORKBOOK.LAUNCH_PLAN process
  • Indexed on PLAN_ID, ORGANIZATION_ID, and INVENTORY_ITEM_ID for performance
  • Purged during plan refresh via MRP.PURGE_PLAN procedure
  • Partitioning recommended for large implementations

Customization and Extensions

Common extensions include:
  • Adding user-defined columns via descriptive flexfields
  • Creating custom views for specialized reporting
  • Developing triggers for validation or workflow integration
The MRP_GROSS_REQUIREMENTS table remains a cornerstone of Oracle's planning engine, providing the granular demand data necessary for effective supply chain execution. Its proper understanding is essential for implementing accurate MRP solutions, troubleshooting planning issues, and developing custom planning enhancements.