Monday morning, whiteboard in hand
Picture a familiar start to the week. A customer wants an earlier ship date. A supplier’s delivery has moved. One production order is already underway, and the parts for another job are spread across two warehouses.
Someone reaches for the whiteboard. They list the jobs, make a few calls, check a spreadsheet, and try to remember which components are already on order. It can work, until the schedule changes again.
The problem isn’t the whiteboard. It’s that no single board can easily keep every order, component, stock balance, and lead time in view at once. Planning needs dependable inputs and a repeatable way to connect them.
That’s where the MRP Wizard comes in.
What the MRP Wizard calculates
Material requirements planning, or MRP, looks at the demand and supply included in a planning run. In SAP Business One, open sales orders and forecasts can contribute to demand. Existing inventory and supply documents can affect what still needs to be made or bought.
For manufactured items, the calculation can follow the bill of materials (BOM) down from a finished product to its components. If a sales order calls for 40 finished units, the plan can account for the materials those units require, while considering existing supply and inventory along the way.
The result is not simply a list of products to order. It is a set of recommendations that can include production orders and purchasing documents. When planning by warehouse, the run can also recommend inventory transfers where appropriate.
A practical distinction matters: the wizard recommends; your team reviews and acts. After examining the results, planners can save recommendations and use the order recommendation process to review, adjust, and create the actual documents.
What goes into a useful run?
The MRP Wizard can only work with the information and selections it is given. Before relying on a weekly plan, make sure the core inputs reflect how the business actually operates.
1. Demand: orders and forecasts
Select the relevant demand sources for the planning run. Open sales orders show committed customer requirements. Forecasts help represent expected demand that has not yet arrived as an order.
If sales orders should consume forecast, review the consumption settings. When configured to consume forecast, an order can reduce the matching forecast demand rather than simply being added on top of it. This helps avoid planning for the same expected demand twice.
2. Supply: what is already coming
Existing supply matters just as much as demand. Depending on the run’s settings, the calculation can consider inventory, purchase orders, planned or released production orders, and other selected supply sources.
That distinction can change the plan. A component already on a confirmed purchase order should not be treated like a component with no incoming supply. Planners should verify that the sources selected for the scenario match the decisions they want it to support.
3. Item rules and lead times
Item planning data helps shape the recommendations. Lead time, minimum order quantity, order multiple, and order interval can influence the suggested timing and quantity.
If a material is bought in fixed pack sizes, for example, the recommended quantity may need to meet the order multiple rather than match demand exactly. Lead times help schedule requirements backward so materials are planned for the date they are needed. If a component’s lead time makes a date unrealistic, the result can flag the timing problem instead of hiding it.
4. Warehouses and BOMs
Decide whether the run should consolidate planning at the company level or calculate separately by warehouse. Warehouse choices affect which inventory, demand, and supply are considered. That matters when materials are not interchangeable across locations or need to be moved before production.
BOMs need attention, too. If a finished product has multiple levels of components, the BOM structure tells MRP what is needed to make it. Incorrect component quantities or warehouse assignments can lead to recommendations that look precise but don’t fit the floor.
The weekly run: from setup to decisions
A disciplined weekly run can give the team a consistent routine:
- Choose or create a scenario. Define its planning horizon and time periods. A weekly view can help teams review requirements in weekly blocks, while a daily view provides more timing detail.
- Select the items and warehouses. Decide whether to plan all relevant MRP items or a specific selection, and confirm which warehouse data to include.
- Choose demand and supply sources. Select the documents, forecasts, inventory, and existing orders the run should consider.
- Run MRP and review the report. Check recommended quantities, projected inventory, and any problem items.
- Inspect the recommendations. Review the proposed production and purchasing documents, release dates, due dates, and quantities.
- Make the call. Adjust or create documents through the order recommendation process based on what the team knows about capacity, suppliers, and shop-floor priorities.
That last step is where people matter. The system can calculate a requirement from the inputs. Your planner knows that a machine is down for maintenance, a supplier needs a call, or a rush job has changed the day’s priorities.
Read the exceptions, not just the totals
A clean-looking total can hide a tight component or a date that cannot be met. Pay attention to problem indicators and recommendations affected by lead times. Check the underlying demand and supply details when a quantity seems surprising.
When results do not make sense, start with a smaller scenario: a limited item selection, a short horizon, or one demand source. Confirm the BOM, inventory, open documents, forecast settings, and item planning data. Then add more sources and complexity. That step-by-step check is often faster than trying to diagnose an entire company-wide run at once.
For the full configuration and process details, see SAP’s MRP guide for SAP Business One. To explore how we support manufacturers with SAP Business One, visit Quaint Business Solutions.
A clearer starting point for the week
The goal isn’t to replace the people who know the floor. It’s to give them a plan grounded in current orders, inventory, supply, forecasts, and production rules, then make it easier to spot what needs attention.
One MRP Wizard run won’t resolve missing data or make every schedule change painless. But a consistent planning process can help your team move from scattered updates to a shared set of recommendations. The whiteboard still has a place. It just doesn’t have to do all the math.
Frequently Asked Questions
Does the MRP Wizard create production and purchase orders automatically?
The wizard produces recommendations. Your team reviews and saves them, then uses the order recommendation process to adjust and create the actual documents.
Can MRP include both sales orders and forecasts?
Yes, when those sources are selected for the run. Review forecast-consumption settings so sales orders are handled as intended and forecast demand is not accidentally counted twice.
Why might an MRP recommendation show a date problem?
The item’s lead time, the planning horizon, existing supply, or other planning details may mean the requirement cannot be met by its needed date. Check the recommendation and its underlying demand and supply, then verify the item and BOM data.
What should we check before trusting a weekly plan?
Confirm the relevant sales orders and forecasts, existing inventory and supply documents, BOMs, warehouse selections, and item planning rules. Good planning starts with dependable inputs.
