The planning template in Microsoft Dynamics 365 Business Central has a handful of fields that change how the planning run behaves. They are powerful, but they only make sense when you understand what each one does and how they work together. This article explains the four key fields: run for all low level codes, suggest quantity to order, run carry out actions, and auto run next template.
If you enable suggest quantity to order, the planning run uses a predefined suggest quantity to order template that you choose on the planning template. If you enable run carry out actions, the lines move from the simple MRP journal or the direct replenishment journal straight into the reverse planning worksheet.
If you enable run for all low level codes, the run plans in low level code order, starting at low level code zero, then one, then two, and so on. This option requires that suggest quantity to order and run carry out actions are also active. If you deselect one of those, the run for all low level codes option is deselected automatically.
The auto run next template field lets you chain several templates together so the planning run executes them one after another. To make either the low level code run or the chained run produce a true MRP, you must enable the include planning lines option on the templates. Without it, the run does not look into the reverse planning worksheet and the dependent demand is not picked up.
The four special fields on the planning template
When you open a planning template, for example a simple MRP template set up to find critical items in all levels, you will see fields that control more than just which items get listed:
- Run for all low level codes – plans in low level code order from zero and upwards.
- Suggest quantity to order – applies a chosen suggest quantity to order template.
- Run carry out actions – moves the resulting lines into the reverse planning worksheet.
- Auto run next template – runs the next template in a chain automatically.
How suggest quantity to order and carry out actions work together
When you enable suggest quantity to order, the run picks up the suggest quantity to order template you have defined on the planning template. This looks the same as running suggest quantity to order manually, but here you can predefine different templates and build your own. You tell the planning template: when I run from this template, use this specific suggest quantity to order template.
When you also enable run carry out actions, the planning run takes the lines from the simple MRP journal or the direct replenishment journal and puts them directly into the reverse planning worksheet. So instead of stopping at suggestions, the run carries them through in one go.
Why run for all low level codes depends on the other fields
Run for all low level codes makes the planning run process items in low level code order, starting at low level code zero, then one, then two, and so on. For this to work, the run has to suggest quantity to order and it has to carry out the actions at each level. That is why deselecting suggest quantity to order or run carry out actions also turns off run for all low level codes. The three belong together.
For this to produce a real MRP, you also need to check the include planning lines option on the template. Otherwise the run does not look into the reverse planning worksheet, and the dependent demand created at one level is not seen when planning the next level.
Example: planning all low level codes with one template
If you run calculate simple MRP with find critical items and no check marks in any of the auto fields, the run simply shows the lines with no quantity to order and does nothing further.
If you then enable run for critical items in all low level codes, the behaviour changes. With a location filter in place, the run calculates according to the one template, first on low level code one, suggesting the quantity to order, setting the carry out check mark, and putting the result into the reverse planning worksheet. Then it moves on to the next low level code.
Because include planning lines is checked on the template, the result in the reverse planning worksheet is a true MRP. The lines at one low level code create dependent demand for the items at the next low level code. If you open a line, you can see its components, and those components become demands for the lower level items. The single template drills all the way down.
Example: chaining templates with auto run next template
The auto run next template field lets you set up a sequence of templates that run automatically, one after the other. Instead of planning all low level codes with one template, you split the work across several templates with different filters and settings.
For example, you can set up three templates:
- Template one transfers orders to safety stock.
- Template two creates production orders to safety stock.
- Template three handles purchased items.
Each template in the chain (except possibly the last) needs include planning lines checked, otherwise it does not make sense to run it as an iterative job. Each template suggests the quantity to order, automatically carries out the actions, and puts the result into the reverse planning worksheet before the next template runs.
When you run calculate simple MRP with this chain, the first template calculates for the defined locations, but only for stock keeping units of type transfer order, putting them into the reverse planning worksheet and creating dependent demand. This still happens in low level code order. Then the next template calculates on the production location using a calculate all low level codes template.
The result in the reverse planning worksheet follows the true supply chain order, even across locations. The transfer orders appear at the top, the production orders further down, and the purchase orders after that. You get cross location planning that respects the real supply chain sequence.
What to watch out for
These fields are smart, but they only behave correctly when set up properly. Keep in mind:
- Run for all low level codes requires both suggest quantity to order and run carry out actions.
- You must check include planning lines on the template for the run to produce a true MRP and to read the reverse planning worksheet.
- When chaining templates with auto run next template, every template in the iterative chain needs include planning lines.
In short, the fields to be aware of on the planning template are auto suggest quantity, auto carry out, calculate all low level codes, and auto run next template.
Q&A
What does run for all low level codes do in a planning template?
It makes the planning run process items in low level code order, starting at low level code zero and moving up through one, two, and so on. This requires that suggest quantity to order and run carry out actions are also enabled, since the run needs to suggest quantities and carry out actions at each level.
Why does include planning lines need to be checked on the template?
Include planning lines makes the run look into the reverse planning worksheet so it picks up the dependent demand created at one low level code when planning the next. Without it, the run does not produce a true MRP and the levels are not linked.
What is the auto run next template field used for?
It lets you chain several planning templates so they run automatically one after another. You can, for example, run a template for transfer orders to safety stock, then one for production orders, then one for purchased items, and the result lands in the reverse planning worksheet in true supply chain order.
What happens if I deselect suggest quantity to order or run carry out actions?
Deselecting either of these also deselects run for all low level codes, because the low level code run depends on both being active to suggest quantities and carry out the actions at each level.
Does auto run next template work across multiple locations?
Yes. The chained run calculates across locations and arranges the result in the reverse planning worksheet in true supply chain order, with transfer orders at the top, production orders next, and purchase orders after that, even when each template targets a different location.