top of page

Planning Optimization

Master planning was in the past run within the application. MSFT for a few reasons that I will talk through in a second changed the architecture here how ever on how master planning is ran. So the build in engine is being depreciated. And moving forward, master planning is ran via planning optimization add-in – this is deployed in LCS. (life cycle services – what is your environment management platform)

The Planning Optimization Add-in enables master planning calculation to occur outside D365FO and the related SQL database.

The benefits that are associated with the Planning Optimization functionality include improved performance and minimal impact on SQL database during master planning runs. Quick planning runs can be done even during office hours, so that planners can immediately react to demand or parameter changes, etc.

From an architecture standpoint, the service is located in the same data center country or region as the related D365FO instance.

High-level data flow for regeneration runs

1.The Supply Chain Management client sends a signal to request a planning run from Planning Optimization.

2.Planning Optimization requests the required data via the integrated connector.

3.The SQL database sends the requested information about setup, master, and transactional data to Planning Optimization via the connector. The connector translates information between Supply Chain Management and the Planning Optimization service.

4.The Planning Optimization service holds planning-related data in memory and does the required calculations.

5.The planning result is sent to the Supply Chain Management database via the connector. The results include information such as planned orders and pegging information. Planning Optimization sends a signal to Supply Chain Management to indicate that the planning run has been completed. It also sends any relevant messages and warnings.

Master planning is driven of coverage groups setups as well as item coverage setups at the released product (REVIEW COVERAGE GROUP FOR ITEM GA0001)

Coverage code specification: (defaulted in from the coverage group assigned)

Coverage group logic based on:

Manual - The lot-sizing method where the system does not suggest purchased, transfer, or production orders for the item. The planner for the item will be in charge of creating the required orders for the replenishment of the item manually.

Per requirement - The lot-sizing method in which the system creates a planned purchase, transfer, or production order per requirement for the item. This is generally used for expensive items with intermittent demand. Means a SO is created, and then a planned order herefore is created.

Per period - The lot-sizing method that combines all the demand for a period into one order for the item.

Min/Max - The lot-sizing method that contains the replenishment of inventory up to a certain level when the predicted on-hand is below a threshold up to the max.

Coverage time zone:

For each plan, you can select how far in the future the various requirements and other considerations must be calculated by master planning. The period is known as a time fence.

The coverage time fence represents the scheduling period, or how far out the demand should be included. In other words, it indicates your planning horizon.

Action messages:

Action messages suggest changes that can be made to the existing supply order to help optimize the supply plan. For example, they might recommend that you advance or postpone orders, or that you increase or decrease the order quantities.

Recent Posts

See All


bottom of page