# Oracle Fusion Supply Planning Checklist > Source: https://netray.co/tools/oracle-fusion-supply-planning-checklist > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Work through plan setup, data collection, item and sourcing attributes, plan runs and exception review for Fusion Supply Planning. ## Category oracle ## Erp Oracle Fusion Cloud SCM ## Audience - Oracle Cloud consultant - Supply chain planner - Planning lead ## Tool **Kind:** checklist **Scoring Note:** Mark each item as done. Treat unfinished critical items as blockers for a plan run you intend to trust. A plan built on bad item or sourcing data produces confident but wrong recommendations. **Groups:** #### Plan setup and scope **Items:** **Text:** Plan type and scope agreed (which organizations, items and horizons) **Critical:** true **Text:** Planning organization hierarchy and planning calendar defined **Critical:** true Plan options reviewed: horizon, time buckets, demand and supply inputs included Demand source defined (sales orders, forecast, or both) and priority agreed Plan naming and ownership documented, one named owner per plan Scenario approach decided for what-if plans versus the operational plan #### Data collection **Items:** **Text:** Planning data collection scheduled and monitored for the source organizations **Critical:** true **Text:** Collected counts reconciled against source for items, on hand, work orders and purchase orders **Critical:** true Collection errors reviewed and a daily owner assigned Full versus incremental collection pattern agreed Timing of collection aligned with the plan run schedule Archived or inactive organizations excluded on purpose #### Item and sourcing attributes **Items:** **Text:** Planning method set per item (planned or not planned) and reviewed for exceptions **Critical:** true **Text:** Lead times populated for make, buy and transfer items **Critical:** true Safety stock rules agreed, with quantity or days of cover documented Order modifiers such as minimum, maximum and multiples checked for sensible values **Text:** Sourcing rules and assignment sets cover every planned item **Critical:** true Preprocessing, processing and postprocessing lead times validated Make or buy flags consistent between item and sourcing #### Bills, routings and capacity **Items:** **Text:** Bills of material effective and complete for planned assemblies **Critical:** true Routings and resources set up if capacity checks are in scope Alternate and substitute components decisions documented Yield and scrap factors reviewed Phantom and planning bills used only where intended #### Plan run and exceptions **Items:** **Text:** Baseline plan run end to end in a test pod with realistic volumes **Critical:** true Run duration recorded and acceptable for the planning window Exception types enabled and thresholds agreed with planners Recommended orders reviewed against known good cases **Text:** Process for releasing recommendations to purchase requisitions and work orders defined **Critical:** true Planners trained on exception workflows and plan comparisons Daily and weekly planning calendar documented ## Content **Intro:** A supply plan is only as good as the data it consumes. This checklist covers the setup, data collection, attributes and run discipline that decide whether Oracle Fusion Supply Planning produces recommendations a planner can trust. **Sections:** #### How to use the checklist **Body:** Work through the groups in order. Plan setup first, because scope decisions drive everything else. Then data collection, since a plan run can only see what has been collected. Critical items are blockers: do not schedule a go live plan until they are complete. Export the checklist to PDF for a design authority or to Excel to assign owners and dates for each open line. #### Why data collection matters most **Body:** Planning works on collected data. If collection is behind or partial, the plan will recommend orders for demand that was already supplied. Reconcile counts of items, on hand quantity, open work orders and purchase orders against the source after each cycle during testing. Assign a single person to review collection errors every day. This one habit prevents most mysterious plan results. #### Attributes and sourcing **Body:** Planners blame the tool for results that come from missing lead times, absent sourcing rules or odd order modifiers. Review the item attributes systematically, not by sampling. A good test is to list planned items with no sourcing rule or with a lead time of zero and ask whether that is truly intended. Many go live problems are found with that single query. **Bullets:** - Planned items with no sourcing assignment - Items with zero or default lead time - Order modifiers set far above typical demand - Mismatched make or buy flags #### Running and trusting the plan **Body:** Run a baseline plan on realistic volumes and compare a handful of items by hand: the demand, the supply, the net and the recommendation. If a planner can follow the logic for ten items, trust grows. Record run duration so you know if it fits your window, and keep one named owner for exception thresholds so they do not drift. **Cta:** If your planners want to ask questions across plan output and ERP transactions, Netray can build a private, read-only assistant on top of your data. The checklist is useful without it. **Faq:** #### What is the first thing to check when a plan looks wrong? **Answer:** Check what was collected. Compare the collected on hand, open orders and demand to the source. Many wrong-looking plans are simply planning on stale or partial data rather than showing a logic defect. #### Do I need sourcing rules for every planned item? **Answer:** Planned items need a defined source, whether through sourcing rules and assignment sets or item defaults, so the plan knows whether to make, buy or transfer. Items without a source commonly produce exceptions or no recommendation. #### How often should planning data be collected? **Answer:** As often as the planning cadence requires, and always before the plan run that will be acted on. Many teams schedule an incremental collection before each run and a full collection less often. Agree it with planners. #### Is this checklist only for new implementations? **Answer:** No. It is also useful as a health check on a live system, particularly after a quarterly update, an acquisition of new plants or a change in sourcing policy. ## Search terms oracle fusion supply planning checklist, oracle supply planning setup, oracle fusion plan inputs, oracle fusion collect planning data, oracle cloud supply plan options, oracle fusion planning exceptions, oracle supply chain planning implementation checklist, oracle fusion supply planning go live --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json