SyteLine ION BOD Integration Go-Live Checklist
This checklist takes a BOD integration between SyteLine or CSI 10 on-prem and Infor ION from setup to hypercare. It suits CRM, WMS, EPM, localization and other ION connected applications that exchange BODs with SyteLine.
0 of 26 items complete
7 critical items still open - these are the highest-risk gaps.
Setup
Scope
Testing
Cutover
Hypercare
Critical items are the ones that stop BODs silently: triggers not regenerated after a rule change, logical IDs that do not match ION, master data loaded out of order, and no one watching the outbox after go-live.
Get your BOD scope reviewed
Send us the list of BODs in scope and receiving applications and we will check the setup and test plan against CSI 10.
Optional. The tool and every export work without this. No spam.
How to use it
Run Setup and Scope during build, Testing in each test cycle, and Cutover and Hypercare in the go-live plan. Treat each BOD in scope as its own row in the testing group: export to Excel and add one line per noun so you can see which have passed end to end. Keep the exported checklist as part of the integration runbook, because the same checks are what support uses when a flow stops months later.
Where this lives in SyteLine
Outbound BODs are generated through replication rules and categories, with triggers that must be regenerated on Replication Management after every change. Generated documents appear in Replication Document Outbox, inbound ones in the inbox, and the ION connection point exchanges them with ION. Inbound processing can be extended with application event handlers on BodPreReceive, BodOnReceive and BodOnReceiveFail. The Replication Tool on the utility server views, corrects and resubmits request documents.
- Replication Rules and categories: what generates BODs
- Replication Management: Regenerate Replication Triggers
- Replication Document Outbox: outbound BODs and Confirm BODs
- LogMonitor: replication and BOD processing errors
Version differences and gotchas
Regenerating triggers drops and recreates trigger code, so do it with users out of the database and separately at each site. A Confirm BOD in the outbox means SyteLine failed to process an inbound BOD and is reporting that error back, not that delivery succeeded. Whether processed BODs stay in the outbox depends on retention settings, so an empty outbox can mean success or a setting. The recommended master data load order depends on the receiving application, so take it from that application's integration guide.
How to check the result in the system
Change one record that should generate a BOD, then follow it: Replication Document Outbox in SyteLine, the document in ION OneView, and the record in the receiving application. For inbound, send one BOD, check the processed indicator and the SyteLine form, make sure no Confirm BOD was generated, and watch LogMonitor for errors. Repeat for the failure path.
Frequently Asked Questions
Does SyteLine have an ION API?
SyteLine exchanges business documents with ION as BODs, and its IDO REST endpoints can be exposed to external callers through ION API Gateway with OAuth2 service accounts. BODs suit event driven document flows between applications; the IDO API suits direct reads and method calls. Many integrations use both.
Why is no BOD generated after I change a replication rule?
Replication triggers must be regenerated on Replication Management after any change to rules or categories, and separately at each site. Until then the database triggers still reflect the old setup. Regeneration drops and recreates trigger code, so schedule it when no other users are logged in.
What does a Confirm BOD in the outbox mean?
A Confirm BOD in the SyteLine outbox is generated when SyteLine could not process an inbound BOD, and it carries the error back to the sender through ION. Open it to read the error, fix the data, setup or mapping, and have the document resent or resubmitted. During testing, keep processed BODs where your release allows it.
How do I handle inbound BOD failures in SyteLine?
Add an application event handler on BodOnReceiveFail to alert the integration owner, and use BodPreReceive to validate before processing; if a BodPreReceive handler fails, the BOD is not processed and BodOnReceive does not fire. Then use the Replication Tool to view, correct and resubmit the failed document.
If you want people to ask what happened to an order across SyteLine and connected applications in plain English on your own servers, we can build that layer.
Related Tools
SyteLine Multi-Site Replication Health Checklist
Configuration, data, service, queue and post-upgrade checks that keep SyteLine 9 and CSI 10 on-prem multi-site replication healthy.
Developer ToolsSyteLine Event System Troubleshooting Checklist
Checks for event handlers in SyteLine 9 and CSI 10 that do not fire, fire twice or hang, from event name and flags to runtime services and action outcomes.
Developer ToolsSyteLine IDO API Security Hardening Checklist
Accounts, transport, tokens, request hygiene and monitoring checks for exposing the SyteLine IDO request service (REST and SOAP) to integrations and scripts.
Infor SyteLineSyteLine Integration Complexity Calculator
Estimate build hours, testing effort, cost, and timeline for your SyteLine integration portfolio based on architecture and data volume.
Infor M3 & CloudSuiteInfor ION BOD Verbs and Nouns Reference for M3
Look up what each ION BOD verb does, common nouns used with M3, and key ION components in plain language.
More Infor SyteLine tools
See all- SyteLine Form Personalization Checklist
- SyteLine User Access Request Form Template
- SyteLine Custom Report Request Template
- SyteLine Data Conversion Mapping Worksheet
- SyteLine UAT Test Script Worksheet
- SyteLine Cutover Plan Worksheet
- SyteLine Change Request Form Template
- SyteLine Cycle Count Variance Worksheet
- SyteLine Database Growth Forecast Calculator
Keep exploring
Free tools
- SyteLine ION Outbound BOD ReferenceEvery outbound BOD SyteLine/CSI generates for ION, with verb, noun, the Infor applications Infor lists as receivers and the business area.
- SyteLine ION BOD Message Volume CalculatorEstimate how many outbound BODs SyteLine sends to ION per day, the peak rate per minute and the outbox storage if BODs are kept.
- SyteLine Go-Live Readiness ChecklistThirty expert checks across data, testing, people, technical, and cutover workstreams to tell you whether your SyteLine go-live is actually ready.
ERP fixes and how-tos
- SyteLine EDI or BOD inbound document fails to create a sales orderWhy an inbound EDI order or ION BOD fails to create a SyteLine sales order, and how to trace the failure through the EDI error log or ION BOD inbox to the root cause.
- How to Set Up an ION Workflow Approval for SyteLine Purchase OrdersHow to build an ION workflow approval for SyteLine purchase orders: trigger from a BOD, route to approvers by amount, and write the result back safely.
- How to Map and Transform a BOD in Infor ION ConnectHow to build a mapping in ION Desk between two BOD or message types, handle custom fields and lookups, test with the Monitor and fix common mapping errors.
Runs with your ERP
- XEDI EDI Integration with Infor LN (ION BODs)How XEDI translates X12 and EDIFACT into Infor BODs routed through ION for Infor LN, plus SyteLine and M3. Setup steps, data flows, pitfalls and FAQ.
- Infor WMS with Infor SyteLine: using an external warehouse applicationHow Infor WMS integrates with SyteLine as an external warehouse application over ION BODs, what moves between them, setup steps, pitfalls and simpler options.
- SPS Commerce Fulfillment with Infor SyteLine: EDI orders, ASNs and invoices over IONHow SPS Commerce Fulfillment exchanges orders, ASNs and invoices with Infor SyteLine using ION BOD XML. Also covers LN, M3 and VISUAL, with setup and pitfalls.
Guides
- SyteLine ION API Integration: The Complete GuideStep-by-step SyteLine ION API integration guide: API gateway setup, OAuth 2.0 tokens, BODs vs IDO endpoints, and secure on-prem to cloud connections.
- Infor ION BOD Message Processing GuideMaster Infor ION BOD message processing with document flow configuration, XML mapping, transformation rules, and error handling for CloudSuite integrations.
- Infor ION Connect Setup for SyteLine IntegrationConfigure Infor ION Connect for SyteLine data integration. Set up connection points, document flows, BODs, and ION API Gateway for CloudSuite Industrial.