D365 Master Planning Ran but No Planned Orders Were Generated
D365 master planning no planned orders generated
Also searched as
- D365 master planning not creating planned purchase orders
- D365 planned orders missing after master plan run
- item coverage coverage code D365 no planned order
- D365 planning optimization no planned orders
Short answer
If a master planning run produces no planned orders, check in this order: the item is included in the plan, coverage is not set to Manual, the item is not stopped for purchase or production, a default order type exists, and the demand falls inside the plan's and item's time fences. Also confirm whether the plan uses Planning Optimization.
Applies to: Dynamics 365 Supply Chain Management master planning, both the legacy engine and Planning Optimization. Menu names can vary slightly by release.
How to find why no planned orders were created
- 1Open Master planning > Master planning > Planned orders and filter by item and plan to confirm there really are none, and that you are looking at the right master plan (for example a Static or Dynamic plan).
- 2Open the master plan under Master planning > Setup > Plans > Master plans and confirm the plan is active and that you ran that plan, not another one. Check whether Use Planning Optimization applies.
- 3Open the item's coverage under Product information management > Released products > Plan > Item coverage and confirm the Coverage group and the Coverage code. Manual coverage never creates planned orders.
- 4Check the coverage group under Master planning > Setup > Coverage > Coverage groups, looking at the Coverage code, Positive days and Negative days, and time fence settings.
- 5On the released product, confirm Default order type is set under Plan > Default order settings, and that the item is not marked Stopped for purchase, transfer or production.
- 6Check demand: confirm the sales orders or forecast lines exist in the plan's date range, in the correct site and warehouse, and that the net requirement is actually above available on-hand.
- 7For purchased items, confirm an approved vendor exists if the Approved vendor check is on, and that trade agreements or prices exist for the item.
- 8Rerun planning with a regeneration for a test item and then open Master planning > Master planning > Planned orders and the Explosion view to see the pegging.
Coverage settings that suppress planning
Coverage code controls how planning reacts to demand. Requirement creates supply tied to each demand, Period groups demand into periods, Min/Max keeps stock between limits, and Manual tells the engine to ignore the item. Manual is the single most common reason planned orders never appear, often set intentionally for engineered items and then forgotten.
Item coverage can also override the coverage group, so check both the group and the item-level record. The item-level setting, by dimension such as site or warehouse, is used if present, and a coverage record for the wrong site means the warehouse you care about has no valid coverage.
Coverage group time fences influence the result. The Calculated lead time and the Coverage time fence mean that demand beyond the fence is ignored, so planned orders appear only for demand inside the horizon. A short fence with distant demand yields an empty planned order list.
Order settings, stop flags and approved vendors
Default order settings define what type of order planning creates: Purchase order, Production or Transfer. If Default order type is Not set or points to an order type the item cannot support, such as production without an active BOM and route, the engine cannot generate a planned order.
Stopped flags are a common trap. An item marked Stopped for purchase, even if only briefly, blocks planned purchase orders. Likewise a BOM version that is not approved or active, or one outside its date range, blocks planned production orders and may show a message in the planning log.
When Approved vendor check is on, planned purchase orders need a vendor on the approved vendor list for the item, or planning creates none. Confirm vendor setup and, where relevant, that a trade agreement or default purchase price exists so a vendor can be suggested.
Planning Optimization versus the legacy engine
Planning Optimization runs as an external service and requires its add-in to be installed and the master plan configured to use it. If the plan is set to use it but the add-in or the dataset sync is unhealthy, runs may complete with little or no output. Check the Planning Optimization pages for run status and errors.
Some settings behave differently between the engines. Time fence handling, coverage by dimension and certain parameters are implemented differently, so a configuration that worked on the old engine can produce unexpected results after the switch. Compare behavior on a single test item before blaming data.
Master planning logs help here. Review Master planning > Master planning > Master planning log or the Planning Optimization run details for messages on specific items, which often name the exact reason, such as a missing BOM or a stopped item.
-- Read-only: items with Manual coverage (ReqItemTable, coverage code 4 = Manual in legacy enum; verify in your version) SELECT ITEMID, COVPROFILE, REQGROUPID FROM REQITEMTABLE WHERE COVPROFILE = 4;
Common pitfalls
- !Running a different master plan than the one you are viewing.
- !Leaving coverage code on Manual for items that should be planned.
- !Missing Default order type, or an inactive BOM and route for planned production.
- !Items marked Stopped for purchase or production.
- !Short coverage time fences hiding distant demand.
- !Switching to Planning Optimization without validating the add-in and data sync.
How an ERP-grounded AI assistant handles this
An assistant grounded in the ERP, such as ERPray, can take an item and a plan and explain the absence of planned orders: coverage code, stop flags, default order type, approved vendor list and time fence, side by side with the demand it found. It reads item and plan setup with your roles and shows the queries, so a planner sees the reason in one answer.
Frequently asked questions
What does Manual coverage mean in D365?
Manual coverage tells master planning not to generate planned orders for the item. Demand is still visible, but supply must be created by hand. It is useful for special items but a frequent cause of missing planned orders.
Why are planned orders created for some warehouses but not others?
Item coverage can be set per site and warehouse. If the coverage record exists for one warehouse and not the other, or inherits a Manual setting, planning behaves differently by location. Review coverage by dimension.
Does a time fence stop planned orders?
Yes. Demand beyond the coverage time fence is ignored, and planning also treats the period inside a planning time fence differently, often creating action messages rather than new orders. Check both fences on the coverage group.
Where do I see why an item was skipped?
Check the master planning log, or the run details under Planning Optimization. Each shows item-level messages such as missing BOM, stopped items or missing vendors. Use the explosion view to inspect pegging for a single item.
Related
D365 Warehouse Wave Runs but No Work Is Created
When a wave finishes without creating work, one of four things is usually wrong: the wave template has no Create work method, no work template matches the work order type, no location directive finds a pick location, or the inventory is not available at the warehouse locations. Open the wave processing history and work creation history first, because they state which step failed.
Error fixFixing "There are currently no batch servers available for processing" in D365 F&SCM
This message means the batch framework cannot find any AOS instance flagged as a batch server and available for the batch group the job is assigned to. The fix is almost always in server configuration (System administration > Servers) or batch group assignment, not in the batch job itself.
Error fixD365 Purchase Order Workflow: Submit Button Missing or Workflow Not Starting
The Submit button only appears when change management is on for the vendor or legal entity and an active workflow version applies to the purchase order. Check that the Purchase order review workflow is activated for the right legal entity, that its conditions match the PO, and that the workflow batch jobs are running.
Error fixFixing "Cannot create a record in (table). The record already exists" in D365 F&SCM data entity imports
This is the standard kernel duplicate-key exception, thrown when the Data Management Framework tries to insert a staging row into a target table whose unique or alternate key already matches an existing record. It almost always means the entity's insert-vs-update logic did not recognize the target row as an update, not that you have a true accidental duplicate in your source file.
Error fixFixing "You do not have the following permissions on TableData (table): (permission)" in Business Central AL
This runtime error means the current user's assigned permission sets do not grant the required Insert, Modify, Delete, Read, or Execute right on that specific table. It is most common right after installing or updating a custom AL extension, because Business Central checks object-level permissions even for tables an extension owns.
Error fixFixing "The CIL object was not found" in Dynamics AX 2012
This error appears when the AOS tries to execute compiled CIL for a class or method that has not actually been regenerated since a code change was imported or edited, so the .NET runtime has nothing matching to run. The fix is a full compile followed by a full CIL generation and an AOS restart, not just a partial or incremental rebuild.
AI for ERPAI for Dynamics 365 Finance and Supply Chain beyond Copilot
AI for D365 Finance and Supply Chain beyond Microsoft Copilot: private LLM grounded on data entities and OData, on-prem-capable via Local Business Data.
Stuck on Microsoft Dynamics 365 Finance and Supply Chain Management?
Talk to engineers who work inside Microsoft Dynamics 365 Finance and Supply Chain Management every week, and who build private AI that answers these questions from your own ERP data.