Overview
Manufacturing operations generate data that business systems need. Every production order completed, every material consumed, every quality result recorded, every machine hour logged — this is the operational data that ERP systems need to maintain accurate inventory records, produce financial reporting, plan future production, and manage the supply chain that keeps the factory running. When this data flows automatically from production systems to the ERP, the business operates from current, accurate information. When it does not — when production supervisors manually enter yesterday's production counts into the ERP this morning, when material consumption is estimated rather than measured, when quality data stays in the quality system and never reaches the financial record — the ERP becomes an approximation of reality rather than a record of it.
ERP integration for manufacturing is the data plumbing that connects the production floor to the business systems that manage, plan, and report on what happens there. It eliminates the manual data entry that is the largest source of ERP data quality problems in manufacturing. It ensures that the ERP's inventory, production, and financial records reflect the actual state of the factory rather than the state that was manually reported. And it provides the data flows that enable the ERP-driven planning and scheduling that modern manufacturing operations depend on to reach the factory floor in time to affect what actually happens there.
We build manufacturing ERP integrations for production facilities using Exact Online, AFAS, SAP, and other ERP platforms alongside MES systems, SCADA systems, quality management systems, machine data collection, and the operational databases that production generates — designing the data flows that connect these systems correctly, handling the transformation logic that maps production data to ERP data structures, and building the reliability and monitoring infrastructure that makes these integrations trustworthy in a production environment.
What Manufacturing ERP Integrations Cover
Production order completion and reporting. The production order — the ERP's instruction to manufacture a defined quantity of a product — is the primary unit of coordination between the ERP and the factory floor. When a production order is completed, the ERP needs to know: how many units were produced, how many were scrapped, when production started and finished, which work centres were used, and what actual labour and machine time was consumed. This data drives inventory updates, actual cost recording, delivery schedule management, and the production performance reporting that manufacturing management requires.
Production order completion integration retrieves the actual production data from the MES, the SCADA system, or the machine data collection infrastructure where it is recorded at the point of production, and reports it to the ERP in the format and at the timing the ERP requires. The integration handles the mapping between the production system's work order references and the ERP's production order numbers, the unit of measure conversions that may differ between production tracking and ERP records, and the quality split between conforming and non-conforming production that the ERP needs for inventory and cost recording.
For Exact Online, production order completion data is posted through the Exact Online Manufacturing module API — updating the realised quantities, the actual material usage, and the production status that downstream processes depend on. For AFAS, production completion data integrates with the AFAS production module. For SAP, production order confirmation (CO15/CO11N) transactions are triggered by the integration from the production data source.
Material consumption recording. Manufacturing processes consume raw materials, components, and semi-finished goods. The ERP's inventory record needs to reflect actual material consumption — not the theoretical consumption from the bill of materials, which may differ from actual consumption due to scrap, substitutions, yield variation, and process adjustments. Accurate material consumption recording keeps the ERP's raw material and WIP inventory accurate, drives the reorder planning that prevents material shortages, and provides the actual material cost data that product costing requires.
Material consumption integration reads the actual consumption data from the production system — the MES, the weighing system, the material tracking database — and posts goods issues to the ERP for each material consumed against each production order. Consumption data that is captured automatically — from weighing systems, from barcode scanning at the point of consumption, from machine data that correlates with material usage — is more accurate and more timely than consumption data entered manually at shift end.
For complex manufacturing processes where consumption varies based on process conditions, consumption integration handles the variable consumption logic — applying the yield factors, the scrap allowances, and the process-specific consumption rules that the standard BOM does not capture.
Inventory and goods movements. Manufacturing operations generate inventory movements beyond the production order — materials moved between storage locations, finished goods transferred from production to the finished goods warehouse, semi-finished goods moved to an intermediate storage location between production stages. These movements need to be recorded in the ERP to maintain location accuracy and to support the lot traceability that many manufacturing operations require.
Inventory movement integration captures the physical movements recorded in the WMS or production system and posts the corresponding ERP goods movements — transfer orders, stock transfers, goods receipts — as they occur rather than in batched end-of-day updates. Real-time inventory accuracy reduces the production disruptions that occur when production planning is based on inventory records that do not reflect current stock positions.
Quality results and inspection data. Quality inspection results — dimensional measurements, chemical analysis, functional testing, visual inspection — need to reach the ERP for stock blocking of non-conforming material, for quality cost recording, and for the customer-facing quality documentation that some industries require. Quality integration reads inspection results from the quality management system or the measurement equipment data collection and posts quality usage decisions and inspection lot results to the ERP.
For SAP QM, quality inspection lot results are posted through the QM module integration. For ERP systems with simpler quality modules, quality decisions are reflected through stock movements — blocking non-conforming stock, releasing conforming stock, posting scrap. Quality integration ensures that the ERP's inventory reflects the quality status of stock without requiring quality inspectors to perform duplicate data entry in both the quality system and the ERP.
Labour and machine time recording. Actual production labour hours and machine hours — the data that feeds actual cost recording and capacity utilisation reporting — need to reach the ERP from the time recording systems where they are captured. Labour time recording integration reads confirmed work order times from the production time recording system and posts activity confirmations to the ERP's production orders.
For manufacturers using direct labour cost tracking, actual labour hours by work centre and by production order drive the standard cost variance analysis that manufacturing cost accounting requires. For manufacturers tracking machine capacity utilisation, actual machine hours by work centre feed the capacity planning that production scheduling depends on.
Production planning data synchronisation. ERP production planning — MRP/MPS runs that calculate what needs to be produced, when, and with what resources — produces production orders and planned orders that need to reach the factory floor. Planning data synchronisation pushes planned production requirements from the ERP to the production scheduling system, ensuring that the factory floor is working to the plan that the ERP has calculated rather than to an independently managed schedule that may conflict with ERP requirements.
The reverse data flow — actual production performance against plan, current machine availability, current work-in-progress status — feeds back to the ERP to support the re-planning cycles that maintain the production plan's accuracy as conditions change.
Cost and financial data. Manufacturing costs — material costs, labour costs, machine costs, overhead — are recorded in the ERP as production orders are confirmed. The actual cost data that production order completion integration delivers supports the standard cost variance analysis, the product cost calculation, and the manufacturing P&L reporting that financial management of manufacturing operations requires.
Cost integration handles the mapping between the production system's cost categories and the ERP's cost elements, the allocation of overhead costs to production orders based on the cost allocation rules the finance function defines, and the period-end closing entries that move WIP balances to finished goods and cost of sales.
ERP Platform Specifics
Exact Online. Exact Online's manufacturing module provides the production order, BOM, and work centre infrastructure that discrete manufacturers use. Integration with Exact Online manufacturing covers production order confirmation via the REST API, material consumption posting, quality result recording, and the synchronisation of production master data — BOMs, routings, work centres — between the production system and Exact Online. For Dutch manufacturers using Exact Online as their primary ERP, integration bridges the gap between the production data captured at machine level and the ERP records that financial reporting and planning depend on.
AFAS. AFAS Profit's production module handles production planning and production order management for the mid-market manufacturers that use AFAS as their integrated ERP and HRM platform. Integration with AFAS production covers order confirmation, material consumption, and the production performance data that AFAS reporting requires. AFAS REST API connectivity provides the integration interface for real-time data exchange rather than file-based batch updates.
SAP. SAP PP (Production Planning) and SAP ME (Manufacturing Execution) together constitute the ERP-side infrastructure for manufacturing integration in SAP environments. Integration with SAP manufacturing covers production order confirmation (CO15), goods issue posting (MIGO), quality inspection lot processing (QM), and the IDOc and BAPI interfaces that SAP exposes for production system connectivity. SAP environments often have the most complex integration requirements — multi-plant structures, complex BOM configurations, integrated quality management — and the integration design needs to handle this complexity correctly.
Other ERP platforms. For manufacturers using other ERP systems — Microsoft Dynamics, Oracle, Infor, or industry-specific ERP platforms — we design and build integrations against the API and data interfaces each platform exposes, applying the same principles of real-time data flow, transformation correctness, and integration reliability that Exact Online, AFAS, and SAP integrations require.
Integration Reliability in a Production Environment
Manufacturing ERP integrations operate in an environment with specific reliability requirements. Production cannot stop because an ERP integration has failed. The integration infrastructure needs to handle the failure conditions that production environments produce — network interruptions between production floor and server, ERP downtime for maintenance windows, production systems that are not always available for external connections — without losing data or requiring manual recovery.
Buffering and retry. Integration events that cannot be delivered to the ERP immediately — because the ERP is temporarily unavailable, because the network connection has been interrupted, because the ERP is processing a month-end batch — are buffered and retried when connectivity is restored. The buffer persists across restarts, ensuring that integration events are not lost if the integration service is restarted during a production run.
Idempotent processing. Production environments are not always predictable — a network interruption might mean that an integration event is delivered twice, or that the ERP acknowledges receipt but the acknowledgement is lost before it reaches the integration service. Idempotent processing ensures that delivering the same event twice produces the same result as delivering it once — preventing the duplicate postings that unreliable delivery can produce without idempotency protection.
Error handling and alerting. Integration errors — ERP validation rejections, mapping failures, connection timeouts — are caught, logged with the full context needed for diagnosis, and routed to the operational alerts that inform the ERP and production teams when an integration requires attention. Errors that can be automatically retried are retried. Errors that require manual correction — a production order reference that does not exist in the ERP, a material code that has not been created — are surfaced for resolution rather than silently dropped.
Monitoring and audit trail. Every integration transaction — the source data received, the transformation applied, the ERP request sent, the ERP response received — is logged with the timestamp and the processing outcome. The audit trail supports the investigation of ERP data quality issues, confirms that integration events have been processed, and provides the evidence for the reconciliation of production system data against ERP records.
Master Data Synchronisation
ERP integrations depend on master data being consistent across the systems they connect. A production order in the MES that references a work centre code that does not exist in the ERP, or a material consumption record that uses a material code that the ERP cannot resolve, will fail at the ERP posting stage. Master data synchronisation keeps the reference data consistent:
Material master synchronisation. Material codes, descriptions, units of measure, and the material classifications that production systems need to reference ERP materials are synchronised from the ERP to the production system. New materials created in the ERP are propagated to production systems. Material master changes — unit of measure changes, description updates, status changes — are reflected in the production system without requiring dual maintenance.
BOM and routing synchronisation. The bill of materials and the production routing that the ERP maintains as the standard for production execution are synchronised to the MES or production scheduling system. Engineering changes — new BOM versions, routing changes, work centre reassignments — flow from the ERP change management process to the production system, ensuring that the factory floor is working to the current engineering standard.
Work centre and resource synchronisation. Work centre definitions, capacities, and cost rates maintained in the ERP are synchronised to the production scheduling and capacity planning systems that use this data for scheduling decisions.
Technologies Used
- Rust / Axum — high-performance integration data processing, transformation engine, buffering and retry infrastructure
- C# / ASP.NET Core — ERP API client implementations, SAP BAPI and IDoc connectivity, complex manufacturing data transformation
- SQL (PostgreSQL, MySQL, SQLite) — integration event buffer, transaction audit trail, master data cache, error records
- Redis — integration state management, retry queue, real-time monitoring
- Exact Online REST API — Exact Online manufacturing module integration
- AFAS REST API — AFAS production module integration
- SAP BAPI / RFC / IDoc — SAP production, quality, and inventory integration
- OPC UA / MQTT — production system connectivity for machine-level data sources
- REST / Webhooks — MES, QMS, and production system API integration
- SMTP / Slack — integration error alerts and operational monitoring notifications
The ERP Data Quality Problem in Manufacturing
The root cause of ERP data quality problems in manufacturing is almost always the same: the ERP's records are maintained by people entering data manually rather than by systems capturing it automatically. Manual data entry introduces errors, introduces delays, and is selectively performed — the records that seem important get updated, the records that seem routine are deferred. The result is an ERP whose inventory records do not match physical stock, whose production records do not match actual output, and whose cost records are based on estimates rather than measurements.
ERP integration that captures production data automatically at the source eliminates these problems at their root. The integration does not forget to post a goods issue. The integration does not round consumption figures to make data entry faster. The integration posts production completions as they happen rather than at the end of the shift when the supervisor has time. The ERP's records reflect reality because the integration is connected to the systems that measure reality.
Connect the Factory Floor to the Business
The value of an ERP depends on the accuracy of its data. The accuracy of manufacturing ERP data depends on the quality of the connection between the production floor and the ERP. Integration built correctly — with reliable data flows, correct transformations, and the monitoring that surfaces failures before they affect business operations — is the infrastructure that makes the ERP's manufacturing modules deliver the value they are designed to provide.