# Infor LN and M3 BOD Documentation: Definitions, Mapping and Tracing in ION > Source: https://netray.co/erp-help/infor-ln-bod-documentation-m3-bod-processor-ion-trace > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer A BOD (Business Object Document) is the XML message ION moves between Infor applications. Definitions come from the Infor documentation and from ION itself (the document and schema information in ION Desk), the outbound mapping is configured in the application that publishes the BOD, and a BOD is traced through ION with the message monitoring tools by its document name and identifier. ## Kind how-to ## System infor-os ## Erp Infor LN / Infor M3 / Infor ION ## Module ION / BOD integration ## Query infor ln bod documentation ## Alternate Queries - infor ln outbound bod mapping and descriptions - infor m3 bod processor - where to find infor bod definitions - trace a bod through ion ## Applies To Infor LN 10.x and Infor M3 with Infor ION (on-prem and multi-tenant); menu names vary by ION version ## Steps ### How to find, map and trace a BOD **Items:** Identify the BOD noun and verb: for example Sync.SalesOrder, Process.PurchaseOrder, Sync.Item. The noun is the business object, the verb says how the receiver should treat it. Look up the noun in the Infor documentation for your application (LN or M3) and in the ION documentation for the BOD schema, which lists each element and which are mandatory. In ION Desk open the connection point of the application and check the document definitions it publishes and subscribes to. This shows the BOD names your system really supports. For outbound BODs from LN, check the BOD configuration in the application: which events trigger publication and which field mapping from tables to BOD elements applies. For M3, check how BODs are produced and consumed by the M3 BOD processor, a component that converts between M3 data and BODs, and confirm it is running. Create a document flow in ION Desk connecting publisher and subscriber, and add mapping or routing as needed. See the existing page on mapping and transforming BODs. Trigger a test event, then open the ION monitoring view and search by document name and time to find the message. Read the status, the error text and the payload. If the document failed, compare the payload against the schema, correct the mapping, and resubmit from the monitor if allowed. ## Sections ### Where BOD definitions live **Body:** There are three useful sources. The Infor product documentation lists the supported nouns and the application-specific mapping. The ION documentation and the schemas shipped with ION describe the generic BOD structure. And the live system, through the ION Desk connection point, shows what your instance actually publishes and subscribes to, which beats any static list. The BOD schema follows the OAGIS-based structure with an ApplicationArea (sender, creation time, BODID) and a DataArea containing the verb and the noun. The BODID in the ApplicationArea is the value you search for when tracing a specific message. ### How outbound mapping works **Body:** The publishing application maps its internal data to BOD elements. In LN, publication is driven by events on business objects, and the mapping defines which table fields fill which BOD fields. In M3, the BOD processor reads M3 data through the application layer and builds the BOD. If a field is missing in the outbound BOD, the first question is whether the application maps it at all. If it does not, the options are a custom extension in the publishing application, or an ION mapping that enriches the message from another source. Keep these two clearly separate in your design documents. ### Tracing a BOD end to end **Body:** Trace in order: did the application publish the BOD, did ION receive it, was it routed to the subscriber, did the subscriber acknowledge it. Each hop has its own status in the monitoring tools, and the first non-successful hop is your problem. A BOD with a warning is not the same as a BOD that failed. Read the payload and the acknowledgement for the subscriber's response, because the receiving application often reports exactly which field it rejected. **Code:** Trace checklist: 1. Search ION monitor by document name (for example Sync.SalesOrder) and time window 2. Open the message, copy BODID and compare with the publisher log 3. Check status per hop: published, routed, delivered, acknowledged 4. Read the Confirm or error BOD for the rejection reason ## Pitfalls - Assuming a BOD documented for one application version is published by yours. - Searching the ION monitor without a tight time window and drowning in messages. - Changing the receiver mapping when the publisher never sent the field. - Ignoring the confirmation BOD, which carries the rejection reason. - Leaving the M3 BOD processor stopped after maintenance. ## Ai Angle An assistant grounded in your ION message history can answer which BOD failed for this order and why, by pulling the message and the rejection text and explaining the mismatch against the schema. It is read-only and shows what it queried; resubmission stays with your integration team. ## Faq ### Where can I find Infor LN BOD documentation? **Answer:** Use the Infor product documentation for LN and the ION documentation for the schema, and confirm the live list in ION Desk by looking at the connection point of your LN system. The live list reflects your actual version. ### What is the M3 BOD processor? **Answer:** It is the M3 component that builds outbound BODs from M3 data and processes inbound BODs into M3 transactions. If it is not running, BOD traffic to and from M3 stops without an obvious error in the business screens. ### How do I trace a BOD in ION? **Answer:** Search the ION monitoring view by document name and time window, open the message, and follow its status hop by hop. The BODID in the ApplicationArea links the message across the publisher, ION and the subscriber. ### How do I add a field to an outbound BOD? **Answer:** Check whether the publisher maps it. If not, extend the mapping in the publishing application, or enrich the message in an ION mapping. Prefer the publisher when the data lives there. ## Search terms infor ln bod documentation, infor ln outbound bod mapping, infor m3 bod processor, infor ion bod, business object document infor, ion desk document flow, infor bod trace, infor bod schema --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json