Free tool
ERP Integration and EDI Designer
Pick business objects and target systems and get the ERP's real interface for each flow (BODs, IDocs, APIs, open interface tables, EDI documents), a field-level starter map and effort notes.
Pick customers, items, orders, shipments, invoices and the rest, choose the system on the other side (Salesforce, Dynamics, a web store, an EDI trading partner, WMS, MES, PLM or a data warehouse) and get a design you can hand to a developer or an integration partner.
Choose your ERP
7 interface types, 12 EDI documents
Infor SyteLine (CloudSuite Industrial)
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.
7 interface types, 16 EDI documents
Infor LN (and Baan)
LN publishes BODs to Infor ION from business events and from initial load sessions such as Publish Logistic Master Data (tcbod0200m000); BOD Parameters (tcbod0100m000) control publishing, schema version and inbound routing errors. Synchronous calls use LN OData REST APIs or BDEs through the ION API gateway; EDI runs through the BEMIS flat file standard and a third-party translator.
8 interface types, 12 EDI documents
Infor M3 (formerly Movex)
Outbound M3 BODs start as table events: Event Analytics rules filter them, the BOD Processor enriches them and Event Hub hands them to Infor Enterprise Collaborator (IEC), which publishes to ION. Each BOD must be enabled per company and division in BOD Processor Administration. Synchronous calls use MI programs through the ION API gateway at /M3/m3api-rest/v2/execute with OAuth 2.0.
7 interface types, 12 EDI documents
JD Edwards EnterpriseOne
JD Edwards EnterpriseOne exposes synchronous integration through the AIS Server (REST: orchestrations, form service, data service, business function service) and the Business Services Server (SOAP published business services). Outbound events come from real-time events on the Transaction Server, and batch flows use Z file interoperability tables and the EDI interface tables (F47xxx) processed by UBEs.
7 interface types, 12 EDI documents
SAP ECC (ERP Central Component)
SAP ECC 6.0 runs on SAP NetWeaver AS ABAP. Asynchronous integration uses IDocs (ALE between SAP systems, EDI to trading partners) driven by output determination or change pointers; synchronous integration uses BAPIs and RFC function modules, or OData services built in SAP Gateway. Most landscapes put SAP PI/PO or SAP Integration Suite (Cloud Integration) in the middle, with the SAP Cloud Connector for cloud to on-premises calls. Mainstream maintenance for SAP ERP 6.0 runs to the end of 2027, with optional extended maintenance to the end of 2030.
8 interface types, 12 EDI documents
SAP S/4HANA (on-premise and private cloud)
S/4HANA offers three main integration surfaces: IDocs over ALE or EDI (partner profiles in WE20), released synchronous OData APIs and SOAP services published on the SAP Business Accelerator Hub, and business events for change notifications. Middleware is usually SAP Integration Suite (Cloud Integration) or an existing SAP Process Orchestration 7.5 system; any iPaaS that speaks OData, SOAP or IDoc can also connect.
7 interface types, 15 EDI documents
Oracle E-Business Suite (EBS 12.2)
Oracle EBS has no single message bus. Batch inbound loads use open interface tables plus a concurrent import program; synchronous calls use public PL/SQL APIs deployed as SOAP or REST services through Integrated SOA Gateway; outbound events come from the Workflow Business Event System; EDI runs through e-Commerce Gateway flat files and a third-party translator. Every API call runs under an EBS user and responsibility, and multi-org data needs the operating unit (ORG_ID).
11 interface types, 10 EDI documents
Oracle NetSuite
NetSuite is multi-tenant SaaS with no database access, so every integration goes through SuiteTalk REST web services (records and SuiteQL), RESTlets, SuiteScript, CSV import or read-only SuiteAnalytics Connect. Oracle plans to disable all SOAP web services endpoints with the 2028.2 release, and from 2026.1 new integrations should use REST with OAuth 2.0. Throughput is capped by the account Integration Concurrency Limit, set by service tier and SuiteCloud Plus licenses.
9 interface types, 10 EDI documents
Epicor Kinetic (formerly Epicor ERP 10)
Kinetic exposes every business object, process, report, BAQ and Epicor Function through the Open REST API (OData v4), so most integrations read with BAQs and write through BO services or Functions. Epicor sells two iPaaS options, Epicor Automation Studio (powered by Workato) and Epicor Integration Cloud (powered by Jitterbit), and Epicor EDI for trading partners; Kinetic is moving from semi-annual releases toward a monthly CI/CD cadence starting with the May 2026 release (2026.100), so plan regression tests for every interface.
7 interface types, 11 EDI documents
SYSPRO ERP (SYSPRO 8)
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.
What it gives you
- An integration inventory table with the method and the exact artifact per flow, ready for a design document.
- Method rationale: event or API, synchronous or asynchronous, and where the delivered interface stops.
- A field-level starter map per object with keys and required fields, where you can type the target field names.
- EDI mode: X12 850, 855, 856, 810, 846 and the EDIFACT equivalents mapped to the ERP documents, segment by segment.
- Effort and risk notes, plus export to PDF, Excel, Word or CSV and an optional engineer review.
Questions
What does the Integration and EDI Designer produce?
An integration inventory: one row per object, target and direction with the ERP interface to use (for example an ION BOD, an SAP IDoc type, a JD Edwards AIS call or an Oracle EBS open interface table), why it fits, a relative effort score and risks. It also gives a field-level starter map per object and, in EDI mode, segment-level notes for X12 and EDIFACT documents.
Which ERPs are covered?
Infor SyteLine (CloudSuite Industrial) is available now. Infor LN, Infor M3, JD Edwards EnterpriseOne, SAP ECC, SAP S/4HANA and Oracle E-Business Suite pages are added as their interface data is verified against vendor documentation.
Are the interface names real?
Yes. BOD nouns, IDoc types, tables and API paths come from vendor documentation, listed under Sources on each ERP page. Where a name could not be confirmed for every release, the tool says verify with vendor.
Do I need an account?
No. Everything works and exports without signing in. A free account lets you save the design and reopen it on another device.
Is the effort score an estimate I can quote?
No. It is a relative planning heuristic based on object complexity, direction, frequency, method and target, useful for comparing interfaces and sequencing work. For a real estimate, send the design for an engineer review.