# Infor LN: BOD mapping errors when publishing to ION > Source: https://netray.co/erp-help/ln-bod-mapping-error-fix > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## 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. ## Kind error ## System infor-ln ## Erp Infor LN (Baan) ## Module Integration / ION BOD Mapping ## Query No mapping found error when publishing a BOD from Infor LN to ION ## Alternate Queries - 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 ## Applies To Infor LN 10.x with ION integration, Business Object Documents, ION Desk ## Steps ### Fix a BOD mapping error **Items:** - Open ION Desk and locate the failed document or flow instance to read the exact mapping error detail - Identify the specific field or reference value ION flagged as unmapped - In LN, check the relevant code mapping table referenced by the integration setup, such as currency, unit of measure, or a custom code list - Add the missing mapping entry, or correct the mismatched code between LN and the target application's BOD schema - Republish or reprocess the failed document from ION Desk rather than regenerating it from LN when possible - If the field is a custom LN field, confirm it was included in the BOD mapping configuration, not just added to the table - Test with a single document before batch-reprocessing a backlog - Monitor the ION Desk document flow dashboard to confirm the same mapping error does not recur on the next batch ## Sections ### How LN to ION mapping works **Body:** 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 **Body:** 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 **Body:** 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 **Body:** 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. ## 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 ## Ai Angle 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. ## Faq ### Is a BOD mapping error an ION problem or an LN problem? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms infor ln bod mapping error, ln no mapping found ion, ion desk mapping error infor ln, infor ln outbound bod field not mapped, ln ion integration error fix, baan bod publish error, infor ln custom field bod mapping, ion desk document flow mapping --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json