Week 4 of 8

ION, BODs and integrations

Infor applications talk to each other and to everyone else through ION. Most messages are BODs: an OAGi-standard noun such as SalesOrder or ItemMaster, plus a verb such as Sync or Process. ION OneView tracks each document and shows every component it passed through.

Integrations are also where budgets slip. In Panorama’s 2026 ERP Report, more than a quarter of organizations went over budget, and the most common reason was an unexpected need for additional technology.

This week: inventory every flow and test the error path

List every ION document flow and API integration: BOD noun and verb, source and target, trigger, daily volume, monitoring and cutover action.
Give each one an internal owner and a partner contact, and book partner test windows for SIT 1 now.
Write at least a positive, a negative and an error-BOD test for each flow. Add volume tests for high-volume and financial flows.
Make an ION OneView reference the required evidence for every executed test. A flow is ready only when it passed in SIT 2 and the final mock.

Number of the week

1 in 4+

organizations exceeded their ERP budget; unexpected additional technology was the top reason.

Source: Panorama Consulting, The 2026 ERP Report

Use this week

Infor ION & BOD Integration Test Tracker →
Nine example flows with BOD noun and verb, owners, test types, OneView evidence and a Ready flag.
SIT Cycle Plan & Entry/Exit Criteria →
End-to-end scenarios that cross integrations, with a daily burn-down.

Next week: the data you migrate is under test too. Rehearse it, reconcile it, sign it.

Get the playbook in your inbox, one week at a time

Subscribe free and every template in the library is yours.