Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Note
Community interest groups have now moved from Yammer to Microsoft Viva Engage. To join a Viva Engage community and take part in the latest discussions, fill out the Request access to Finance and Operations Viva Engage Community form and choose the community you want to join.
When you transition from the deprecated built-in master planning engine to Planning Optimization, you might notice differences in planned orders, quantities, and dates. Use this article and the related resources to identify whether an issue you're experiencing is due to an expected difference, an unsupported feature, or a parameter change.
Identify the type of issue
Use the following table to find the right resource for your situation:
| Issue | Resource |
|---|---|
| Planning Optimization shows different planned order results, dates, quantities, or behavior | Expected differences (this article) |
| A feature doesn't work or is missing in Planning Optimization | Planning Optimization fit analysis |
| Date or time calculations produce different results | Date and time parameters used by Planning Optimization |
| A master planning parameter seems to have no effect | Parameters not used by Planning Optimization |
| You have questions about when the deprecated engine will be removed | Deprecated master planning overview |
| You need guidance on the full migration process | Migration to Planning Optimization |
Expected differences
The following table lists specific differences between Planning Optimization and the deprecated master planning engine that aren't listed on the Planning Optimization fit analysis page.
| Feature | How Planning Optimization differs from deprecated master planning |
|---|---|
| Forecasts for today's date | Planning Optimization doesn't consider forecasts for today's date, though the deprecated master planning engine considered them. |
| Filtered production runs | For details, see Production planning - Filters. |
| Forecast planning | Forecast planning isn't supported. Use master planning where a forecast model is assigned to the master plan. |
| Number sequences for planned orders | Number sequences for planned orders aren't supported. Planning Optimization uses its own proprietary number sequence for all generated planned order numbers, and there's no method available for modifying this number sequence. The Master scheduling planned order number setting on the Number sequences tab of the Master planning parameters page has no effect when you use Planning Optimization. The planned order number normally shows 14 digits, but the sequence is actually built on 20 characters, with 6 digits allocated for the planning run count and 10 for the planned orders count. |
| Plan copy, plan delete, and plan version cleanup | Under Master planning > Master planning > Maintain plans in the navigation pane, the following items are disabled:
|
| Return orders | Planning Optimization doesn't consider return orders. |
| Scheduling related features | For details, see Scheduling with infinite capacity. |
| Safety stock fulfillment | Planning Optimization always uses the Today's date + procurement time option for the Fulfill minimum field on the Item coverage page. This choice helps prevent unwanted planned orders and other issues. If the procurement time isn't included for safety stock, planned orders that are created for low on-hand inventory are always delayed because of the lead time. Learn more in Safety stock fulfillment with the deprecated master planning engine. |
| Safety stock pegging and net requirements | The Safety stock requirement type isn't included and isn't displayed on the Net requirements page. Safety stock doesn't represent demand and doesn't have a requirement date associated with it. Instead, it sets a constraint on how much inventory must be present at all times. However, the Minimum field value is still taken into account when calculating planned orders during master planning. Inspect the Accumulated quantity column on the Net requirements page to see that this value was considered. Because the pegging is different, different actions might be suggested. Learn more in Safety stock fulfillment with the deprecated master planning engine. |
| Transport calendars | The value in the Transport calendar column on the Modes of delivery page is ignored. |
| Min/max coverage code with no values | With the deprecated master planning engine, when you use a min/max coverage code where no minimum or maximum values are set, the planning engine treats the coverage code as a requirement and creates one order for each requirement. With Planning Optimization, the system creates one order per day to cover the full amount for that day. |
| Net requirements and manually created planned orders | With the deprecated master planning engine, manually created supply orders for an item automatically appear among the net requirements for that item. For example, when you create a purchase order from a sales order, the purchase order appears on the Net requirements page without requiring any prior actions. This behavior occurs because the deprecated master planning engine logs inventory transactions in the inventLogTTS table and shows changes on the Net requirements page for dynamic plans. However, with Planning Optimization, manually created orders don't appear among the net requirements of an item until you run Planning Optimization (using a plan that includes the item), or until you select Update > Master planning on the Action Pane on the Net requirements page, which runs master planning for the item. For more information about how to work with the Net requirements page, see Net requirements and pegging information. |
| Net requirements and any changes to supply or demand | With the deprecated master planning engine, any changes to supply or demand for an item automatically appear among the net requirements for that item. For example, when you increase the quantity of a planned order, the purchase order appears on the Net requirements page without requiring any prior actions. This behavior occurs because the deprecated master planning engine logs inventory transactions in the inventLogTTS table and shows changes on the Net requirements page for dynamic plans. However, with Planning Optimization, any changes don't appear among the net requirements of an item until you run Planning Optimization (using a plan that includes the item), or until you select Update > Master planning on the Action Pane on the Net requirements page, which runs master planning for the item. Learn more about how to work with the Net requirements page in Net requirements and pegging information. |
| Resource assignment | When working with infinite capacity, the deprecated master planning engine assigns all planned orders to the same resource on a given resource group. Planning Optimization improves on this behavior by selecting resources at random so different production orders can use different resources. If you want to use the same resource for all planned orders, specify that resource in the route. |
| Extended data types (EDTs) | Planning Optimization doesn't support changes to the precision of EDTs. This process isn't officially supported and isn't guaranteed to work. |
| Safety stock fulfillment | Planning Optimization always uses a Fulfill minimum of Today's date + procurement time. This choice prepares the system to use a simplified planning setup in the future, and provides an actionable result. If the procurement time isn't included for safety stock, planned orders that are created for low on-hand inventory are always delayed because of the lead time. This behavior can cause significant noise and unwanted planned orders. The best practice is to change the setting to use Today's date + procurement time. Update master data to avoid warnings. Learn more in Safety stock fulfillment with the deprecated master planning engine. |
| Purchase order fulfillment | When fulfilling a purchase order, the system always applies a lead time and never disregards it, even if the Add delay to calculated requirement date parameter is set to No. This behavior differs from that of the deprecated master planning engine, which would set an unfeasible date in this case. For example, if today is March 1, 2024, lead time is 30 days, and Add delay to calculated requirement date is set to No, the deprecated engine creates a purchase order with date March 1, 2024, while Planning Optimization creates it with date April 1, 2024 (today plus the 30-day lead time). |
| Copy static to dynamic plan | Planning Optimization doesn't copy static plans to dynamic plans, regardless of the setting on the Master planning parameters page. In general, this operation is less relevant because of the speed and complete regeneration that Planning Optimization provides. If you use two or more plans, trigger master planning for each plan. |
| Negative days | Planning Optimization always uses dynamic negative days, regardless of the setting of Use dynamic negative days on the Master planning parameters. The Use dynamic negative days setting on the Master planning parameters page has no effect on this behavior. For more information on negative days, see Delay tolerance (negative days) |
| Today's date calendar | Planning Optimization doesn't consider the Today's date calendar setting on the Master planning parameters page. Planning Optimization always uses the current time rounded to the next whole hour. In the deprecated master planning engine, this setting defined the start of a freezing time fence. However, the system still uses the Today's date calendar parameter to determine whether a manually created production order is scheduled within the freezing time fence, even when you're using Planning Optimization. |
| Planned orders in the past | Planning Optimization never plans orders in the past, regardless of the Requested date setting. If you set a Requested date that's in the past, the system keeps your setting, but sets the Required date to Today. |
| Definition/meaning of safety stock | In Planning Optimization, safety stock isn't actual demand. For each coverage group, you can specify how strictly the system should peg safety stock as demand against the planned order that's created for it. (Learn more in Safety stock pegging options.) Coverage groups that use strict safety stock pegging work just like all groups in the deprecated engine where the Fulfill minimum field is set to Today's date + procurement time. In the deprecated master planning engine, safety stock is demand, the same as other demand types. You can specify when safety stock will be fulfilled. |
| When safety stock is fulfilled | In Planning Optimization, safety stock is always fulfilled on today's date + procurement time, regardless of the item coverage setting. In the deprecated master planning engine, item coverage settings include a Fulfill minimum field that defines when the safety stock must be fulfilled. (Learn more in Safety stock fulfillment with the deprecated master planning engine.) |
| Forecast plan time fence | When deciding which demand and supply forecast entries to take into consideration, Planning Optimization always takes the lower of the following two values: coverage time fence or forecast plan time fence. The deprecated planning engine always uses the forecast plan time fence. Planning Optimization therefore guarantees that the supply covers all demand forecast entries that are included in a plan. |
| Issue margin | When the issue margin can be met, Planning Optimization applies its value to the receipt requirement date, not the issue requirement date; if the margin can't be met, Planning Optimization pushes the issue requirement date forward. The deprecated planning engine always adjusts the issue requirement date by the value of the issue margin. Planning Optimization therefore treats the issue margin more correctly, as a shipping-time buffer that affects how far in advance receipt is required. Learn more in Safety margins. |
| Vendor calendar lead time | Planning Optimization doesn't consider closed days from the vendor's calendar when calculating lead times for delivery dates. It only considers the coverage group calendar when calculating lead times. Learn more in Calendar matrix for Planning Optimization. |
| Zero positive days | Setting positive days to one in Planning Optimization provides the same behavior as setting positive days to zero in the deprecated master planning engine. |
| Planning with negative on-hand quantities | If the system shows a negative aggregate on-hand quantity, Planning Optimization treats it as quantity 0 (zero) to help avoid over supply. Learn more in Planning with negative on-hand quantities. The deprecated master planning engine instead replenished the negative quantity. |
| Firming manual planned production orders | When firming planned production orders that were created manually, Planning Optimization doesn't automatically trigger the explosion of items. You must manually trigger item explosions as needed. |
| CTP with lean manufacturing | The event kanban rule replenishment strategy with event type sales event set to Automatic with CTP doesn't automatically generate and add kanbans to the schedule for sales order order lines that use the CTP delivery date control method. Instead, replenish through a planning kanban and apply auto-firming. |