Infor LN integration document types and integration rules with ION
infor ln integration document type
Also searched as
- integration rules for ln
- infor ln ion bod document
- infor ln integration mapping setup
Short answer
In LN, an integration document type ties an LN business object to a BOD noun and direction so ION can send or receive it. Rules and mappings then decide which LN data populates the BOD, which events trigger publication and how incoming BODs are converted into LN transactions. Set up the document type first, then the mapping, then test in ION Desk.
Applies to: Infor LN 10.x with Infor OS / ION (on-prem or cloud). Session names vary by version.
Set up an integration document
- 1Confirm the ION connection point (the LN application ID) and logical ID are configured and active.
- 2Define or enable the integration document type for the BOD noun, with direction (outbound publish or inbound consume).
- 3Configure the data mapping from LN fields to BOD elements, including code translations (units, currencies, business partners).
- 4Configure the triggering rule: which LN event or status change publishes the BOD, and any filter conditions.
- 5Register the document flow in ION Desk with the connection points and a routing rule.
- 6Test with one record and inspect the BOD in ION monitoring. Fix mapping errors before enabling at volume.
What the document type controls
The document type is the contract. It says which LN entity maps to which BOD noun, in which direction, and with which verbs (Sync, Process, Get). Without it enabled, ION sees nothing from LN or LN rejects what ION sends.
Custom fields need DAL extensions and an extended mapping. Out-of-sync customization shows as missing elements in the BOD or inbound validation failures.
Rules, mapping and translation
Most production issues sit in code translation: a unit of measure, an item or a business partner code that exists in LN but has no cross-reference in the other system. Maintain cross-reference tables intentionally and monitor for unmapped values.
Inbound BODs run through DAL, so business rules apply. A BOD that breaks a rule is rejected with a message you can read in the integration monitor.
Where to debug
Use the LN integration monitor for outbound status, ION Desk for message flow and the BOD content, and the LN log for DAL errors. Compare a good and a bad BOD side by side.
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
- !Enabling publication before translation tables are populated.
- !Testing only with a toy record that skips optional elements.
- !Custom fields not reflected in the mapping.
- !No monitoring for rejected inbound BODs.
- !Changing mapping in production without versioning.
How an ERP-grounded AI assistant handles this
An assistant that reads ION message logs and LN mapping tables can say why a BOD failed and which cross-reference is missing. Netray builds integrations and private AI over them; inbound writes stay behind human approval.
Frequently asked questions
What is an integration document type in LN?
It is the definition that links an LN business entity to a BOD noun and direction, so LN can publish or consume that document through ION.
Do I need a rule for every BOD?
You need a trigger for outbound documents and a mapping for both directions. Exact configuration depends on the noun and version.
Why is my BOD rejected on inbound?
Most often an unmapped code or a DAL validation failure. The integration monitor and LN log show which.
Can I use REST instead of BODs?
For many scenarios, yes. See the LN REST API page; BODs remain the standard for event-driven document exchange.
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.
Error fixInfor LN Incoming EDI Message Not Processed or Stuck
An inbound EDI message that never becomes a sales order or schedule has stopped at one of three stages: receipt into the EDI message tables, conversion from the external format to the LN business document, or the application update that writes the order. Find the stage from the message status and log, fix the mapping, trading partner or master data cause, then reprocess the message rather than re-sending the file.
How-toInfor LN REST API: documentation, administration and a first call
LN REST access goes through the Infor ION API gateway. You register an authorized app in ION API, download its .ionapi credentials file, obtain an OAuth 2.0 token and call the LN API endpoints with the bearer token. Official reference material is on the Infor documentation site and the ION API documentation inside your Infor OS portal.
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 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 ERPAI for Legacy Baan IV/V: Capture the Knowledge Before It Walks Out the Door
Use AI to capture knowledge from ageing Baan IV/V systems, document undocumented customisations, and de-risk a future migration to LN or CloudSuite.
Stuck on Infor LN?
Talk to engineers who work inside Infor LN 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 Safety Stock and Reorder Point CalculatorCompute safety stock, reorder point and the equivalent safety time in days, with a lead time what-if chart.
- Infor LN Warehousing Order Origins and Types ReferenceReference of the order origins that feed LN warehousing, their direction, source package and what to check.
ERP fixes and how-tos
- 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 Inbound BOD Mapping and DescriptionsWhat a BOD is, the full form, how Infor LN receives inbound BODs through ION, how integration document types and mapping work, and how to read the fields.
- 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.
- 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.
- 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.
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.