SAP Business One production process flow: from BOM to production order to receipt
sap business one production process flow chart
Also searched as
- sap business one production process
- sap b1 bom to production order to receipt
- sap business one manufacturing user guide
- sap business one for manufacturing companies
Short answer
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.
Applies to: SAP Business One 10.0 (SQL Server and HANA). Menu names may vary slightly by version and localization.
The production flow step by step
- 1Master data: create finished goods, components and raw materials in Inventory > Item Master Data. Mark items as inventory items and set the valuation method.
- 2Bill of materials: Production > Bill of Materials. Choose type Production, enter components, quantities, warehouses and issue method (manual or backflush).
- 3Plan: run MRP (Production > MRP > MRP Wizard) to get recommendations, or create the order manually from a sales order or demand.
- 4Production order: Production > Production Order. Enter item, quantity, warehouse, dates. Status Planned, then change to Released when materials are ready.
- 5Issue for production: Inventory > Inventory Transactions > Issue for Production, based on the released order, for manual issue components.
- 6Receipt from production: Receipt from Production for the finished goods, based on the production order. Backflush components issue at this point if set.
- 7Close the order: set status Closed to post variances and stop further movements.
Documents and their tables
Each step leaves a trail in the database. The BOM sits in OITT (header) and ITT1 (rows). Production orders are in OWOR with component rows in WOR1. Issue and receipt for production create inventory documents in OIGE and OIGN with rows in IGE1 and IGN1. Stock movements for audit appear in OINM, and item stock per warehouse in OITW. Table prefix O means header or object table, and a trailing 1 means the row table of the same document, which helps reading the schema.
Use these for queries and reports, but treat the application as the source of truth for writes. Never update these tables directly.
-- Open production orders and their status (SQL Server / HANA)
SELECT T0."DocEntry", T0."ItemCode", T0."PlannedQty", T0."CmpltQty", T0."Status", T0."DueDate"
FROM "OWOR" T0 WHERE T0."Status" IN ('P','R');Reports and learning resources
For reporting, start with the Production reports: Production Order Status, Open Items List for orders, and Bill of Materials reports in the Production module, plus Inventory reports for stock audit. For custom reports use queries in Tools > Queries or Crystal layouts. SAP's own Help Portal carries the Business One user guide and the manufacturing documentation, and SAP partners publish training videos; verify versions against your release.
If you need a functional consultant for manufacturing, look for someone who has configured MRP, backflush rules, warehouse structure and cost accounting, since the production module is simple but the surrounding configuration decides whether results are right.
Scope for manufacturers (including Gulf region use)
Business One covers discrete and light assembly manufacturing well: multi-level BOMs, production orders, MRP, subcontracting via purchase orders, and basic shop floor through add-ons. It is widely used by small and mid-size manufacturers, including in the UAE, where local partners deliver implementation and localization such as VAT.
Where requirements grow into routing and capacity planning, shop floor data collection, batch genealogy or process manufacturing, check whether a manufacturing add-on is needed, and evaluate it against your process before committing.
Try it here, free
SAP B1 Production Order Cost Variance Calculator
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
- !Releasing an order without materials in stock and then forcing negative inventory.
- !Mixing manual and backflush issue methods without a clear rule per item.
- !Not closing orders, which leaves work in process and variances unposted.
- !Using the wrong warehouse on BOM rows so components are issued from the wrong site.
- !Reporting only from the order and ignoring OINM, which loses the audit trail.
How an ERP-grounded AI assistant handles this
Shop managers ask questions such as which orders are late or short of components. A read-only assistant over the Business One tables, like ERPray, answers those in plain language and shows the SQL it used. For manufacturers who keep data on-prem, the model runs on your own server and respects the permissions of the connecting user.
Frequently asked questions
What are the main steps of production in SAP Business One?
Maintain items and the bill of materials, plan with MRP or manually, create and release a production order, issue components, receive the finished goods, and close the order. Close posts variances and stops movements.
Where is the production order stored?
In table OWOR for the header and WOR1 for the component rows. Issue and receipt documents are stored in OIGE/IGE1 and OIGN/IGN1, and inventory movements in OINM.
Does Business One support routings and capacity planning?
The standard production module is focused on BOMs and orders and has limited routing and capacity planning. Companies that need detailed scheduling or shop floor control usually add a partner solution.
What is backflush in SAP Business One?
It is an issue method on the BOM row that issues the component automatically when you post the receipt from production, based on the produced quantity, instead of manual issue before production.
Related
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-toSAP 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.
Error fixFix SAP Business One 'Quantity falls below zero' (-2028) on Production Issue
SAP Business One raises 'Quantity falls below zero' (ODBC -2028) when a goods issue, including an Issue for Production, would push an item's on-hand quantity in a warehouse, or a batch or serial, below zero and negative inventory is not allowed. Fix it by receiving the stock first, correcting the warehouse or batch, or deliberately allowing negative stock for the right items.
Error fixSAP 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 fixSAP 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 fixSAP 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 ERPAI 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 ERPAI 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
- SAP B1 Production Order Cost Variance CalculatorCompare actual to standard on a closed production order and see how much of the variance is material, labor rate and labor efficiency.
- SAP B1 Period End Close ChecklistA grouped month-end checklist for SAP Business One covering sub-ledgers, inventory, production, revaluation and locking the posting period.
- SAP Business One Production Order ChecklistA step-by-step checklist for creating, releasing, issuing to, receiving from and closing a production order in SAP Business One.
ERP fixes and how-tos
- Production standard cost in SAP Business One: how it works and where it stopsHow standard cost works for production orders in SAP Business One: valuation method, issue and receipt values, variances at close and process limits.
- SAP Business One production planning: MRP, production orders, cost and variancesSAP Business One production planning end to end: MRP, planned to released orders, cost rollup, variance reporting and when you need a manufacturing add-on.
- Fix SAP Business One 'Quantity falls below zero' (-2028) on Production IssueFix 'Quantity falls below zero' (-2028) when issuing to a production order in SAP Business One: causes, negative stock settings, backflush and posting dates.
Runs with your ERP
- CompuTec ProcessForce with SAP Business OneHow CompuTec ProcessForce extends SAP Business One with multi-level BOMs, routings, MRP, scheduling, quality and traceability, plus setup steps.
- ECOSIRE shop floor data collection with SAP Business One: operator clock-on and OEEHow ECOSIRE's shop floor terminal for SAP Business One records clock-ons, good and scrap quantities and OEE from routing standards, with setup and pitfalls.
- Ecosire quality control and inspection with SAP Business One: CoA, NCR and CAPAHow Ecosire's quality add-on for SAP Business One handles inspections, certificates of analysis, NCR and CAPA ageing and supplier quality reporting.
AI on your ERP
- AI for SAP Business One Purchasing, From Purchase Request to A/P InvoiceGround AI in SAP Business One purchasing: purchase requests, POs, goods receipts and A/P invoices via Service Layer, read-only, on-prem or private cloud.
- AI on SAP Business One for Electronics Manufacturers: BOMs, Shortages and TraceabilityPrivate AI on SAP Business One for electronics makers: multi-level BOM questions, component shortages, lot and serial traceability, RoHS and obsolescence checks.
Integrations
- How to add AI agents to SAP Business OneHow to put AI agents on SAP Business One: Service Layer tool design, read-only first, draft documents for human approval, and an on-prem model option.
- How to add WhatsApp to SAP Business OneHow to add WhatsApp to SAP Business One: Service Layer, Cloud API templates, opt-in rules, order status, delivery alerts and two-way replies into documents.