# How to Map and Transform a BOD in Infor ION Connect > Source: https://netray.co/erp-help/infor-ion-bod-mapping-transform-how-to > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer 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. ## Kind advanced ## System infor-os ## Erp Infor ION (Connect) ## Module ION Desk / Mappings and Document Flows ## Query how to map and transform a BOD in Infor ION Connect ## Alternate Queries - ION Desk mapping BOD to BOD - Infor ION document flow mapping fields - ION Connect BOD transformation custom field - Infor ION mapping function lookup ## Applies To Infor ION Connect in Infor OS, cloud and on-premises; screens and function names vary slightly by release ## Steps ### Build and test a mapping **Items:** - In ION Desk, open Connect and confirm both applications have connection points, with the document types you need (for example Sync.SalesOrder or a custom noun) registered. - Create a Mapping and choose the source and target document definitions. Load a sample of each, ideally exported from the Monitor so it reflects your real data. - Map fields by dragging source elements to target elements, and use functions for string, number, date and conditional logic where the formats differ. - Handle repeating lines by mapping the source line element to the target line element, and set any parent or header level values separately. - Use a lookup table or cross reference for code translations (for example unit of measure or warehouse), and decide the default for values that are not found. - Create or edit a Document Flow, add the mapping in the path from the source connection point to the target, and activate the flow. - Send a test BOD, then open the Monitor in ION Desk to confirm the status of the document at each hop, reading the error text on any failure. - Promote the mapping to production through your normal tenant move process and keep the sample files in version control. ## Sections ### Mapping design choices that matter **Body:** A mapping is only as stable as the document definition under it. If either application changes its BOD version or adds a mandatory element, a mapping that worked yesterday starts failing with schema or validation errors. Capture the definition version in your documentation and retest whenever either side upgrades. Keep business logic out of mappings where you can. Simple field moves, formatting and code lookups belong here. Complex decisions, such as which plant owns an order, belong in the source or target application where they can be seen by the people who maintain it. A mapping that grows hundreds of conditional rules is hard to test and harder to hand over. ### Custom fields and user defined data **Body:** Standard BODs often include a place for extended data, such as user-defined fields or extension elements. Check what your source application actually publishes before building the target side, because a field that exists in the database may not be in the outgoing BOD until it is added to the publishing configuration of the source product. When a field must travel but the target noun has no place for it, use the target's extension element if one exists, or agree a custom noun with the owner of the target system. Avoid overloading an existing field such as a description with encoded data, which breaks the first time someone edits it. **Code:** -- Typical test routine in the ION Desk Monitor 1. Document Flows > open flow > Test 2. Paste sample BOD XML or send from source app 3. Monitor > select document > view Source, Target and Error tabs 4. Fix mapping, re-submit the failed document from Monitor ### Reading mapping errors **Body:** Errors in the Monitor usually point to one of four causes: a mandatory target element left empty, a value outside an allowed code list, a lookup that returned nothing, or a date or number format that the target cannot parse. The error text names the element, so start there rather than testing the whole mapping blindly. After you correct the mapping, resubmit the failed documents from the Monitor instead of re-triggering them in the source application. This avoids duplicates, since a repeated publish from the source can create a second business document in the target. ## Pitfalls - Building a mapping from a hand-written sample instead of an actual BOD from the Monitor, which hides real optional elements. - Leaving lookup defaults empty so unmatched codes pass through as blank and fail later in the target. - Re-triggering the business transaction in the source instead of resubmitting from the Monitor, which can create duplicates. - Hard coding site, plant or company codes in the mapping that differ between test and production tenants. - Not retesting after an ERP upgrade changes the BOD version or adds mandatory elements. ## Ai Angle An assistant can help with the dull parts of this work: comparing two document definitions, drafting a field mapping table for review, and reading Monitor errors to point at the failing element. It should propose changes, not apply them. Netray custom agents can be set up to draft the mapping spec while a person approves the change, and SyteRay does the same for SyteLine-side integrations. ## Faq ### What is the difference between a mapping and a document flow in ION? **Answer:** A mapping defines how fields from a source document convert to a target document. A document flow defines the route a document takes between connection points and which mappings, routing rules and filters apply along that route. ### Where do I see why a BOD failed in ION? **Answer:** Use the Monitor in ION Desk. Open the failed document and review its status at each step and the error text, then compare the source and target payloads to find the element that broke. ### Can ION mappings call external systems for lookups? **Answer:** Mappings support lookup tables and functions for in-flow translation. Live calls to external systems are normally handled with API or scripting steps in your integration design rather than inside a field mapping. ### Should I test mappings directly in production? **Answer:** No. Build and test in a non-production tenant with realistic data, keep the sample files, and then promote. A faulty mapping in production can create bad business documents in the target system. ## Search terms Infor ION mapping, ION Desk mapping BOD, ION Connect document flow, BOD transformation, Infor ION Monitor error, ION lookup table, Infor ION custom field BOD, Sync.SalesOrder mapping, ION Desk connection point, Infor ION BOD to BOD --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json