# Infor ION BOD Verbs and Nouns Reference for M3 Integrations > Source: https://netray.co/tools/infor-m3-ion-bod-verbs-and-nouns-reference > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Look up what each ION BOD verb does, common nouns used with M3, and key ION components in plain language. ## Category infor-cloudsuite ## Erp Infor M3 ## Audience - Integration developer - M3 consultant - Infor OS administrator ## Tool **Kind:** worksheet **Mode:** reference **Columns:** #### Type **Key:** type **Type:** text #### Name **Key:** name **Type:** text #### Meaning **Key:** meaning **Type:** text #### Practical note **Key:** note **Type:** text **Rows:** #### Sync **Type:** Verb **Meaning:** Publishes a change in master or transactional data to subscribers **Note:** Typical for master data such as items and parties #### Process **Type:** Verb **Meaning:** Asks the receiver to create or act on a business object **Note:** Usually followed by an Acknowledge #### Acknowledge **Type:** Verb **Meaning:** Reports the outcome of a Process or Sync request **Note:** Carries accept or reject status and errors #### Get **Type:** Verb **Meaning:** Requests data from another application **Note:** Answered by a Show #### Show **Type:** Verb **Meaning:** Returns the data requested by a Get **Note:** Contains the requested business objects #### Change **Type:** Verb **Meaning:** Requests a change to an existing business object **Note:** Used when a full Process is not appropriate #### Cancel **Type:** Verb **Meaning:** Requests cancellation of a business object **Note:** Check receiver support before relying on it #### Confirm **Type:** Verb **Meaning:** Confirms receipt or completion of a request **Note:** Use only where your flow defines it #### Respond **Type:** Verb **Meaning:** Provides a business response to a request **Note:** Often seen in request and reply patterns #### Notify **Type:** Verb **Meaning:** Informs subscribers of an event **Note:** No reply is expected #### Load **Type:** Verb **Meaning:** Bulk loads data into a target **Note:** Used mainly for initial or batch loads #### ItemMaster **Type:** Noun **Meaning:** Item or product master data **Note:** Sync from M3 to PLM, WMS or e-commerce #### SalesOrder **Type:** Noun **Meaning:** Customer sales order **Note:** Process to create orders, Sync to publish changes #### PurchaseOrder **Type:** Noun **Meaning:** Purchase order to a supplier **Note:** Used to send POs to portals or EDI hubs #### CustomerPartyMaster **Type:** Noun **Meaning:** Customer master data **Note:** Common between M3, CRM and billing tools #### SupplierPartyMaster **Type:** Noun **Meaning:** Supplier master data **Note:** Common between M3 and supplier portals #### ION Connect **Type:** Concept **Meaning:** Messaging and routing layer that moves BODs between applications **Note:** Defines connection points and document flows #### Connection point **Type:** Concept **Meaning:** A configured endpoint for an application or file/API source **Note:** One per application instance #### Document flow **Type:** Concept **Meaning:** Routing and mapping rules for BODs between connection points **Note:** Where filters and transformations are defined #### ION API **Type:** Concept **Meaning:** Gateway for secured access to APIs of Infor applications **Note:** Used for REST calls with OAuth service accounts #### Data Catalog **Type:** Concept **Meaning:** Registry of data objects ingested into the Data Lake **Note:** Defines the objects you can query #### Data Lake **Type:** Concept **Meaning:** Cloud storage and query layer for Infor application data **Note:** Used for reporting and AI over M3 data **Notes:** 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. ## Content **Intro:** 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. **Sections:** #### How to use the reference **Body:** 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 **Body:** 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. **Bullets:** - 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 **Body:** 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. **Cta:** 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. **Faq:** #### What is a BOD in Infor ION? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms infor ion bod, ion bod verbs, sync bod infor, process acknowledge bod, infor ion document flow, m3 ion integration, infor ion noun list --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json