What Is BOD (Business Object Document)?
Also known as: Business Object Document, BODs, OAGIS BOD
Definition
A BOD (Business Object Document) is the standardized XML message format Infor applications use to exchange data through ION. Each BOD pairs a verb such as Sync or Process with a noun such as ItemMaster, based on the open OAGIS integration standard.
BOD (Business Object Document) Explained
BODs come from the Open Applications Group Integration Specification, an open standard Infor adopted so its acquired product lines could talk to one another without point-to-point mapping. The message name is always verb plus noun. Sync.ItemMaster publishes the current state of an item so any subscriber can mirror it. Process.PurchaseOrder asks a receiving application to act on a document. Acknowledge, Get, Show, Load, and Update round out the common verb set, each with defined semantics about who owns the data and what the receiver is expected to do.
Structurally a BOD has two halves. The ApplicationArea carries routing and control metadata: sender logical ID, creation timestamp, and a BOD ID that ION uses for tracing and idempotency. The DataArea carries the verb element and one or more noun documents with the actual payload. Identifiers use accounting entity and location qualifiers so the same item number in two SyteLine sites resolves unambiguously, which is precisely the problem that defeats naive CSV integrations in multi-site manufacturers.
In a SyteLine landscape, BOD publication is driven by replication or event configuration that detects a change, builds the XML, and hands it to ION Connect. ION then applies the document flow: routing rules, filters, mappings, and any workflow or alert triggers. Subscribers receive the BOD and process it through their own connection point. Because everything is standard XML flowing through a broker, you get monitoring and error queues that a direct database link can never provide.
The common misconception is that BODs are a SyteLine feature. They are not - they are an Infor OS integration standard used across LN, M3, CloudSuite Industrial, EAM, and others. That is exactly the point: a manufacturer running SyteLine at one plant and LN at another can publish Sync.ItemMaster from both into a common flow. The trade-off is verbosity. BOD XML is large, and high-volume transaction integrations sometimes justify a direct IDO REST call instead.
Why It Matters
- BODs let mixed Infor estates integrate on a common contract instead of building bespoke mappings for every application pair.
- The standard identifier scheme resolves the multi-site, multi-entity ambiguity that breaks flat-file integrations in manufacturers with several plants.
- ION's BOD tracing gives auditable, replayable message history - a real advantage for regulated aerospace and defense suppliers.
- Choosing BODs versus direct REST calls determines integration latency and volume ceilings, so the decision belongs in architecture, not implementation.
In Practice
A frequent gotcha is the accounting entity qualifier. Two SyteLine sites publishing Sync.ItemMaster with the same item number but mismatched entity IDs will either collide or create duplicates in the subscriber. Fix the logical ID and entity configuration in ION before turning on the flow, not after the first duplicate item shows up in the data lake.
Frequently Asked Questions
What is the difference between a Sync BOD and a Process BOD?
A Sync BOD publishes the current state of a business object so subscribers can mirror it; the publisher owns the data and the receiver simply updates its copy. A Process BOD requests that the receiving application perform work, such as creating a purchase order. Sync is informational replication; Process is a request for action with an expected Acknowledge response.
Do I have to use BODs to integrate with SyteLine?
No. BODs are the standard path when you are integrating across Infor applications through ION, and they give you tracing, replay, and workflow. For high-volume or low-latency needs, or when integrating a non-Infor system directly, calling SyteLine's IDO REST endpoints is often simpler and faster. Many landscapes use both patterns for different flows.
Related Terms
Infor ION
Infor ION is the integration backbone of Infor OS. It routes BOD messages between Infor applications such as SyteLine, LN, and M3 and third-party systems, and adds document flows, workflow, event alerts, and a monitored, replayable message trail.
IDO (Intelligent Data Object)
An IDO (Intelligent Data Object) is the middle-tier business object in SyteLine and the Mongoose framework that exposes database tables as named properties, methods, and collections, so forms, mobile apps, and REST clients all read and write data through one governed layer.
CloudSuite Industrial
CloudSuite Industrial (CSI) is the cloud-delivered edition of Infor SyteLine, hosted by Infor on AWS alongside the Infor OS platform. It uses the same Mongoose application but adds managed updates and restricts customization and direct database access.
Go Deeper
SyteLine Implementation Cost Calculator
Estimate the full first-year cost of an Infor SyteLine implementation, including licensing, services, data migration, and internal effort.
SyteLine ION API Integration Guide
Step-by-step SyteLine ION API integration guide: API gateway setup, OAuth 2.0 tokens, BODs vs IDO endpoints, and secure on-prem to cloud connections.
The SyteLine Mongoose Framework: A Developer Guide
SyteLine Mongoose is the metadata framework behind Infor SyteLine and CloudSuite Industrial: IDOs, WinStudio forms, application events, and scripting explained.
Working with BOD (Business Object Document) in a live environment? Our engineers do this every day - and our AI agents automate most of it.
Try it here, free
SyteLine ION Outbound BOD Reference
Every outbound BOD SyteLine/CSI generates for ION, with verb, noun, the Infor applications Infor lists as receivers and the business area.
New to Infor SyteLine? Start with the Infor SyteLine guide and toolkit, or plan with Training Path Builder, ERP Certification Study Planner, Upgrade Path Planner.
Keep exploring
Free tools
- SyteLine ION Outbound BOD ReferenceEvery outbound BOD SyteLine/CSI generates for ION, with verb, noun, the Infor applications Infor lists as receivers and the business area.
- SyteLine ION BOD Integration Go-Live ChecklistSetup, scope, testing, cutover and hypercare checks for BOD based integrations between SyteLine or CSI 10 on-prem and Infor ION.
- SyteLine ION BOD Message Volume CalculatorEstimate how many outbound BODs SyteLine sends to ION per day, the peak rate per minute and the outbox storage if BODs are kept.
ERP fixes and how-tos
- SyteLine EDI or BOD inbound document fails to create a sales orderWhy an inbound EDI order or ION BOD fails to create a SyteLine sales order, and how to trace the failure through the EDI error log or ION BOD inbox to the root cause.
- Diagnose and fix a failed BOD document flow in ION DeskDiagnose a failed BOD document flow in Infor ION Desk: read the error detail, check the mapping, and resubmit safely without duplicating transactions.
- How to Set Up an ION Workflow Approval for SyteLine Purchase OrdersHow to build an ION workflow approval for SyteLine purchase orders: trigger from a BOD, route to approvers by amount, and write the result back safely.
Guides
- Infor ION BOD Message Processing GuideMaster Infor ION BOD message processing with document flow configuration, XML mapping, transformation rules, and error handling for CloudSuite integrations.
- Infor ION Connect Setup for SyteLine IntegrationConfigure Infor ION Connect for SyteLine data integration. Set up connection points, document flows, BODs, and ION API Gateway for CloudSuite Industrial.
- SyteLine ION API Integration: The Complete GuideStep-by-step SyteLine ION API integration guide: API gateway setup, OAuth 2.0 tokens, BODs vs IDO endpoints, and secure on-prem to cloud connections.