The Calculate Plan Configuration table is where you define the parameters that will be used to run MRP. The Code field is the primary key that identifies the individual configurations and all the option you have as a user when running the calculate plan manually (staring/ending dates, MPS/MRP, etc..) is in the table.
Part of this setup is an option to specify what worksheet the suggestions should be created in and an item view. The item view sets the sorting and filters on the item table. This way you can separate the complete MRP run into different worksheets (see the Microsoft help about how to create records views).
In the below example Mike is responsible for planning the ‘furniture’ items, Sara is responsible for planning the manufactured items and Steve is responsible for planning the purchased items and they all have their own worksheets that are equal to their names that that are working in.
Note that when you split the MRP calculation up this way you need to be aware of the fact that the different items creates demand for each other and that they have to be planned that way. You can for example not plan purchased items before you plan manufactured items if they use the purchased items as components since that plan for the manufactured items creates demand for the purchase ones. If you are aware of this, then running multiple MRP calculations for different items are possible (you just have to run the top level parts first before the lower lever parts are run). The low level codes can help you determine what to run when.
You then setup Job Queue Entries to execute Codeunit 70666578 – NMM MRP Run Calc Plan Config with the Code from the Calculate Plan Configuration table as Parameter String. The below example will run MRP according to the settings defined for the A code. Note that the Parameter String can be a filter of Codes, A|B will for example run A followed by B. If you leave the Parameter String empty it will run all of them in the order of the Code.
