# How to publish a BOD from Infor LN to Infor ION > Source: https://netray.co/erp-help/ln-publish-bod-to-ion-desk > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer 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. ## Kind how-to ## System infor-ln ## Erp Infor LN ## Module Infor ION / BOD Integration ## Query how to publish a bod from infor ln to ion ## Alternate Queries - infor ln bod publish setup - infor ln ion connect point configuration - enable bod publish infor ln table - infor ln to ion desk document flow ## Applies To Infor LN Enterprise Edition connected to Infor ION / Infor OS, ION Desk ## Steps ### Enable and configure BOD publish from Infor LN **Items:** - Confirm the LN environment is registered as a connection point in Infor ION (Infor OS) and that connectivity between LN and ION is active. - In LN, identify the table or session tied to the business object you want to publish, for example Sales Order, Purchase Order or Item. - Enable the BOD publish setting for that table or session so relevant create, change or cancel events raise a BOD. - In Infor ION Desk, create or edit the document flow: select the LN connection point as the source and choose the BOD type, such as SalesOrder or PurchaseOrder. - Define the target application or service as the subscriber for that document flow. - Map any fields or apply transformations in ION Desk if the subscriber expects a different structure than the BOD LN generates. - Activate the document flow, then in LN trigger a test transaction, such as creating or changing the relevant record, to generate a BOD event. - Monitor the message in ION's document flow tooling to confirm it was generated, routed and consumed without errors. - Once confirmed in test, promote the LN publish setting and the document flow through your standard environments to production. ## Sections ### What a BOD actually is **Body:** BOD stands for Business Object Document, a standard OAGIS-based XML message format built from an ApplicationArea (routing and metadata) and a DataArea (the actual business data). Infor's ION-connected applications, including LN, use this common structure so an application does not need a custom point-to-point interface for every integration. Publishing means LN raises this XML whenever the flagged table or session changes, independent of what, if anything, consumes it. Whether the message goes anywhere useful depends entirely on the document flow you configure in ION Desk. ### Connection points and document flows **Body:** An ION connection point represents the LN environment inside ION. ION Desk is where you build and monitor document flows that route a BOD from a source connection point to one or more targets, with optional field mapping between the structure LN generates and whatever the target application expects. ### Common publish scenarios **Body:** Typical uses include publishing Sales Order or Item BODs from LN to a CRM or e-commerce platform, publishing Invoice BODs to a finance consolidation tool, or routing transaction BODs to a data lake for reporting. Each scenario just needs a document flow pointed at a different target with its own mapping; the LN-side publish setup does not change. **Code:** InforLN ... Add ... ... ### Troubleshooting a BOD that never arrives **Body:** Check the publish flag is actually enabled on the source table, not just saved as a draft. Check the document flow in ION Desk is active, not merely created. Check the connection point's health status, and check the ION Desk monitor for a message stuck in error or held for manual mapping resolution before assuming the problem is on the LN side. ## Pitfalls - Enabling BOD publish on the table but leaving the ION document flow inactive, so nothing actually routes. - Assuming a BOD publishes on every field change, when it may only fire on the specific events you configured. - Testing with a minimal record instead of one with all typically-populated fields, so a mapping gap only shows up on real transactions. - Ignoring the ION Desk monitor logs, letting failed messages queue up silently until a downstream user reports missing data. - Publishing high-volume tables, like every inventory transaction, without considering message volume and downstream processing load. ## Ai Angle For a support team fielding a question like why a sales order did not show up downstream, an AI assistant grounded in the LN-to-ION document flow configuration can check the publish flag, the flow's active status and the ION Desk error log in one pass and summarize where the message actually stalled, instead of someone stepping through each screen by hand. ## Faq ### What does BOD stand for in Infor LN? **Answer:** Business Object Document, a standard OAGIS-based XML message format that Infor applications use to exchange business data, such as a sales order or item, through Infor ION rather than through point-to-point custom interfaces. ### Do I need Infor ION to publish a BOD from LN? **Answer:** Yes. BOD publish only has somewhere to go once LN is connected to Infor ION through an active connection point; without ION there is no document flow to route the message anywhere. ### Where do I see if a published BOD reached its target? **Answer:** In Infor ION Desk's document flow monitor, which shows each message's status, such as delivered, in error, or held for mapping, so you can trace a specific transaction end to end. ### Can I publish a BOD from a custom LN table? **Answer:** Yes, provided the table and its business object are properly defined and flagged for publish, and a matching BOD definition and document flow exist or are created in ION Desk for that custom object. ## Search terms infor ln bod publish, infor ion desk document flow, infor ln ion connect point, publish sales order bod infor ln, infor ln ion integration setup, oagis bod infor ln, infor ln to ion connectivity, infor ln business object document, ion desk monitor bod errors, infor ln ion api --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json