Infor SyteLine (On-Premises) Integration Guide
Connect an on-premises Infor SyteLine (CloudSuite Industrial) installation to MachineMetrics for bidirectional work order and labor tracking synchronization.
This guide covers on-premises SyteLine, where the connector talks directly to your SyteLine SQL Server database. If your SyteLine runs in the Infor Cloud and you connect through the Infor ION API Gateway, use the Infor CloudSuite Industrial (SyteLine) guide instead.
| Section | Description |
|---|---|
| Overview | Integration type and data flow summary |
| How It Works | End-to-end data flow explanation |
| Requirements | Prerequisites before setup |
| Step-by-Step Setup Guide | SQL Server account, permissions, and connection info |
| Configuration Options | Behavior settings applied during onboarding |
| After Setup | Verification steps |
| Troubleshooting | Common issues and solutions |
Overview
The MachineMetrics and Infor SyteLine (On-Premises) integration enables bidirectional data flow between your ERP system and the shop floor, synchronizing work orders, labor tickets, and production data in real time. Unlike the cloud connector, this integration reads and writes directly against your SyteLine SQL Server database from the MachineMetrics Edge Device.
Integration Type
| Attribute | Value |
|---|---|
| Direction | Bidirectional |
| Data Flow (Inbound) | Work orders, operations, resources, employees, parts, and reason codes from SyteLine → MachineMetrics |
| Data Flow (Outbound) | Labor tickets and work order progress from MachineMetrics → SyteLine |
| Runs On | MachineMetrics Edge Device (physical or Virtual Edge) |
| Connection Method | Direct connection to the SyteLine SQL Server database |
This connector is under active development. Some features may change, and certain capabilities may not be available at the time of reading.
How It Works
The connector runs as a service on your Edge Device (or Virtual Edge) and connects directly to your SyteLine SQL Server database, facilitating smooth two-way communication between SyteLine and MachineMetrics.
1. Management — Work Order Transmission
Active work orders are read from SyteLine and transmitted to MachineMetrics, making them available for operators in real time. The connector tracks changes incrementally (using each record's modified date), and a configurable historical start date controls how far back the initial backfill reaches.
2. Tracking — Labor and Progress Reporting
As operators work on orders within MachineMetrics via ShopPulse:
- Labor inputs generate labor tickets
- Work order progress updates in real time
- Accurate records are maintained automatically
3. Synchronization — Real-Time Updates
When an operator closes a labor ticket, the connector writes a job transaction (jobtran_mst) back to SyteLine. When enabled, the connector can also roll completed quantities and status up to the work order operation and the parent work order. Transactions are written in an unposted state by default — see Confirm Job Transaction Posting.
4. Scheduling — Dynamic Visibility
Shop floor managers and production planners gain instant visibility into:
- Work in progress status
- Schedule adherence
- Required adjustments
Changes to the schedule are immediately communicated to operators.
Requirements
Before starting the connection process, ensure that:
| Requirement | Details |
|---|---|
| MachineMetrics Edge | A physical or Virtual Edge Device to run the connector service. |
| On-Premises SyteLine | SyteLine (CloudSuite Industrial) hosted on a Microsoft SQL Server you control. |
| Network Access | The Edge device must have direct network access to your SyteLine SQL Server by IP address (typically TCP port 1433) and outbound internet access to the MachineMetrics APIs. Hostnames are not supported — the SQL Server must be reachable at a fixed IP. See the Network Requirements Guide for Edge connectivity requirements. |
| SQL Server Account | A dedicated SQL Server login with the table permissions described in Step 1. |
| SyteLine Configuration Values | The site, warehouse, and user code values used when writing labor tickets — confirm these with your SyteLine administrator. |
Step-by-Step Setup Guide
Setup consists of three steps: create a dedicated SQL Server account, confirm the SyteLine values used for labor-ticket write-back, and securely share the connection details with MachineMetrics.
Step 1: Create a Dedicated SQL Server Account
Create a dedicated SQL Server login with access to the SyteLine database. Grant the following permissions on the SyteLine database tables.
SELECT (read) permissions:
employee_mst -- Employees / operators
item_mst -- Items / parts
job_mst -- Work orders
job_sch_mst -- Work order schedules
jobroute_mst -- Work order operations (routing)
jobtran_mst -- Job transactions / labor tickets
jrt_sch_mst -- Routing schedule (run rates)
reason_mst -- Reason codes
wc_mst -- Work centers / resources
INSERT + UPDATE (write) permissions:
jobtran_mst -- Labor ticket write-back from ShopPulse
UPDATE permissions (only if work order roll-up is enabled — see Configuration Options):
jobroute_mst -- Roll completed quantity/status up to the operation
job_mst -- Roll completed quantity/status up to the work order
job_sch_mst -- Update the work order completion date
Grant read-only access first if you want to validate inbound work order sync before enabling labor write-back. Labor tickets cannot be written until the connector has INSERT/UPDATE on jobtran_mst.
Step 2: Confirm SyteLine Labor-Ticket Values
When the connector writes a labor ticket, several SyteLine-specific fields must match your site's configuration. Confirm these values with your SyteLine administrator before go-live — the connector has defaults, but they are installation-specific and not universally correct.
| Value | SyteLine field | Description |
|---|---|---|
| Site Ref | site_ref | The SyteLine site the labor ticket belongs to |
| Warehouse | whse | The warehouse written on the labor ticket |
| User Code | user_code | The SyteLine user code recorded on the transaction |
Step 3: Provide MachineMetrics with Connection Information
Gather the following and share them securely with your MachineMetrics implementation team:
| Value | Description | Example |
|---|---|---|
| SQL Server IP Address | The IP address of the SyteLine SQL Server. This must be an IP address — hostnames are not supported, because the Edge device cannot resolve internal DNS names on the customer network. | 192.168.1.100 |
| Database Name | The SyteLine database name | SyteLineDB |
| Username | The SQL Server login created in Step 1 | machinemetrics |
| Password | Password for that login | ******** |
| Site Ref / Warehouse / User Code | The values confirmed in Step 2 | — |
The SQL Server must be reachable at a fixed IP address — a static IP or a DHCP reservation. Hostnames are not supported, and if the server's IP changes the connector loses its connection until the new address is provided.
Security Tip: Use the MachineMetrics secure link sharing service at SnapPass or your company's secure file sharing to transmit credentials — do not send them by email.
Your MachineMetrics implementation team can help configuring the connector on the Edge Device using the values above, along with the behavior settings described in Configuration Options.
Configuration Options
The following behaviors are configured by your MachineMetrics implementation team during onboarding. They are listed here so you know what can be tuned to match your SyteLine environment and reporting requirements.
| Setting | Environment Variable | Description | Default |
|---|---|---|---|
| Job Filter Pattern (WO/WOO/LX) | ERP_LX_JOBFILTER | SQL LIKE pattern that restricts which jobs are imported (e.g. [A-Z]% for jobs starting with a letter) | No filter |
| Part Operations Job Filter | ERP_PART_OPS_JOB_FILTER | SQL LIKE pattern that restricts jobs used for part operations | No filter |
| Historical Start Dates | ERP_RESOURCES_HISTORICAL_START_DATEERP_PERSONS_HISTORICAL_START_DATEERP_REASONS_HISTORICAL_START_DATEERP_PARTS_HISTORICAL_START_DATEERP_WORK_ORDERS_HISTORICAL_START_DATE | Earliest date to backfill, set independently per entity (resources, persons, reasons, parts, and work orders) | 2022/01/01 |
| Polling Interval | POLL_INTERVAL | How often work orders are pulled from SyteLine | 5 min |
| Labor Tickets To ERP Interval | TO_ERP_INTERVAL | How often closed labor tickets are written back to SyteLine | 5 min |
| Retry Failed Labor Tickets Interval | RETRY_LABOR_TICKETS_INTERVAL | How often failed labor-ticket writes are retried | 30 min |
Calculate a_hrs | CALCULATE_A_HRS | Compute actual hours from operator clock in/out times | On |
| Set Completed Qty = Good + Bad Parts | SET_QTY_BAD_PLUS_GOOD_PARTS | Record completed quantity as good plus scrapped parts | On |
| Propagate Status to WO Operations (Roll-Up) | ERP_LX_DO_WORKORDER_ROLLUP | Roll completed quantity and status up to the operation and parent work order (requires the additional UPDATE permissions in Step 1) | Off |
| Assign Labor Tickets to Machine's Group | ERP_DO_RESOURCE_TO_GROUP | Write labor against a machine's group resource instead of the individual machine | On |
| Default Resource ID | MM_DEFAULT_RESOURCE_ID | Force a specific resource ID on outgoing labor tickets | Not set |
After Setup
Once the integration is configured:
- Work orders from SyteLine appear in MachineMetrics
- Operators select and start jobs via ShopPulse
- Labor data syncs back to SyteLine when tickets are closed
- Production Schedule Intelligence displays accurate job status
Verifying the Integration
- Go to Production → Schedule in MachineMetrics
- Confirm work orders from SyteLine are visible
- Have an operator start and close a job on their tablet
- Verify the labor ticket (
jobtran_mst) appears in SyteLine
Confirm Job Transaction Posting
The connector writes labor tickets to SyteLine in an unposted state — the same state SyteLine uses for labor entered through its own forms. The connector does not post transactions. Posting is a SyteLine-side responsibility and is what triggers material consumption, quantity roll-up, cost roll-up to WIP, and the corresponding general ledger entries. Until a transaction is posted, none of these effects happen.
Before going live, confirm how posting is handled in this environment (for example, a scheduled background task, a manual end-of-shift posting run, or a workflow-driven post).
Troubleshooting
| Issue | Possible Cause | Solution |
|---|---|---|
| Work orders not appearing | Database connection failed | Verify the SQL Server IP address, database name, credentials, and firewall rules between the Edge and SQL Server |
| Connection timeout | Firewall blocking the Edge, or the SQL Server IP changed | Ensure the Edge can reach the SQL Server IP (typically TCP 1433); if the server's IP changed, provide the new address |
| Missing tables or permission errors | SQL account permissions incomplete | Add the missing SELECT/INSERT/UPDATE permissions from Step 1 |
| Labor not syncing back | Missing jobtran_mst write permission, or ticket not yet closed | Confirm INSERT/UPDATE on jobtran_mst, and that the operator has clocked out |
| Roll-up not updating operations or work orders | Roll-up disabled, or missing UPDATE on jobroute_mst/job_mst/job_sch_mst | Enable roll-up and grant the additional UPDATE permissions from Step 1 |
| Labor written to the wrong site/warehouse | site_ref, whse, or user_code incorrect | Confirm the values from Step 2 with your SyteLine administrator |
| Only some jobs imported | Job filter pattern too restrictive | Review the Job Filter Pattern in Configuration Options |
| Transactions never take effect in SyteLine | Tickets remain unposted | Confirm posting is configured in SyteLine (see Confirm Job Transaction Posting) |
Related Articles
- Infor CloudSuite Industrial (SyteLine) — The cloud (ION API) SyteLine connector
- ERP Integration Guide — General ERP integration overview
- ERP Data Studio — Mapping work centers
- Production Schedule Intelligence — Using the schedule view
- ShopPulse Interface Guide — How operators interact with jobs
Getting Help
- Setup Assistance: Contact your MachineMetrics Solution Delivery Manager (SDM)
- Technical Issues: Email support@machinemetrics.com
- SyteLine Configuration: Consult your SyteLine administrator or Infor partner