# Infor LN Inbound BOD Mapping and Descriptions > Source: https://netray.co/erp-help/infor-ln-inbound-bod-mapping-and-descriptions > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer BOD stands for Business Object Document, an XML message format from the Open Applications Group (OAGIS) that Infor uses to exchange business data between LN and other applications through ION. An inbound BOD is received by ION, optionally mapped, delivered to LN and processed by the integration document type configured for that noun and verb. 'BOD report' usually means a view of BOD message status in ION, not a printed report. ## Kind how-to ## System infor-ln ## Erp Infor LN / ION ## Module LN Integration / BOD Interface ## Query infor ln inbound bod mapping and descriptions ## Alternate Queries - integration document type infor ln - what is a bod report - bod report full form - what is bod reporting ## Applies To Infor LN 10.x with Infor ION (on-premises or cloud). Session names differ by version. ## Steps ### Trace and map an inbound BOD into LN **Items:** - Identify the BOD by noun and verb, for example a SalesOrder with the Process or Sync verb. The noun is the business object, the verb is the action requested. - In ION Desk, confirm the sending application and the LN connection point exist and that a document flow routes this BOD to LN. - If the source format is not the LN BOD format, add a mapping in the document flow so source fields land in the BOD elements LN expects. - In LN, check the integration document type setup for that BOD so LN knows which processing logic runs when it arrives. - Send a test message and watch it in ION Desk's monitoring. Note status: queued, delivered, error. - Open the failed message and read the error text and the field it names. Correct the mapping or the master data it refers to, then reprocess. - Confirm the business result in LN, for example the order or item that should have been created or updated. ## Sections ### BOD in plain terms **Body:** BOD stands for Business Object Document. It is an XML envelope built on the OAGIS standard. Every BOD has an ApplicationArea, which says who sent it, when and with what identifiers, and a DataArea, which carries a verb element (the action) and one or more noun elements (the business data). Common verbs include Process (do this, then confirm), Sync (keep a copy in step), Get and Show (query and response), and Acknowledge or Confirm as reply messages. Which verbs a given noun supports depends on the Infor application and version. **Code:** sender, creation time, BOD id header and lines ### Integration document types in LN **Body:** LN does not treat every incoming XML the same way. Each supported BOD is registered as an integration document type, which links the BOD to the LN logic that creates or updates records. If the document type is not set up or not active, the BOD arrives in ION but nothing happens in LN. When reading a BOD, start from the noun to find the LN business object it touches, then check master data such as items, business partners, warehouses and units that the content refers to. Most inbound failures are missing or inconsistent master data, not bad XML. ### Mapping, descriptions and 'BOD reporting' **Body:** A mapping in ION Desk translates fields between a source structure and the target BOD. Keep mappings simple: direct field copies, a few constants and lookups. Complex conversion belongs in a documented transformation step so support staff can read it. 'BOD reporting' normally means monitoring: how many BODs arrived, which failed and why. ION Desk's message monitoring is the first place to look, and a periodic summary of failures by noun is a useful operational report. ## Pitfalls - Mapping to the wrong verb, so a Sync is processed as if it were a Process or vice versa. - Sending BODs that reference items or business partners that do not yet exist in LN. - Reprocessing failed messages without fixing the cause, producing the same error repeatedly. - Assuming ION delivery success means LN processing success. They are separate statuses. - Over-engineering mappings so only one person understands them. ## Ai Angle BOD failures are mostly a matter of reading an error and tracing it to master data. A private assistant inside your network can read ION message errors, match them to LN item and partner data in read-only mode, and explain in plain language what is missing. Netray runs this with open-weight models on your own hardware, so payload content stays on-prem. ## Faq ### What is the full form of BOD? **Answer:** In Infor and OAGIS usage, BOD stands for Business Object Document. It is a standard XML message used to exchange business data such as orders, items and invoices between applications through ION. ### What is a BOD report? **Answer:** Most often it means a monitoring view of BOD messages in ION Desk showing what was sent, delivered or failed. It is not a printed ERP report. Some teams also build a summary of failed BODs by noun and cause. ### What is an integration document type in Infor LN? **Answer:** It is the LN-side registration that ties an incoming or outgoing BOD to the logic that processes it. Without an active document type for a BOD, LN will not act on the message even if ION delivers it. ### Why did my inbound BOD arrive but create nothing? **Answer:** Check ION first for delivery status, then the LN document type setup and the master data the BOD references. A missing item, warehouse or business partner is the most common reason for no result or an error. ## Search terms infor ln inbound bod, bod full form, business object document, what is a bod, infor ion bod mapping, integration document type infor ln, oagis bod, bod reporting infor --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json