Infor M3 & CloudSuiteFree referencePDF, Excel, Word exportInfor M3

Infor ION BOD Verbs and Nouns Reference for M3 Integrations

Infor ION moves data between applications as Business Object Documents, or BODs. Each BOD has a verb that says what to do and a noun that says what it is about. This reference explains the verbs and common nouns M3 integrations use.

Download:

Type	Name	Meaning	Practical note
Verb	Sync	Publishes a change in master or transactional data to subscribers	Typical for master data such as items and parties
Verb	Process	Asks the receiver to create or act on a business object	Usually followed by an Acknowledge
Verb	Acknowledge	Reports the outcome of a Process or Sync request	Carries accept or reject status and errors
Verb	Get	Requests data from another application	Answered by a Show
Verb	Show	Returns the data requested by a Get	Contains the requested business objects
Verb	Change	Requests a change to an existing business object	Used when a full Process is not appropriate
Verb	Cancel	Requests cancellation of a business object	Check receiver support before relying on it
Verb	Confirm	Confirms receipt or completion of a request	Use only where your flow defines it
Verb	Respond	Provides a business response to a request	Often seen in request and reply patterns
Verb	Notify	Informs subscribers of an event	No reply is expected
Verb	Load	Bulk loads data into a target	Used mainly for initial or batch loads
Noun	ItemMaster	Item or product master data	Sync from M3 to PLM, WMS or e-commerce
Noun	SalesOrder	Customer sales order	Process to create orders, Sync to publish changes
Noun	PurchaseOrder	Purchase order to a supplier	Used to send POs to portals or EDI hubs
Noun	CustomerPartyMaster	Customer master data	Common between M3, CRM and billing tools
Noun	SupplierPartyMaster	Supplier master data	Common between M3 and supplier portals
Concept	ION Connect	Messaging and routing layer that moves BODs between applications	Defines connection points and document flows
Concept	Connection point	A configured endpoint for an application or file/API source	One per application instance
Concept	Document flow	Routing and mapping rules for BODs between connection points	Where filters and transformations are defined
Concept	ION API	Gateway for secured access to APIs of Infor applications	Used for REST calls with OAuth service accounts
Concept	Data Catalog	Registry of data objects ingested into the Data Lake	Defines the objects you can query
Concept	Data Lake	Cloud storage and query layer for Infor application data	Used for reporting and AI over M3 data

BODs follow the OAGIS standard as used by Infor ION. Available nouns and verbs depend on your application and release, so check the BOD catalog in ION Desk for the exact list in your environment.

Review an M3 integration design

We can look at your ION flows or API plan and point out gaps, as an optional follow-up.

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

How to use the reference

Search for a verb such as Sync or Process to see its meaning and the pattern it belongs to, or search a noun such as SalesOrder to see where it is used. The Concept rows cover the ION components you configure around BODs. Export to Excel and include it in the integration design document so the whole team uses the same terms.

Common message patterns

Most integrations use one of a few patterns. Master data publishing uses Sync from the owning application to subscribers. Transactional requests use Process followed by Acknowledge. Data retrieval uses Get followed by Show. Choosing the pattern first makes the document flow design much easier.

Sync: publish, no reply required beyond acknowledgement
Process then Acknowledge: request an action and get a result
Get then Show: query and receive data

Common mistakes

Teams often design flows around the screens they know rather than the BOD catalog, then discover that a noun does not support the action they need. Check the catalog early. Also plan for errors: an Acknowledge can carry a rejection, and unhandled rejections silently stop data. Set up monitoring in ION and decide who owns failed messages.

Frequently Asked Questions

What is a BOD in Infor ION?

A Business Object Document is an XML message based on the OAGIS standard. It combines a verb, such as Sync or Process, with a noun, such as SalesOrder, and carries the data and control information between applications.

What is the difference between Sync and Process?

Sync publishes that data has changed so subscribers can update themselves. Process asks a receiver to act on a business object, for example create an order. Process normally gets an Acknowledge back with the outcome.

Do I always need ION for M3 integrations?

No. Direct M3 API calls, MEC or file-based exchange are valid for point-to-point needs. ION is most useful for many-to-many flows and when you want central monitoring and mapping.

Where do I see the BODs available?

ION Desk shows the BOD catalog and the connection points and document flows in your environment. Check there for the nouns and verbs supported by your applications and versions.

If you are weighing ION flows against direct API calls for an integration, we can review the design with you and where an agent could monitor failed messages.

Talk to an Expert Explore More Free Tools

Related Tools

Infor M3 & CloudSuite

More Infor M3 & CloudSuite tools

See all

Back to All Tools