Symptom
Purchase requisitions and sales order items don't have an one-to-one relationship in "Pegged Requirements" of Monitor Stock / Requirements List (MD04) app.
For example, sales order A and B both have a requirement quantity of 2. Purchase requisition C and D both have a quantity of 2 as well. In the Pegged Requirement screen, it is shown that 1 quantity of purchase requisition C and D is used to fulfill the requirement of sales order A, and the other 1 quantity of purchase requisition C and D is used to fulfilled the requirement of sales order B.
Environment
SAP S/4HANA Cloud Public Edition
Reproducing the Issue
- Open the Monitor Stock / Requirements List (MD04) app.
- Search for the affected material.
- Select a sales order item and choose Pegged Requirements.
- Observe that the sales order item quantity is fulfilled by multiple purchase requisitions.
- Observe that a single purchase requisition is split to fulfill multiple sales order items.
Cause
The pegged requirement relationship is not a physical (fixed) linkage between the demand and supply, but only a proposal of the system from the quantity perspective. The system proposes to use A purchase requisition to fulfill B sales order item, but it is not a must, since there is actually no real linkage between them, as we cannot see the purchase requisition information in the sales order and vice versa. The pegged requirement can be changed dynamically as the demand and supply situation changes. Any purchase requisition can be used to fulfill any sales order requirement.
Resolution
This behavior is by design: pegged requirements are dynamic proposals rather than fixed links, so no action is required.
See Also
Keywords
MD04, pegged requirements, one-to-one, purchase requisition, sales order item, dynamic proposal, MRP, stock requirements list, quantity mismatch, not match , KBA , PP-MRP-2CL , Material Requirements Planning (Public Cloud) , Problem
SAP Knowledge Base Article - Public