How-toSAP Business OneProduction / MRP

SAP Business One production planning: MRP, production orders, cost and variances

Question
sap business one production planning

Also searched as

  • sap business one production order variance report
  • sap business one manufacturing add on
  • sap business one for manufacturing industry
  • sap business one production standard cost rollup

Short answer

Planning in SAP Business One starts with demand (sales orders, forecasts), runs through the MRP wizard to produce recommendations, converts them into production and purchase orders, and ends with cost and variance review at close. The standard module is strong on BOM and MRP, light on scheduling and shop floor, where add-ons fill the gap.

Applies to: SAP Business One 10.0 on SQL Server or HANA; add-on scope depends on the vendor.

Run production planning in Business One

  1. 1Prepare master data: items with correct procurement method (make or buy), lead times, order multiples and minimum order quantity, and BOMs.
  2. 2Enter demand: sales orders, forecasts (Production > MRP > Forecast) and reorder points.
  3. 3Run the MRP Wizard (Production > MRP > MRP Wizard): choose scenario, scope, planning horizon, and what to consider (stock, open orders, forecasts).
  4. 4Review recommendations in Order Recommendation Report: select lines, then create production and purchase orders from it.
  5. 5Check component availability on the production order and release it. Adjust dates when components are late.
  6. 6Execute: issue components, report receipt, handle scrap, then close the order.
  7. 7After close, review cost and variances (see below) and adjust BOM quantities or standard costs.

Costing, standard cost and variance in production

Production order cost follows the item's valuation method. Components are issued at their cost, and finished goods are received at the order cost. With standard costing, the receipt is valued at the standard price of the finished item and the difference between actual consumption and standard is posted as a variance when you close the order. With moving average or FIFO, the finished goods take the actual cost.

A true multi-level rollup of standard cost is not a one-click function in the standard application. A common approach is to calculate the BOM cost from component prices (for example with a price list based on component cost), then update the finished item's standard price through a controlled process, such as a DI API script or an add-on. Confirm the options available in your version before you design the process.

Order variance reporting

Compare planned and actual quantities and costs per order. The production order carries planned component quantities (WOR1) and issued quantities, and the inventory log (OINM) records the cost of each movement. A query joining these gives a variance report by component and by order, which you can run as a saved query or Crystal report.

Look at quantity variance (more or less material than the BOM said), price variance (component cost changed) and yield variance (receipt quantity versus planned). Different corrective actions follow from each: BOM correction, purchasing action or process fix.

-- Planned vs issued quantity per component for closed orders
SELECT T0."DocEntry", T1."ItemCode", T1."PlannedQty", T1."IssuedQty",
       (T1."IssuedQty" - T1."PlannedQty") AS "QtyVariance"
FROM "OWOR" T0 JOIN "WOR1" T1 ON T0."DocEntry" = T1."DocEntry"
WHERE T0."Status" = 'L';

Limits, process manufacturing and add-ons

The standard module does not provide finite capacity scheduling, work center routings with operations, co-product and by-product management, formula recipes with potency or yield adjustments, or shop floor data collection. Companies in process industries such as food, chemicals and pharma, or those with complex discrete routing, usually add a partner manufacturing solution built on the Business One platform.

When you evaluate add-ons, test them against your real BOMs, a real month of orders, your costing method and your upgrade path, and ask how they handle the next feature package. A short pilot on a cloned database is cheaper than a wrong decision.

Try it here, free

SAP B1 Production Order Cost Variance Calculator

Open full tool

Compare actual to standard on a closed production order and see how much of the variance is material, labor rate and labor efficiency.

Common pitfalls

  • !Running MRP with wrong lead times and then blaming MRP.
  • !Assuming standard cost rolls up automatically through multi-level BOMs.
  • !Closing orders late, so variances land in the wrong period.
  • !Ignoring scrap and yield in the BOM, causing permanent quantity variances.
  • !Buying an add-on without checking how it handles upgrades and your custom fields.

How an ERP-grounded AI assistant handles this

Planning questions are mostly questions about data: which components are short for next week's orders, which orders have large variances, which items have unrealistic lead times. A read-only assistant on your Business One database answers these and shows the SQL, and because it can run on your own server, the data stays private. Write actions such as creating orders remain a human step.

Frequently asked questions

Does SAP Business One have MRP?

Yes. The MRP Wizard in the Production module calculates requirements from sales orders, forecasts and stock levels and produces recommendations to create production or purchase orders.

How does Business One calculate production order cost?

It values issued components at their inventory cost and receives finished goods according to the item's valuation method. With standard costing, differences are posted as variances when the order is closed.

Can Business One handle process manufacturing?

Only to a limited degree. Recipes, co-products, potency and strict batch control usually need a partner add-on. Test candidates against your process before you decide.

How do I see production variances?

Use the production order reports and the inventory audit, or build a query comparing planned and issued quantities and the inventory log cost. Variances are posted when the order is closed.

Related

How-to

SAP Business One MRP Wizard Returns No Recommendations: Checklist

When the MRP Wizard in SAP Business One produces an empty recommendation report, the cause is almost always data, not a bug: the item has Planning Method set to None, the scenario excludes the demand documents, the planning horizon is too short, or existing stock and orders already cover demand. Work through item planning data first, then the scenario, then the document selection.

How-to

SAP Business One Query: Released Production Orders with Component Shortages

Join OWOR (production order header), WOR1 (components) and OITW (stock per warehouse) to see, for every released production order, how much of each component is still to be issued and whether the warehouse can cover it. Run it in Tools > Queries > Query Manager, using double-quoted identifiers on HANA and the same query with minor syntax changes on SQL Server.

How-to

SAP Business One production process flow: from BOM to production order to receipt

In SAP Business One the production flow is: item master and bill of materials, MRP recommendation or manual order, production order (planned, released), issue for production, receipt from production, then close. Each step creates documents you can report on. This is a flow chart in words with the menus and tables.

Error fix

SAP M7 021: Deficit of SL Stock Quantity

M7 021 fires during a goods issue, delivery, or confirmation when SAP checks the unrestricted-use (SL) stock for the exact plant, storage location and batch combination and finds less than what you are trying to post out. Fix the entry (batch, storage location, quantity) first; only enable negative stock or downgrade the message to a warning if the business genuinely needs to post ahead of a receipt.

Error fix

SAP IDoc Status 51: Application Document Not Posted

Status 51 tells you the IDoc reached the application layer and failed to post, but the status text itself is not the error - the real cause sits in the status record's long text or the linked application log. Fix the underlying data or configuration, then reprocess the IDoc through BD87 rather than editing the status.

Error fix

SAP Short Dump TIME_OUT: Maximum Runtime Exceeded

A TIME_OUT runtime error means a dialog (or RFC) work process ran longer than the maximum allowed runtime, controlled by profile parameter rdisp/max_wprun_time (600 seconds by default). The fix is almost always to move the long-running work to background processing or tune the underlying program, not to raise the timeout.

AI for ERP

AI for SAP Business One, Without Sending Your Books to a Public API

Add AI to SAP Business One without sending customer data or financials to a public API. Service Layer and DI API integration, sized for an SMB budget.

AI for ERP

AI Agents for SAP Production Planning, MRP, and Exception Triage

AI agents that triage SAP MD04 exceptions, explain predictive MRP shortages, and draft planned-order actions, grounded on your own SAP data, deployed on-prem.

Stuck on SAP Business One?

Talk to engineers who work inside SAP Business One every week, and who build private AI that answers these questions from your own ERP data.

Keep exploring

Free tools

ERP fixes and how-tos

Runs with your ERP

AI on your ERP

Integrations

Comparisons

Software