Materials with excluded MRP controllers were planned by MRP.
Reproducing the Issue
- Schedule MRP with specific MRP controllers.
- After running, materials with excluded MRP controllers were planned
The MRP controller in the MRP run does not restrict the planning to materials with the assigned MRP controller.
The MRP controller in the MRP run is just intended to define a "minimum" planning scope to start the MRP run ("plan at least all materials assigned to MRP controller xyz"). But the number of materials which are effectively planned is usually much higher and depends on the data modeling and the other planning parameters like include changed/all BOM components or stock transfer materials.
Two simple examples to illustrate that: You are able to assign different MRP controllers for a single material in the plant and in storage location/subcontracting MRP areas for evaluation purposes. But the MRP run will always plan all MRP areas of a material (plant + storage location/subcontracting MRP areas) at once by design, So it is impossible to distinguish the different MRP controllers at this point in time to ensure consistency of the planning result.
If the user wants to plan dependent materials as well (include changed/all BOM components or stock transfers) the MRP run will of course plan these materials even if they are not assigned to the MRP controller specified in the parameters of the MRP run. If the MRP controller would make a hard cut when materials of other MRP controllers will be selected you would never get a consistent planning result over all your materials. It would be necessary to define a unique sequence for planning runs with different MRP controller which is impossible if there are two-way or recursive dependencies between different MRP controllers.
This is standard system behavior.
Schedule MRP run, MRP controller , KBA , PP-MRP-PR , Planning Execution , Problem