Infor M33 min readNetray Engineering TeamPublished February 14, 2026

Infor ION Integration Patterns for M3: BODs, ION Connect, and Event-Driven Architecture

Short answer

Infor ION is the integration backbone that connects M3 to other Infor applications (d/EPM, Optiva, PLM), third-party systems, and cloud services. ION uses Business Object Documents (BODs) as the canonical message format, enabling loosely coupled integrations that survive application upgrades. Understanding ION's document flow model, connection point configuration, and event-driven patterns is essential for every M3 architect building a connected enterprise.

BOD Architecture and M3 Document Flows

ION communications are built on OAGIS-based Business Object Documents (BODs). CustomerPartyMaster when customers are updated in CRS610. Subscribing applications receive these BODs through ION connection points, enabling real-time data synchronization without point-to-point interfaces.

Configure M3 BOD publisher in MNS860 for key document types: ItemMaster, PurchaseOrder, SalesOrder, ChartOfAccounts
Map M3 fields to BOD elements using ION Desk mapping tools for custom field extensions beyond standard BOD coverage
Set up BOD subscription filters in ION to route documents by M3 company (CONO), division (DIVI), or custom attributes
Enable BOD acknowledgment tracking (ConfirmBOD) for critical integrations requiring guaranteed delivery
Monitor ION document flow health in ION Desk: throughput rates, failed deliveries, and processing latency metrics

ION Connect, API Gateway, and Third-Party Integration

ION Connect enables non-Infor applications to participate in the ION message fabric. Connection points for REST APIs, SOAP services, flat files, and database tables allow any system to publish and subscribe to BODs. The ION API Gateway provides OAuth2-secured REST endpoints for M3 MI programs, enabling modern web and mobile applications to interact with M3 without MvxAPI dependencies.

Third-party integrations use ION Connect for Salesforce, Workday, and e-commerce platform connectivity.

Configure ION Connect file-based connection points for legacy system flat file integration (CSV, XML, fixed-width)
Set up ION API Gateway endpoints for M3 MI programs with OAuth2 client credentials and JWT token validation
Use ION Connect REST connection points for real-time integration with Salesforce, Shopify, and WMS platforms
Implement ION data lake integration for M3 transactional data export to analytics and BI environments
Configure ION Connect database connection points for direct table-level integration with non-M3 databases

Event-Driven Workflows and ION Process Automation

ION's workflow engine enables event-driven process automation triggered by M3 business events. When a purchase order exceeds a threshold in PPS200, ION can route an approval workflow to the procurement manager. When inventory drops below safety stock in MMS100, ION triggers a replenishment notification.

These event-driven patterns replace scheduled batch processes with real-time responses, reducing reaction time from hours to seconds.

Design ION workflows triggered by M3 BOD events: approval routing, notification chains, and escalation paths
Configure ION alert rules for threshold-based monitoring: credit limit breaches, inventory exceptions, delivery delays
Implement multi-step approval workflows: PO approval, customer credit override, price exception authorization
Use ION workflow tasks for human-in-the-loop processes with mobile-friendly approval interfaces
Monitor ION workflow execution: completion rates, average cycle time, bottleneck identification by approval step

Try it here, free

ERP Integration Diagram Template: Inbound and Outbound Interfaces

Open full tool

Fill in your ERP and connected systems to generate an integration map with inbound and outbound interface tables, flow notes and an owner register.

Fill in

Company

ERP system

MES / shop floor system

WMS / warehouse

PLM / engineering

EDI / B2B provider

CRM / quoting

BI / reporting

Integration layer

Owner / reviewer

Date

Live preview

Free, optional. Reopen it on any device.

Download:

ERP Integration Diagram Template: Inbound and Outbound Interfaces

Integration overview

Company: Harlow Metal Products Core system: Infor SyteLine (on-prem) Integration layer: Integration server with REST and file adapters Owner: IT manager Date: 2026-11-01

Direction key: Inbound means data enters Infor SyteLine (on-prem). Outbound means data leaves Infor SyteLine (on-prem).

Context diagram (text)

[ PLM with released BOMs and drawings ] --releases items, BOMs, ECOs--> [ Integration server with REST and file adapters ] --> [ Infor SyteLine (on-prem) ] [ EDI VAN with X12 850, 855, 856, 810 ] --customer orders, ASNs in/out--> [ Integration server with REST and file adapters ] <--> [ Infor SyteLine (on-prem) ] [ CRM and quoting tool ] --quotes, customers--> [ Integration server with REST and file adapters ] --> [ Infor SyteLine (on-prem) ] [ Infor SyteLine (on-prem) ] --work orders, routings--> [ Integration server with REST and file adapters ] --> [ Shop floor data collection terminals ] [ Shop floor data collection terminals ] --labour, quantities, scrap--> [ Integration server with REST and file adapters ] --> [ Infor SyteLine (on-prem) ] [ Barcode warehouse app ] <--pick, receipt, move transactions--> [ Integration server with REST and file adapters ] <--> [ Infor SyteLine (on-prem) ] [ Infor SyteLine (on-prem) ] --read-only extracts--> [ Reporting database and dashboards ]

Inbound interfaces (data into the ERP)

ID	Source	Method	Data	Frequency	Owner	Error handling
IN-01	PLM with released BOMs and drawings	REST or file	Item master, BOM, revision, ECO	On release	Engineering	Reject queue with email
IN-02	EDI VAN with X12 850, 855, 856, 810	EDI X12 850 via VAN	Customer purchase orders	Every 15 min	Customer service	Translator error report
IN-03	CRM and quoting tool	REST API	Customers, quotes, contacts	Near real time	Sales ops	Retry then alert
IN-04	Shop floor data collection terminals	API or staging table	Job labour, quantity complete, scrap	Every 5 min	Production	Hold in staging, review
IN-05	Barcode warehouse app	API	Receipts, picks, bin moves	Real time	Warehouse	Retry, reconcile nightly

Outbound interfaces (data out of the ERP)

ID	Target	Method	Data	Frequency	Owner	Error handling
OUT-01	EDI VAN with X12 850, 855, 856, 810	EDI X12 855, 856, 810	Acknowledgements, ship notices, invoices	On event	Customer service	Resend from log
OUT-02	Shop floor data collection terminals	API or file	Released work orders, routings, BOM	On release	Planning	Alert, manual push
OUT-03	Barcode warehouse app	API	Pick lists, expected receipts	Real time	Warehouse	Retry queue
OUT-04	Reporting database and dashboards	Read-only database view	Orders, inventory, WIP, costs	Nightly	Finance / IT	Job failure alert
OUT-05	Suppliers via EDI VAN with X12 850, 855, 856, 810	EDI X12 850	Purchase orders	On approval	Purchasing	Resend, confirm by email

Review notes

For every interface record: authentication method, who is paged when it fails, how a failed message is replayed, whether the interface writes to the ERP or only reads, and what happens during ERP upgrades or downtime. Mark any interface that depends on a custom table, a database trigger or a person with specific knowledge as a risk.

Approvals

ERP owner / Date

IT security / Date

Integration lead / Date

The context diagram is rendered as text, so it exports cleanly to Word and PDF. Redraw it in your own diagramming tool if you need boxes and lines. Method names are examples. Replace them with the real adapters, APIs and message formats in your landscape, and add a row for each additional interface.

Review your interface map

An optional session to check an interface map and identify where a private AI layer could read ERP data safely.

Optional. The tool and every export work without this. No spam.

Frequently asked questions

Is Infor ION an ordering system?

No. ION is integration middleware, not an application where orders are entered. Customer orders are entered in M3 itself (OIS100) and purchase orders in the purchasing programs such as PPS200. ION carries the resulting order documents, for example Process.PurchaseOrder BODs when a PO is approved, to other systems, and it can trigger workflows such as an approval when a PO passes a threshold. Which order BODs you publish depends on how your M3 and ION configuration is set up.

Design your M3 ION integration architecture with Netray's AI-powered analysis—get started today.

Talk to an engineer Try the free ERP Integration Diagram Template: Inbound and Outbound Interfaces

ArchRay builder

Design the on-prem AI stack for Infor M3: model, GPUs, RAG pipeline, guardrails

See memory, speed and cost as you swap parts, then export the diagram. Free, in your browser.

Open the builder

New to Infor M3? Start with the Infor M3 guide and toolkit, or plan with Training Path Builder, Upgrade Path Planner, ERP Table and Field Explorer.

Keep exploring

Free tools

ERP fixes and how-tos

Runs with your ERP

Guides

AI on your ERP

Integrations

Comparisons

Infor M3 vs SAP S/4HANA for Global Multi-Site ManufacturersInfor M3 vs SAP S/4HANA: compare process and discrete fit, deployment model, cost structure and upgrade burden for global multi-site manufacturers.

Software

Infor M3Independent guide to Infor M3 ERP, formerly Movex: modules, MI programs and MEC integration, deployment, strengths, limits and alternatives.

TermsEvent-Driven Architecture

Back to all resources