# Oracle Fusion Supply Planning: No Recommendations or Plan Run Fails > Source: https://netray.co/erp-help/fusion-supply-plan-no-recommendations-or-run-fails > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer An empty or failed Fusion supply plan usually traces to planning data collection that did not bring in demand or supply, plan options that exclude the items or organizations, or item attributes that make the item unplannable. Check collection first, then plan inputs, then item planning attributes and netting. ## Kind how-to ## System oracle-fusion ## Erp Oracle Fusion Cloud SCM ## Module Supply Planning / Plan Inputs ## Query Oracle Fusion supply plan run fails or produces no recommendations ## Alternate Queries - Fusion supply planning no planned orders generated - Oracle Cloud supply plan empty recommendations - Fusion collect planning data errors - Fusion supply planning plan run error ## Applies To Oracle Fusion Cloud SCM Supply Planning and Planning Central; plans run from the Supply Planning work area ## Steps ### How to diagnose an empty or failed supply plan **Items:** - Open the plan in Supply Planning and check the run status and any messages from the last plan run before changing anything. - Confirm planning data collection ran successfully: in Scheduled Processes, check the Collect Planning Data job (or the data load from files if you load externally) for errors. - Review the collection scope and the source organizations to confirm the right organizations and entities are included in the plan. - Open Plan Inputs and check the plan options: planning horizon, item selection, organizations and the demand and supply sets included. - Check item attributes for the items expected in the plan, such as planned make or buy, planning method and whether the item is enabled for planning in the organization. - Look at demand. If forecasts and sales orders are not collected or are outside the planning horizon, there is nothing to plan. - Check netting: on-hand in nettable subinventories, open purchase orders and work orders can fully cover demand, so no new supply is recommended. - Rerun the plan after the fix and review exceptions in the plan workbench for any remaining issues. ## Sections ### Collection is the first suspect **Body:** Supply Planning works on a snapshot of source data that is collected into the planning repository. If collection failed, ran only partly, or excluded an organization, the plan runs successfully against incomplete data and returns few or no recommendations. A green plan run does not prove the inputs were right. Check the collection job messages and the entities collected, and compare counts of items, on-hand and open orders against the source application. If you load from files, validate the files, because format problems cause rows to be rejected while the job still finishes. ### Plan options and horizon **Body:** The plan only considers what its options include. Item selection, organization scope and the horizon decide which demand is visible. A planning horizon that ends before the customer demand dates, or a plan that selects a category the item is not assigned to, leaves the item outside the plan. Also check the demand schedules and the forecast sets referenced in the plan. A plan that includes a forecast set which was never populated looks fine and does nothing. ### Item attributes and netting **Body:** Items need to be enabled for planning with a sensible planning method and make or buy flag, plus lead times that allow suggested dates to be computed. Missing lead times produce odd dates or suppressed recommendations. Check safety stock, order modifiers such as minimums and multiples, and sourcing rules. If the plan simply finds enough nettable supply, no new orders is the correct answer. Verify against on-hand status and subinventory nettable settings before assuming a defect. ## Pitfalls - Rerunning the plan repeatedly without checking whether data collection actually succeeded. - Treating a successful plan run as proof the right organizations were included. - Forgetting that non-nettable subinventories are ignored as supply, which can increase or decrease recommendations unexpectedly. - Setting a horizon shorter than the cumulative lead time of the item, so no planned orders appear. - Editing recommendations by hand to compensate for missing sourcing rules. ## Ai Angle ERPray, grounded on Fusion planning and source data, can compare what the plan sees against what is in inventory, purchasing and sales orders, and name the items where demand exists but the plan has no recommendation, with the likely reason. It cites its query and does not release or change plan outputs on its own. ## Faq ### Why does the plan run succeed but show nothing? **Answer:** A plan run succeeds if the engine completes, even over incomplete input. Failed or partial collection, a wrong horizon or an excluded item selection leaves the plan with little to evaluate. ### Do I have to collect planning data every time? **Answer:** Planning works on collected data, so changes in source transactions appear in the plan after the next collection. Your cadence depends on how fresh the plan needs to be. ### Where do I see plan exceptions? **Answer:** In the Supply Planning workbench for the plan, where exceptions such as late supply, shortages and past-due orders are reported. Review them after each run. ### Can sourcing rules stop recommendations? **Answer:** Yes. Without valid sourcing for a buy or transfer item, the engine cannot suggest a supplier or source, so check sourcing rules and assignments for the item and organization. ## Search terms Oracle Fusion supply planning, Fusion planning central, Collect Planning Data Fusion, Fusion supply plan no recommendations, Fusion planned orders not generated, Fusion plan inputs, Oracle Cloud MRP planning, Fusion plan options, Fusion planning exceptions --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json