Symptom
You have maintained Planned Independent Requirements (PIR) on the assembly level. After planned order is created for the header material, the dependent requirement (DepReq) doesn't consume the existing PIR. The PIR and DepReq appear in Monitor Stock / Requirements List (MD04) at the same time, which results in extra supplying items generated.
Environment
SAP S/4HANA Cloud Public Edition
Cause
The "Mixed MRP" indicator is not correctly maintained in the component master data.
Resolution
By default, the PIR will only be consumed by the sales order. In order to make it consumed by other requirement elements, the "Mixed MRP" indicator needs to be set in the master data (MRP3 view) accordingly.
- For subassembly planning with final assembly, for example planning strategy 70, where the requirement type of the PIR is VSFB, the "Mixed MRP" indicator must be "1".
- For subassembly planning without final assembly, for example planning strategy 52, where the requirement type of the PIR is VSE, the "Mixed MRP" indicator must be "3".
Keywords
Planned Independent Requirements (PIR), MD04, Stock/Requirements List, dependent requirements (DepReq), MRP, material requirements planning, Mixed MRP indicator, SAP S/4HANA Cloud, VSFB, VSE, consumption , KBA , PP-MP-DEM-2CL , Demand Management (Public Cloud) , PP-MRP-2CL , Material Requirements Planning (Public Cloud) , Problem
SAP Knowledge Base Article - Public