Free tool for SYSPRO ERP (SYSPRO 8)

SYSPRO ERP Integration and EDI Designer

Pick the business objects and the systems you need to connect, and get a SYSPRO integration inventory that names the real interface for each flow: e.net Solutions business objects such as SORTOI, PORTOI and ARSSCS called through the e.NET Communications Load Balancer, Document Flow Manager contracts for file and XML drops, read-only SYSPRO OData, or the Interface module EDI files. Switch to EDI mode to see how X12 850, 855, 810 and 830 (and the EDIFACT equivalents) map to the SYSPRO EDI record layouts, field position by field position.

Business objects

Toggle what moves between systems. Presets add a typical set.

Targets, direction and frequency

Direction is seen from SYSPRO.

Nothing in scope yet

Pick an object or a preset in step 1.

Integration inventory

All writes into SYSPRO go through e.net Solutions business objects (XML in, XML out) called through the Syspro 8 e.NET Communications Load Balancer over net.tcp, SOAP or its REST binding, or through Document Flow Manager contracts. Reads can use query business objects or the read-only Syspro OData service, which is the only data access path on Syspro Cloud ERP. SYSPRO has no outbound message bus; events leave through Trigger Program Setup, e.net Solutions triggers or Event Management.

Your inventory appears here

Each interface gets the SYSPRO method, the exact artifact and a relative effort score.
Free, optional. Reopen it on any device.
Download the design:

Exports include the inventory, rationale, field maps with your target names, selected EDI maps and risks. No sign-in needed.

How to use it

  1. 1

    Pick the objects

    Select the business objects in scope, such as customers, stock codes, sales orders and dispatch notes.

  2. 2

    Add the target systems

    For each object choose the system on the other side, the direction seen from SYSPRO and how often it must move.

  3. 3

    Read the inventory

    Each row names the SYSPRO interface (business object, DFM contract, OData entity, trigger or EDI program), why it fits and what to watch for.

  4. 4

    Check the field map

    Open the starter map for an object, fill in the target field names and note the keys and required fields.

  5. 5

    Export or save

    Download the design as PDF, Excel, Word or CSV, save it to your account, or send it to an engineer for review.

SYSPRO interfaces in this tool

e.net business objects (Load Balancer) synchronous
Logon returns a 34-character UserID, then Query (Query, Browse, Fetch), Setup (Add, Update, Delete) or Transaction (Build, Post) calls pass XML to a six-character business object such as SORTOI. Same validation, security and settings as the SYSPRO program. The installer lists Load Balancer ports 31001 (SOAP) and 31002 (REST); check SYSPRO.8.enet.Communications.exe.config for the bindings in use.
Document Flow Manager (DFM) asynchronous
Contracts tell the Syspro 8 Document Flow Manager Folder Poller which folder and file type to watch; the Queue Poller transforms the file with XSLT, calls the business object named on the contract, and writes the result or a failed set (e, s and t files). Licensing DFM covers all business objects called through it.
Syspro OData (read only) synchronous
OData 4.0 service hosted in IIS over HTTPS with basic authentication for flagged OData operators. Exposes company and system-wide tables and Business Activity Queries for reads; no writes. Licensed as an OData site license or through a Managed Run Time Product.
Triggers and Event Management asynchronous
Trigger Program Setup fires up to nine programs per trigger point (for example After sales order added in IMP040) and passes the key to a custom program or any application. e.net Solutions triggers do the same for business object calls. Event Management watches field values and can email, run a program or write to the inbox.
Interface module EDI files asynchronous
Fixed-width ASCII files in a SYSPRO-defined layout (not X12 or EDIFACT): Sales Order Import, Blanket Sales Order Releases Import, Purchase Order Export, Purchase Order Confirmation Import and Invoice, Credit & Debit Note Export. A translator converts partner X12 or EDIFACT to and from these layouts.
Import Master Data (IMPIMP) asynchronous
Spreadsheet templates loaded through Setup class business objects to add, update or delete master data. Suits one-off and periodic bulk loads, not live integration.
Direct SQL read (not advised) asynchronous
SYSPRO advises against connecting to its databases with SQL drivers: it affects performance, licensing and upgrades, and Syspro Cloud ERP does not allow it. Use OData or query business objects instead; keep any on-premises SQL to read-only reporting.

Questions

How does a SYSPRO e.net business object call work?

You log on to e.net Solutions with an operator, password and company and receive a 34-character UserID (a 32-character GUID plus instance and user type digits). Each call passes that UserID, the business object name and XML: query objects take one XML string, setup and transaction objects take a parameter string and a document string. Methods are Query, Browse, Fetch, NextKey and PreviousKey for queries, Add, Update and Delete for setup, and Build and Post for transactions. Log off at the end to release the session in AdmState.

Does SYSPRO have a REST API?

The Syspro 8 e.NET Communications Load Balancer hosts a REST binding next to net.tcp, basic HTTP and WS HTTP; the installer lists 31001 as the SOAP port and 31002 as the REST port, and the base address and binding ports are set in SYSPRO.8.enet.Communications.exe.config. It calls the same business objects as the other bindings. Syspro OData is a separate, read-only REST service. SYSPRO's October 2023 connectivity best practice article said it was investigating a web-based REST endpoint for ISVs; check the WCF Services Feature Guide for your release before you build on REST paths.

How does SYSPRO handle X12 EDI?

SYSPRO does not read X12 or EDIFACT directly. The Interface module imports and exports fixed-width ASCII files in a SYSPRO layout: Sales Order Import (ORDERS), Blanket Sales Order Releases Import (RELCUM), Purchase Order Export, Purchase Order Confirmation Import and Invoice, Credit & Debit Note Export (INVCRN). A translator converts partner documents to those layouts. Other documents, such as an 856 ASN or a supplier 810, need a custom extract or a translator that writes XML for a Document Flow Manager contract.

How are e.net business objects licensed?

Business objects are grouped into functional areas, and each functional area is licensed for a number of users in LICENSE.XML; the matching SYSPRO module must also be licensed. A named user gets one concurrent e.net logon. A guest or anonymous operator lets many people share one operator code, with a concurrent count measured over a 30-minute window. Certified ISV partners use Run Time Product licenses that pass a product code at logon. Licensing Document Flow Manager covers all business objects called through DFM.

Can I read the SYSPRO SQL database directly?

SYSPRO advises against it: direct SQL connections affect performance, licensing and upgrades, because version-specific tables and columns tie a solution to a release. Syspro Cloud ERP does not allow direct database access at all. Use query business objects when you need business rules applied (tax, ageing, currency, discounts) and Syspro OData for raw table reads.

How do I get events out of SYSPRO when a record changes?

There is no outbound message bus. Trigger Program Setup fires on trigger points such as After sales order added (IMP040), After dispatch note added (SORPS3) or After stock code changed (INVPST), and can run a custom program or any application with the record key on the command line; up to nine programs run per trigger. e.net Solutions triggers do the same for business object calls, and Event Management watches field values. Most integrations combine a trigger with a query business object, or poll OData.

Why does a Document Flow Manager file sit in the folder or fail?

Check that the contract is enabled and polls the right folder and file type, that the Folder Poller and Queue Poller services are running, and that the service account can read and delete files there. Failed documents are written in triplicate to the failed folder: the e file holds the error, s the original document and t the document after XSLT. DFM status codes 97, 98 and 99 show whether pre-processing, post-processing or the transform failed.

Which SYSPRO release should an integration target?

SYSPRO 8 help sets run from 2018 R1 to 2021 R2 (two releases a year), then annual 2022, 2023, 2024 and 2025 releases, and 2026 R1 and 2026 R2. Business objects are version independent: an application that logs on, calls ARSSCS and logs off keeps working across upgrades. Applications must call the e.net service endpoint; SYSPRO 8 is 64-bit and ENCORE.DLL is no longer available.