Infor LN and M3 BOD Documentation: Definitions, Mapping and Tracing in ION
infor ln bod documentation
Also searched as
- infor ln outbound bod mapping and descriptions
- infor m3 bod processor
- where to find infor bod definitions
- trace a bod through ion
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.
Applies to: Infor LN 10.x and Infor M3 with Infor ION (on-prem and multi-tenant); menu names vary by ION version
How to find, map and trace a BOD
- 1Identify 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.
- 2Look 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.
- 3In 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.
- 4For 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.
- 5For 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.
- 6Create 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.
- 7Trigger 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.
- 8If the document failed, compare the payload against the schema, correct the mapping, and resubmit from the monitor if allowed.
Where BOD definitions live
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
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
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.
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
Try it here, free
Infor ION BOD Verbs and Nouns Reference for M3
Look up what each ION BOD verb does, common nouns used with M3, and key ION components in plain language.
Common 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.
How an ERP-grounded AI assistant handles this
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.
Frequently asked questions
Where can I find Infor LN BOD documentation?
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?
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?
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?
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.
Related
How to publish a BOD from Infor LN to Infor ION
Publishing a Business Object Document from Infor LN means flagging the relevant table or session for BOD publish, confirming LN's connection point to Infor ION is active, and building the document flow in ION Desk so changes like a new sales order are broadcast as a standard OAGIS-style XML message that other applications can subscribe to.
Error fixInfor LN: BOD mapping errors when publishing to ION
This error means the outbound Business Object Document from LN could not translate a field, code, or reference value into the ION-standard BOD schema, most often a missing code list mapping or an unmapped custom field, not a bug in ION itself. Fix the mapping on the correct side and reprocess from ION Desk rather than resending from LN.
AdvancedHow to Map and Transform a BOD in Infor ION Connect
In ION Desk you create a mapping between a source document and a target document, add it to a document flow between two connection points, and test it by sending a real or sample BOD. The mapping editor lets you assign fields, apply functions and lookups, and handle repeating structures, while the ION Monitor shows the result of each run.
Error fixDiagnose and fix a failed BOD document flow in ION Desk
A Document Flow showing Failed in ION Desk means a BOD (Business Object Document) stopped either at schema validation, at the mapping step, or at the target application. Open the failed instance's detail to see the exact failing element, fix the source data or mapping, then use Resubmit rather than re-triggering the original transaction to avoid duplicates.
Error fixFix a 401 Unauthorized error from Infor ION API
A 401 from ION API almost always means the credentials in the .ionapi file no longer match what ION API Gateway expects - not that the password is simply wrong. Check whether the Authorized App or service account behind the file was revoked, regenerated, expired, or issued for a different tenant, then re-test with a direct OAuth2 client_credentials call before touching any calling code.
How-toHow to query Infor Data Lake with Compass SQL
Compass is the SQL query layer in Infor OS for querying Infor Data Lake, where flattened copies of BODs published over ION are stored by Noun and Verb. Open a Compass SQL Workbench tab, browse the schema for the correct table, and run a filtered SELECT rather than pulling the full history, since Data Lake tables can hold years of append-only data.
AI for ERPAI Agents Over Infor ION API, BODs, and the Infor Data Lake
Build AI agents on Infor ION API Gateway, BODs, and Data Lake, alongside or instead of Infor's own GenAI features, with your choice of model and hosting.
AI for ERPAI for Infor LN: Sessions, BODs, and Engineer-to-Order Work
Add grounded AI to Infor LN 10.x or CloudSuite: natural-language answers over sessions and BODs, agents for project and engineer-to-order work, on-prem options.
AI for ERPInfor M3 AI: A Practical Path from MI Programs to a Private Assistant
Infor M3 AI explained: grounded natural-language answers over MI programs and MEC, agents for distribution and manufacturing, on-prem or EU private cloud.
Stuck on Infor LN / Infor M3 / Infor ION?
Talk to engineers who work inside Infor LN / Infor M3 / Infor ION every week, and who build private AI that answers these questions from your own ERP data.
Keep exploring
Free tools
- Infor ION BOD Verbs and Nouns Reference for M3Look up what each ION BOD verb does, common nouns used with M3, and key ION components in plain language.
- Infor M3 MEC Mapping Design TemplateA fill-in design document for an M3 Enterprise Collaborator mapping, from partner and flow to field rules and error handling.
- Infor M3 Data Conversion Mapping WorksheetTrack every legacy field to M3 target mapping with transformation rule, owner, record counts and cleansing status in a single table.
ERP fixes and how-tos
- Infor LN: BOD mapping errors when publishing to IONInfor LN BOD publishing error to ION: no mapping found for a field or code value, where LN and ION Desk mappings live, and how to fix and reprocess safely.
- Infor LN integration document types and integration rules with IONHow integration document types and rules work in Infor LN with ION and BODs: what they define, how mapping is set up, and where to debug.
- How to publish a BOD from Infor LN to Infor IONEnable BOD publish on an Infor LN table, connect it to your ION connection point, and build the document flow in ION Desk so other systems receive the data.
Runs with your ERP
- XEDI EDI Integration with Infor LN (ION BODs)How XEDI translates X12 and EDIFACT into Infor BODs routed through ION for Infor LN, plus SyteLine and M3. Setup steps, data flows, pitfalls and FAQ.
- Infor EDI Managed Service and Infor M3 over IONHow Infor's EDI managed service connects to Infor M3 through ION with pre-built trading partner links: data flows, setup steps, pitfalls and a private AI layer.
- SPS Commerce Fulfillment with Infor SyteLine: EDI orders, ASNs and invoices over IONHow SPS Commerce Fulfillment exchanges orders, ASNs and invoices with Infor SyteLine using ION BOD XML. Also covers LN, M3 and VISUAL, with setup and pitfalls.
Guides
- Infor LN ION API Integration GuideInfor ION API guide for LN: when to use the ION API gateway, BOD messaging or file-based exchange, how OAuth 2.0 access works, and how to secure calls.
- Infor ION Integration Patterns for M3: BODs, ION Connect, and Event-Driven ArchitectureHow Infor ION moves M3 sales and purchase orders between systems: BODs, ION Connect, API Gateway and event workflows. ION is middleware, not an order system.
- Infor LN + ION Workflows: Proven Automation PatternsInfor LN and ION workflow automation patterns: BODs, ION Desk monitors, approval workflows, and API integration recipes that remove manual ERP busywork.
AI on your ERP
- AI for Infor LN: Sessions, BODs, and Engineer-to-Order WorkAdd grounded AI to Infor LN 10.x or CloudSuite: natural-language answers over sessions and BODs, agents for project and engineer-to-order work, on-prem options.
- AI for Infor LN Warehousing: Inventory, Inbound and Outbound Exceptions Made SearchableAI for Infor LN Warehousing: trace inventory discrepancies and inbound or outbound exceptions in plain language. On-prem option, approval on writes.
Integrations
- How to add WhatsApp to Infor M3How to connect WhatsApp Business to Infor M3: M3 API (MI programs), ION events, template messages, opt-in rules and two-way replies, including on-prem M3 setups.
- How to add document OCR to Infor M3Capture invoices, packing slips and certificates into Infor M3 with OCR and AI: IDM, ION, Invoice Matching APIs, confidence thresholds and on-prem processing.