Infor LN: BOD mapping errors when publishing to ION
No mapping found error when publishing a BOD from Infor LN to ION
Also searched as
- LN BOD mapping error in ION Desk
- Infor LN outbound BOD field not mapped
- LN integration mapping failed error
- LN to ION document flow mapping error
Short answer
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.
Applies to: Infor LN 10.x with ION integration, Business Object Documents, ION Desk
Fix a BOD mapping error
- 1Open ION Desk and locate the failed document or flow instance to read the exact mapping error detail
- 2Identify the specific field or reference value ION flagged as unmapped
- 3In LN, check the relevant code mapping table referenced by the integration setup, such as currency, unit of measure, or a custom code list
- 4Add the missing mapping entry, or correct the mismatched code between LN and the target application's BOD schema
- 5Republish or reprocess the failed document from ION Desk rather than regenerating it from LN when possible
- 6If the field is a custom LN field, confirm it was included in the BOD mapping configuration, not just added to the table
- 7Test with a single document before batch-reprocessing a backlog
- 8Monitor the ION Desk document flow dashboard to confirm the same mapping error does not recur on the next batch
How LN to ION mapping works
LN publishes BODs through the ION connector, translating internal LN codes and fields into the standardized BOD schema used across the Infor suite. Every code list and custom field involved in a given flow needs an explicit mapping entry, or the connector has nothing to translate that value to on the receiving side.
Where mappings actually live
Some mappings sit in ION Desk's document flow configuration, others in LN-side setup tables that translate internal codes before the document is even published. A common troubleshooting mistake is checking only one side and concluding the mapping is fine when the gap is actually on the other.
Backlogs and reprocessing
A mapping error on one document often blocks or fails everything behind it in the same queue. Fixing the mapping and reprocessing the failed document from ION Desk is safer than resending it from LN, which can create a duplicate transaction if the original document had already partially processed.
Custom fields and extensions
When a DAL extension adds a new field to an LN object, that field does not automatically flow into an existing BOD map. Whoever owns the ION integration configuration has to add it explicitly, which is a step that is easy to miss after a customization goes live.
Common pitfalls
- !Fixing the mapping in LN and forgetting ION Desk's flow-level mapping also needs updating
- !Resending a document from LN before clearing the failed instance in ION Desk, creating a duplicate transaction
- !Assuming a mapping error means the whole ION connector is broken rather than one field or code value
- !Not testing with a single document before reprocessing a large backlog
- !Adding a custom field to the LN table but not to the BOD mapping configuration
How an ERP-grounded AI assistant handles this
ERPray, grounded in both LN and the ION integration setup, can pull the specific field or code value ION Desk flagged as unmapped and point to whether the gap is on the LN side or the ION flow side, saving a round trip between the ERP team and the integration team just to locate the mismatch.
Frequently asked questions
Is a BOD mapping error an ION problem or an LN problem?
It can be either. The unmapped field or code can originate on the LN side, where the code translation table is incomplete, or on the ION Desk side, where the flow's field mapping was never configured for that value.
Should I resend the document from LN after fixing the mapping?
No, reprocess the failed instance from ION Desk instead. Resending from LN risks creating a duplicate document if the original had already partially processed before it failed.
Why do custom fields need separate mapping work?
Adding a field to an LN table only makes the data available in LN. It does not automatically appear in an existing BOD schema mapping, so the integration owner has to add it explicitly for it to flow through to ION.
Why did a whole batch of documents fail from one mapping gap?
Documents in the same flow queue can back up behind a failed instance, so a single missing code mapping can appear to break every document processed after it until the root cause is fixed and the queue clears.
Related
Infor LN: "Record is locked by another user" error
This error means another LN session, interactive or batch, is holding an update lock on the same table row you are trying to change. Find the locking user or session in Active Sessions, confirm it is stale rather than genuinely running, and either wait or terminate it before you retry.
Error fixInfor LN: finalize run fails or gets stuck
Finalize sessions such as Cost Price Calculation, Sales Invoicing, and Period-End Statistics run as a broadly locked, largely exclusive batch step, so they most often fail because another user has the module open, a prior finalize run did not close cleanly, or a specific record has bad master data. Read the finalize log for the exact record or reason code, not just the failure message.
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 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.
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 DAL Out of Sync After a Custom Field: Cause and Fix
Infor LN throws a DAL, or table, out of sync error, or simply drops a new custom field silently, when a table's dictionary definition is changed but the generated DAL and dependent forms are not regenerated afterward. Running the standard sequence, table compile, DAL generation, then session/form compile, in Tools > Development after every dictionary change resolves it. Skipping any one of the three steps is what causes the mismatch.
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 (Baan)?
Talk to engineers who work inside Infor LN (Baan) every week, and who build private AI that answers these questions from your own ERP data.