SYSPRO API integration: e.net business objects, REST, EDI and Office

Choose and build a SYSPRO integration

1. 1Write down the job: direction (in, out, both), volume, latency and who triggers it.
2. 2Use the table below to pick between business objects, web services, EDI, Office integration or direct read-only SQL.
3. 3Create a dedicated integration operator in SYSPRO with only the program rights the objects need.
4. 4Start with a query object (for example INVQRY or ARSQRY) to prove logon and parameters, then move to a transaction object such as SORTOI.
5. 5Build the XML parameters and document from the object's published schema, and validate before you send.
6. 6Handle the XML result: check for error nodes, log the full response and make writes idempotent so a retry cannot create duplicates.
7. 7Test in a copy company with realistic data, including bad input.
8. 8Monitor the integration operator, the service and failures after go-live.

How an e.net call works

<!-- sketch of a document for a sales order object, not complete -->
<SalesOrders>
  <Orders>
    <OrderHeader>
      <CustomerPoNumber>PO-1001</CustomerPoNumber>
      <Customer>CUST001</Customer>
    </OrderHeader>
  </Orders>
</SalesOrders>

Common pitfalls

• !Writing directly to SYSPRO tables instead of using business objects.
• !Logging on and off for every transaction, exhausting licences and time.
• !Using a personal operator for an unattended integration.
• !Ignoring error nodes in the XML and assuming success.
• !No idempotency key, so a retry creates a duplicate order.