ERP Concepts and Data Flow
An ERP connector exchanges production records between your ERP and MachineMetrics. Live machine signals, such as execution state and part counts, come from your machine connection. They are separate from the connector's ERP sync.
Inbound Data
The records a connector imports depend on the ERP and configuration.
| Record | Purpose |
|---|---|
| Work order | Identifies what to make, the required quantity, and dates. |
| Work order operation | A step in a work order, with a sequence and assigned ERP resource. |
| Part and part operation | Describes the part and its manufacturing steps, including production standards. |
| Resource | An ERP machine, work center, or resource group. |
| Person | An ERP employee record linked to a MachineMetrics operator. |
| Reason | A code used to describe scrap, downtime, or other activity supported by the connector. |
| Labor ticket | A record of who worked on an operation, when, and with what quantities. Some connectors import these from the ERP. |
Use the Data Mapping Specification for field definitions. Use your connector guide for its supported records and filters.
Job Management Modes
| Mode | Where work is managed | Labor flow |
|---|---|---|
| ShopPulse | Operators manage work in the Operator View. | MachineMetrics sends labor to the ERP through the connector. |
| ERP Driven | Operators use their existing ERP process. | MachineMetrics imports ERP labor activity and associates it with machine data. |
Mode availability depends on the connector and account configuration. A connector's read-only setting and a machine's job management mode are different settings. Reading work orders alone does not establish ERP Driven job tracking.
For configuration, use MES Settings. For the ERP-managed workflow, use ERP Driven on MES Machines.
Resource and Operator Mapping
For MES machines, Record labor as identifies the ERP resource used for labor attribution. Schedule jobs as identifies the resources whose jobs appear in the machine's Dispatch Schedule. Both mappings are required before enabling MES. In ERP Driven mode, Record labor as must be an individual resource.
Configure these mappings in MES Settings. Link ERP employees to MachineMetrics operators through ERP Data Studio → Persons.
Sync Timing
Initial imports establish the records the connector needs. Later syncs bring in changes using the connector's own change tracking, filters, and history windows. Polling intervals, retry intervals, and supported historical ranges differ between connectors.
Live machine data can update while ERP data is waiting for its next sync. Check the connector's configuration rather than assuming a fixed delay for every integration.
Labor Ticket Write-Back
When labor first reaches the ERP is connector-specific. Some connectors create an open ERP ticket and close it later. Others send a completed record. Job selection and account configuration also affect when MachineMetrics sends the ticket to the connector.
For MES operator workflows, see ShopPulse on MES Machines. For the ERP-side result, use the Sync Behavior section in your connector guide.
Timesheets
A Timesheet records a person's clock-in/out session. A labor ticket records work on a job or activity. Ending a job does not necessarily end the person's session.
View sessions in ERP Data Studio → Timesheets. Timesheet synchronization is a separate connector capability from labor-ticket synchronization. See Timesheets for the fields, viewing and editing steps, and verified Epicor behavior.
Writing and Posting Are Separate
A successful write does not always mean the ERP has posted the transaction or updated costing and inventory. For example, SyteLine receives unposted job transactions, while Global Shop uses exchange tables and a separate middleware process. Confirm the ERP-side posting process during setup.