Infor LN Inbound BOD Mapping and Descriptions
infor ln inbound bod mapping and descriptions
Also searched as
- integration document type infor ln
- what is a bod report
- bod report full form
- what is bod reporting
Short answer
BOD stands for Business Object Document, an XML message format from the Open Applications Group (OAGIS) that Infor uses to exchange business data between LN and other applications through ION. An inbound BOD is received by ION, optionally mapped, delivered to LN and processed by the integration document type configured for that noun and verb. 'BOD report' usually means a view of BOD message status in ION, not a printed report.
Applies to: Infor LN 10.x with Infor ION (on-premises or cloud). Session names differ by version.
Trace and map an inbound BOD into LN
- 1Identify the BOD by noun and verb, for example a SalesOrder with the Process or Sync verb. The noun is the business object, the verb is the action requested.
- 2In ION Desk, confirm the sending application and the LN connection point exist and that a document flow routes this BOD to LN.
- 3If the source format is not the LN BOD format, add a mapping in the document flow so source fields land in the BOD elements LN expects.
- 4In LN, check the integration document type setup for that BOD so LN knows which processing logic runs when it arrives.
- 5Send a test message and watch it in ION Desk's monitoring. Note status: queued, delivered, error.
- 6Open the failed message and read the error text and the field it names. Correct the mapping or the master data it refers to, then reprocess.
- 7Confirm the business result in LN, for example the order or item that should have been created or updated.
BOD in plain terms
BOD stands for Business Object Document. It is an XML envelope built on the OAGIS standard. Every BOD has an ApplicationArea, which says who sent it, when and with what identifiers, and a DataArea, which carries a verb element (the action) and one or more noun elements (the business data).
Common verbs include Process (do this, then confirm), Sync (keep a copy in step), Get and Show (query and response), and Acknowledge or Confirm as reply messages. Which verbs a given noun supports depends on the Infor application and version.
<ProcessSalesOrder>
<ApplicationArea> sender, creation time, BOD id </ApplicationArea>
<DataArea>
<Process/>
<SalesOrder> header and lines </SalesOrder>
</DataArea>
</ProcessSalesOrder>Integration document types in LN
LN does not treat every incoming XML the same way. Each supported BOD is registered as an integration document type, which links the BOD to the LN logic that creates or updates records. If the document type is not set up or not active, the BOD arrives in ION but nothing happens in LN.
When reading a BOD, start from the noun to find the LN business object it touches, then check master data such as items, business partners, warehouses and units that the content refers to. Most inbound failures are missing or inconsistent master data, not bad XML.
Mapping, descriptions and 'BOD reporting'
A mapping in ION Desk translates fields between a source structure and the target BOD. Keep mappings simple: direct field copies, a few constants and lookups. Complex conversion belongs in a documented transformation step so support staff can read it.
'BOD reporting' normally means monitoring: how many BODs arrived, which failed and why. ION Desk's message monitoring is the first place to look, and a periodic summary of failures by noun is a useful operational report.
Try it here, free
Baan to Infor LN Data Conversion Mapping Worksheet
Field-level mapping sheet for Baan or legacy data moving into Infor LN, with transform rules, owners and load status.
Common pitfalls
- !Mapping to the wrong verb, so a Sync is processed as if it were a Process or vice versa.
- !Sending BODs that reference items or business partners that do not yet exist in LN.
- !Reprocessing failed messages without fixing the cause, producing the same error repeatedly.
- !Assuming ION delivery success means LN processing success. They are separate statuses.
- !Over-engineering mappings so only one person understands them.
How an ERP-grounded AI assistant handles this
BOD failures are mostly a matter of reading an error and tracing it to master data. A private assistant inside your network can read ION message errors, match them to LN item and partner data in read-only mode, and explain in plain language what is missing. Netray runs this with open-weight models on your own hardware, so payload content stays on-prem.
Frequently asked questions
What is the full form of BOD?
In Infor and OAGIS usage, BOD stands for Business Object Document. It is a standard XML message used to exchange business data such as orders, items and invoices between applications through ION.
What is a BOD report?
Most often it means a monitoring view of BOD messages in ION Desk showing what was sent, delivered or failed. It is not a printed ERP report. Some teams also build a summary of failed BODs by noun and cause.
What is an integration document type in Infor LN?
It is the LN-side registration that ties an incoming or outgoing BOD to the logic that processes it. Without an active document type for a BOD, LN will not act on the message even if ION delivers it.
Why did my inbound BOD arrive but create nothing?
Check ION first for delivery status, then the LN document type setup and the master data the BOD references. A missing item, warehouse or business partner is the most common reason for no result or an error.
Related
Infor 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.
How-toHow 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 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 fixSyteLine EDI or BOD inbound document fails to create a sales order
An inbound EDI 850 or ION SyncSalesOrder / ProcessSalesOrder BOD that does not turn into a SyteLine order almost always fails validation before it ever reaches order entry logic - most often a customer, ship-to, or item cross-reference that the mapping expects but SyteLine does not have on file. Check the EDI translator's error log or the ION BOD document inbox first; the rejection reason is usually recorded there, not just a generic SyteLine error.
Error fixInfor LN bshell Process Stuck at 100% CPU: How to Diagnose and Fix It
A bshell process pinned at 100% CPU on the Infor LN application server almost always means one session is stuck in a 4GL loop, scanning an unindexed table, or waiting on a database lock. End the session from the Sessions Monitor first, then kill the OS process only if that fails, and check for a blocking database transaction before assuming it is a bug.
Error fixInfor LN Not Authorized to Run This Session: How to Fix It
Infor LN refuses to open a session with a not authorized message when the logged-in user's assigned role does not include that session, or when the session is blocked for the company they are logged into. Grant the session through Common > Authorization Management > Roles, or check the user's role and company context, and the session opens on retry. In most cases this is a permissions configuration issue, not a bug.
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.
Stuck on Infor LN / ION?
Talk to engineers who work inside Infor LN / ION every week, and who build private AI that answers these questions from your own ERP data.
Keep exploring
Free tools
- Baan to Infor LN Data Conversion Mapping WorksheetField-level mapping sheet for Baan or legacy data moving into Infor LN, with transform rules, owners and load status.
- Infor LN and Baan Integration Interface Specification TemplateFill-in functional and technical specification for an LN or Baan interface, including data flow, error handling and volumes.
- Infor LN Change Request Form TemplateFill-in change request form for LN and Baan changes, covering scope, impact, testing, rollback and sign-off.
ERP fixes and how-tos
- 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.
- Infor LN and M3 BOD Documentation: Definitions, Mapping and Tracing in IONWhere to find BOD definitions for Infor LN and M3, how outbound BOD mapping works, what the M3 BOD processor does, and how to trace a BOD through ION.
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.
- 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.
- Salesforce to Infor LN Data Integration GuideInfor Salesforce integration for Infor LN: sync customers, orders and pricing between Salesforce CRM and LN using ION, BODs and REST APIs. SyteLine covered too.
- Infor LN API Development: REST, SOAP, and BOD Integration GuideBuild integrations with Infor LN APIs using BODs, web services, and the LN Integration Framework. Developer guide for LN REST and SOAP endpoint programming.
Integrations
- How to add AI agents to Infor LNHow to add AI agents to Infor LN: a tool layer over ION API and BODs, read-only reporting first, approval before writes, and fully on-prem model hosting.
- How to add WhatsApp to Infor LNHow to connect WhatsApp to Infor LN: ION BODs and APIs, template messages, opt-in rules, supplier confirmations and order status, including on-prem LN setups.