How to Map and Transform a BOD in Infor ION Connect
how to map and transform a BOD in Infor ION Connect
Also searched as
- ION Desk mapping BOD to BOD
- Infor ION document flow mapping fields
- ION Connect BOD transformation custom field
- Infor ION mapping function lookup
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.
Applies to: Infor ION Connect in Infor OS, cloud and on-premises; screens and function names vary slightly by release
Build and test a mapping
- 1In 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.
- 2Create 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.
- 3Map fields by dragging source elements to target elements, and use functions for string, number, date and conditional logic where the formats differ.
- 4Handle repeating lines by mapping the source line element to the target line element, and set any parent or header level values separately.
- 5Use 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.
- 6Create or edit a Document Flow, add the mapping in the path from the source connection point to the target, and activate the flow.
- 7Send 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.
- 8Promote the mapping to production through your normal tenant move process and keep the sample files in version control.
Mapping design choices that matter
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
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.
-- 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
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.
Common 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.
How an ERP-grounded AI assistant handles this
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.
Frequently asked questions
What is the difference between a mapping and a document flow in ION?
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?
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?
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?
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.
Related
Diagnose 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.
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 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.
CIO briefingEvent-Driven ERP Integration: Architecture That Holds Up
Use events when several systems must react to ERP changes quickly and you want to stop polling. Get events from the ERP's native mechanism where one exists, otherwise from change data capture, and design every consumer to be idempotent and tolerant of reordering. Keep the ERP as the system of record and treat events as notifications, not as the ledger.
Error fixFix a 401 Unauthorized error from Infor ION API
A 401 from ION API almost always means the credentials in the .ionapi file no longer match what ION API Gateway expects - not that the password is simply wrong. Check whether the Authorized App or service account behind the file was revoked, regenerated, expired, or issued for a different tenant, then re-test with a direct OAuth2 client_credentials call before touching any calling code.
How-toHow to query Infor Data Lake with Compass SQL
Compass is the SQL query layer in Infor OS for querying Infor Data Lake, where flattened copies of BODs published over ION are stored by Noun and Verb. Open a Compass SQL Workbench tab, browse the schema for the correct table, and run a filtered SELECT rather than pulling the full history, since Data Lake tables can hold years of append-only data.
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.
AI for ERPAI for Infor SyteLine and CloudSuite Industrial
Add grounded AI to Infor SyteLine or CloudSuite Industrial: natural-language answers, agents over IDOs and ION, on-prem or CloudSuite deployment.
Stuck on Infor ION (Connect)?
Talk to engineers who work inside Infor ION (Connect) every week, and who build private AI that answers these questions from your own ERP data.