# D365 Master Planning Ran but No Planned Orders Were Generated > Source: https://netray.co/erp-help/dynamics-d365fo-master-planning-no-planned-orders-generated > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## 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. ## Kind error ## System dynamics ## Erp Microsoft Dynamics 365 Finance and Supply Chain Management ## Module Master planning ## Query D365 master planning no planned orders generated ## Alternate Queries - 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 ## Applies To Dynamics 365 Supply Chain Management master planning, both the legacy engine and Planning Optimization. Menu names can vary slightly by release. ## Steps ### How to find why no planned orders were created **Items:** Open 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). Open 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. Open 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. Check the coverage group under Master planning > Setup > Coverage > Coverage groups, looking at the Coverage code, Positive days and Negative days, and time fence settings. On 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. Check 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. For purchased items, confirm an approved vendor exists if the Approved vendor check is on, and that trade agreements or prices exist for the item. Rerun 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. ## Sections ### Coverage settings that suppress planning **Body:** 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 **Body:** 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 **Body:** 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. **Code:** -- 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; ## 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. ## Ai Angle 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. ## Faq ### What does Manual coverage mean in D365? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms D365 master planning, no planned orders generated, item coverage D365, coverage group time fence, planning optimization D365, planned purchase orders missing, default order type D365, master plan run D365 --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json