A production order (Fertigungsauftrag) is the central transactional record authorising and tracking a specific production activity. The production order links the planning side (which product, how much, when) with the execution side (which resources, what process steps, actual results). For ERP-bearing manufacturers, production orders are the workhorse transactions of the shop floor — every production event ultimately ties back to a production order, and the order's data flow drives planning, costing, traceability and accounting.
Production-order structure
Each production order carries several layers of information. Header: order number, produced item, quantity, dates (planned start, planned finish, actual). Components: bill of materials with required quantities, allocated batches or serial numbers. Operations: routing steps with resources (machines, work centres), setup and run times, predecessor relationships. Status: lifecycle state (planned, released, in progress, completed, closed). Confirmations: actual quantities and times recorded against operations. Goods movements: component issues, finished-product receipts, scrap. Cost: planned versus actual cost by category (material, labour, overhead). Quality data: inspection results, batch attributes, certifications. Documents: drawings, work instructions, safety data sheets attached to the order.
Production-order lifecycle
Planned order — MRP-generated based on demand. No firm resource commitment
Firm planned order — planner converts to firm, freezing dates against MRP re-runs
Released — production order released to shop floor with all required components available; materials reserved or staged
In progress — operations execute, confirmations record progress, scrap and completed quantities
Technically complete — production finished; goods receipt to stock; minor cost adjustments still possible
Closed — all costs settled; variances posted to relevant cost-centres; order archived
Each transition produces accounting and inventory consequences. ERP automates much of this but the right configuration of cost flows, variances and batch-handling matters substantially.
Integration with MES and shop floor
Modern manufacturing rarely operates production orders purely within the ERP. Integration patterns. (1) ERP-only execution: small-scale operations track production-order progress directly in ERP using shop-floor data collection (manual entry, basic scanners). Suitable for operations under 50 operators. (2) MES-driven execution: ERP creates and releases production orders; MES owns execution with detailed sequencing, machine-state tracking, OEE metrics; results flow back to ERP at order-completion milestones. Standard for larger or more-automated operations. (3) Direct machine integration: production orders flow to PLC controllers and CNC machines via OPC UA or equivalent; machine output automatically confirms order progress. Common in high-automation facilities. The right pattern depends on operational scale, automation level and the value of real-time shop-floor visibility.
Best-practice considerations
Three patterns characterise mature production-order management. (1) Right-size order quantity: order quantities too small create excessive setup overhead; too large inflate WIP and tie up components. Economic lot-size calculations or constraint-driven sizing produce balanced outcomes. (2) Discipline release timing: orders released before all components are available block shop-floor capacity. Modern MRP integrates with available-to-promise checks to release only when executable. (3) Close orders promptly: production orders kept open beyond physical completion accumulate posting errors and distort variance analysis. Monthly close should include systematic review of open orders, with prompt closure of completed ones. Mature operations close orders within days of physical completion; weak operations sometimes carry orders open for months after production ended.
Production order versus process order — what is the difference?
SAP distinguishes them: production orders for discrete manufacturing (countable units assembled from BOMs); process orders for process manufacturing (recipes producing materials in continuous or batch processes). Most other ERPs use unified production-order concepts adaptable to both. The underlying difference reflects the discrete-versus-process manufacturing distinction.
How many production orders can ERP handle simultaneously?
Modern ERPs handle tens of thousands of open production orders without performance issues. For very high-volume operations (assembly-line production with thousands of orders per day), MES handles the operational granularity with the ERP tracking aggregate metrics. The performance limit is rarely the constraint; data-quality and process-discipline matter more.
What about batch versus continuous production?
Both are handled through appropriate production-order configuration. Batch production: clear start, defined quantity, definite end. Continuous production: ongoing operations with order-based reporting for accounting. Process ERPs (SAP S/4HANA Process Industries, Sage X3 Process, GUS-OS Suite) handle both patterns natively.
