How to publish a BOD from Infor LN to Infor ION
how to publish a bod from infor ln to ion
Also searched as
- infor ln bod publish setup
- infor ln ion connect point configuration
- enable bod publish infor ln table
- infor ln to ion desk document flow
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.
Applies to: Infor LN Enterprise Edition connected to Infor ION / Infor OS, ION Desk
Enable and configure BOD publish from Infor LN
- 1Confirm the LN environment is registered as a connection point in Infor ION (Infor OS) and that connectivity between LN and ION is active.
- 2In LN, identify the table or session tied to the business object you want to publish, for example Sales Order, Purchase Order or Item.
- 3Enable the BOD publish setting for that table or session so relevant create, change or cancel events raise a BOD.
- 4In 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.
- 5Define the target application or service as the subscriber for that document flow.
- 6Map any fields or apply transformations in ION Desk if the subscriber expects a different structure than the BOD LN generates.
- 7Activate the document flow, then in LN trigger a test transaction, such as creating or changing the relevant record, to generate a BOD event.
- 8Monitor the message in ION's document flow tooling to confirm it was generated, routed and consumed without errors.
- 9Once confirmed in test, promote the LN publish setting and the document flow through your standard environments to production.
What a BOD actually is
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
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
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.
<!-- Illustrative BOD skeleton pattern (OAGIS-style structure) -->
<SalesOrder>
<ApplicationArea>
<Sender>InforLN</Sender>
<CreationDateTime>...</CreationDateTime>
</ApplicationArea>
<DataArea>
<Process>Add</Process>
<SalesOrder>
<SalesOrderHeader>...</SalesOrderHeader>
<SalesOrderLine>...</SalesOrderLine>
</SalesOrder>
</DataArea>
</SalesOrder>Troubleshooting a BOD that never arrives
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.
Common 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.
How an ERP-grounded AI assistant handles this
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.
Frequently asked questions
What does BOD stand for in Infor LN?
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?
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?
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?
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.
Related
How to extend business logic in Infor LN with DAL2
DAL2 lets you add custom validation, defaulting and calculation logic to Infor LN Enterprise Edition tables by writing a Java business logic handler class and registering it against a table event, without editing the standard DAL. Because the logic sits in your own package rather than inside Infor's base code, it survives upgrades that would otherwise overwrite a direct DAL change.
AdvancedHow to create a custom session in Infor LN Studio
Infor LN Studio's session designer generates a new maintenance, overview or detail session from a table definition, then lets you arrange fields, attach DAL2 validation, and wire menu access, all inside a custom package so the session survives upgrades. Building on a custom table gives the lowest upgrade risk; extending a standard table needs more care and re-testing after every release.
AdvancedHow to diagnose and fix a slow Infor LN session
A slow Infor LN session is usually caused by an unindexed or overly broad database query, unarchived data bloating a transaction table, or resource pressure on the Java application tier, and occasionally by a recently added custom DAL2 handler. The fix starts with isolating which tier the delay is actually in rather than guessing at a solution.
How-toBaan IV to Infor LN migration checklist
Moving from Baan IV to Infor LN is a re-implementation, not an in-place upgrade, because the two products differ in data model, session technology and, for LN Enterprise Edition, the underlying runtime. The checklist centers on inventorying customizations, converting master data, rebuilding logic rather than porting it, and running a real parallel test before cutover.
Error fixInfor LN bshell Process Stuck at 100% CPU: How to Diagnose and Fix It
A bshell process pinned at 100% CPU on the Infor LN application server almost always means one session is stuck in a 4GL loop, scanning an unindexed table, or waiting on a database lock. End the session from the Sessions Monitor first, then kill the OS process only if that fails, and check for a blocking database transaction before assuming it is a bug.
Error fixInfor LN Not Authorized to Run This Session: How to Fix It
Infor LN refuses to open a session with a not authorized message when the logged-in user's assigned role does not include that session, or when the session is blocked for the company they are logged into. Grant the session through Common > Authorization Management > Roles, or check the user's role and company context, and the session opens on retry. In most cases this is a permissions configuration issue, not a bug.
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.
Stuck on Infor LN?
Talk to engineers who work inside Infor LN every week, and who build private AI that answers these questions from your own ERP data.