Free tool for Infor SyteLine (CloudSuite Industrial)

SyteLine Integration and EDI Designer

Pick the business objects and the systems you need to connect, and get a SyteLine integration inventory that names the real interface for each flow: ION BODs such as Sync.SalesOrder or Process.ItemMaster, the Mongoose IDO REST API, or the delivered EDI module with its translator flat files. Switch to EDI mode to see how X12 850, 855, 856 and 810 (and the EDIFACT equivalents) land in SyteLine, record type by record type.

Business objects

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

Targets, direction and frequency

Direction is seen from SyteLine.

Nothing in scope yet

Pick an object or a preset in step 1.

Integration inventory

SyteLine runs on the Infor Mongoose framework. Asynchronous integrations use ION and OAGIS BODs published from the Replication Document Outbox; synchronous calls use IDOs through the IDO REST API, the IDO web service or IDO Request XML. On CloudSuite (multi-tenant) external calls go through the ION API gateway with OAuth 2.0.

Your inventory appears here

Each interface gets the SyteLine 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, items, sales orders and shipments.

  2. 2

    Add the target systems

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

  3. 3

    Read the inventory

    Each row names the SyteLine interface (BOD, IDO or EDI document), 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.

SyteLine interfaces in this tool

ION BODs asynchronous
SyteLine publishes Sync and Process BODs on business events (order entry, invoice posting, master data changes) and accepts a defined set of inbound BODs. ION Connect routes them through connection points and document flows.
IDO REST API (Mongoose REST v2) synchronous
Generic endpoints under /IDORequestService/ido: GET /load/{ido} with properties, filter, orderby and recordcap; POST /update/{ido} with a Changes array (Action 1 insert, 2 update, 4 delete); POST /invoke/{ido}?method= for IDO methods. Business logic in the IDO runs on every call.
IDO web service / IDO Request XML synchronous
The older SOAP surface at /IDORequestService/IDOWebService.asmx and IDO Request XML over HTTP. Still supported and common in existing on-premises integrations; new builds usually prefer REST.
IDO extension class (.NET) synchronous
Custom .NET code attached to an IDO that calls an external web service when SyteLine data changes. Use it for synchronous outbound calls that no BOD covers, and keep the code small and logged.
SyteLine EDI module asynchronous
Delivered EDI for demand (customers) and supply (vendors). A third-party translator converts X12 or EDIFACT to flat ASCII files; the EDI Transaction Load Routine imports them into the edi tables and the EDI Transaction Unload Routine writes outbound files.
Read-only SQL (on-premises) asynchronous
On-premises only: read the site-aware views or a replica for reporting extracts. Never write to _mst tables; direct updates bypass IDO logic and the audit trail. Not available on multi-tenant CloudSuite.
Infor Data Lake (CloudSuite) asynchronous
On CloudSuite, BODs routed through ION can be stored in Infor Data Lake for analytics. Confirm which BODs your tenant publishes to the lake before you design reports on it.

Questions

What is the difference between ION BODs and the IDO REST API in SyteLine?

BODs are asynchronous XML messages that SyteLine publishes on business events (for example Sync.SalesOrder when an order changes) or accepts from other systems (for example Process.SalesOrder). ION routes and stores them, so they suit event feeds and high volume. IDO REST is synchronous: you call /IDORequestService/ido/load, update or invoke and get an answer immediately, which suits lookups, price checks and writes that need the new record number back.

Which BODs can SyteLine receive?

The delivered inbound list includes Process.SalesOrder, Process.ItemMaster, Process.CustomerPartyMaster, Process.ShipToPartyMaster, Process.BillOfMaterials, Process.ProductionOrder, Process.Quote, Process.Requisition, Process.ChartOfAccounts, Sync.Shipment, Sync.ReceiveDelivery, Sync.InventoryAdjustment, Sync.InventoryCount, Sync.EmployeeTimesheet, Sync.PlanningSchedule, Sync.ShipmentSchedule and Load.SupplierInvoice, among others. Anything outside that list needs IDO REST or a custom BOD handler.

How does SyteLine EDI work with a translator?

SyteLine does not parse X12 or EDIFACT itself. A translator converts partner documents to flat ASCII files, the EDI Transaction Load Routine loads them into the edi tables, and validation runs against the EDI Customer Profile or EDI Vendor Profile. Clean transactions post automatically when Auto-Post is set to Inbound or Both. Outbound documents are unloaded to flat files that the translator turns into X12 or EDIFACT and sends over the VAN or AS2.

Which EDI documents does SyteLine support out of the box?

Demand side: inbound 850 (ORDERS), 830 (DELFOR) and 862 (DELJIT), outbound 855 (ORDRSP), 856 (DESADV) and 810 (INVOIC). Supply side: outbound 850, 830 and 862 to vendors, inbound 855, 856 and 810 from vendors. Documents such as the 846 inventory advice or 860 PO change are not in the delivered list and need a custom extract.

How do I call the SyteLine REST API on CloudSuite?

Calls go through the ION API gateway. Register a backend service in ION API to get the .ionapi credentials, obtain an OAuth 2.0 bearer token, and send it with the X-Infor-MongooseConfig header that names your configuration. The paths are the same Mongoose REST v2 paths, for example GET /ido/load/SLItems?properties=Item,Description&recordcap=100.

Can I write directly to SyteLine SQL tables for an integration?

No. Inserts or updates to _mst tables bypass IDO validation, triggers and the audit trail, and Infor support will not stand behind data created that way. Multi-tenant CloudSuite does not allow direct SQL at all. Use IDO REST, BODs or the EDI module, and keep SQL to read-only reporting on premises.

Why does my inbound Process.SalesOrder BOD fail on a missing customer or item?

BODs are processed independently, so master data must exist first. Infor documents a load order: AccountingEntity, FinancialCalendar, AccountingChart and ChartOfAccounts, then master data such as CodeDefinition, Location, CustomerPartyMaster, ItemMaster and the party masters, then transactions. Check the Confirm BOD in ION for the exact validation message.

How do I stop SyteLine from publishing BODs nobody uses?

Open the Replication Categories form, filter on the ESB category and set the Skip Method on the trigger record for each BOD you do not need. SyteLine can generate hundreds of BODs per day, so turning off unused ones reduces ION traffic and Replication Document Outbox volume.