What is a BOD at Infor?

And why it makes communication between systems so much easier

Connecting systems should not feel like translating between two foreign languages. After all, we want our systems to talk to each other—clearly, reliably, and without misunderstandings. This is exactly where Infor’s BODs (Business Object Documents) come into play.

What exactly is a BOD?

A Business Object Document (BOD) is, simply put, a standardized “data package” that securely exchanges information between different systems.

Technically, it is based on the XML format defined by the Open Applications Group (OAGi).

A BOD always contains three crucial elements:

What is in the package – i.e., the actual business data (e.g., an order or inventory)

Where it is going – the target system that is to receive the data

How it is transported – via the trusted Infor ION network

In this way, Infor ensures that applications such as Infor LN, Infor CloudSuite Industrial (CSI), and other systems can communicate reliably with each other – without complicated interfaces or upgrade concerns.

Structure of a BOD

A BOD typically consists of several layers:

  • Header: Contains metadata such as sender, recipient, time of creation, and document type.
  • Business Object: The actual business data object, e.g., an order, an invoice, or a stock entry.
  • Payload: Detailed information about the business data object – i.e., all relevant fields such as item number, quantity, price, or customer information.


Thanks to this clear structure, BODs can be easily transferred and processed between systems.

Examples of BODs

Some typical BOD types at Infor are:

  • OrderBOD: Represents a customer order.
  • InvoiceBOD: Contains invoice information.
  • ShipmentBOD: Describes delivery details and shipping information.


This standardization makes it possible to efficiently automate processes such as order processing, invoicing, and warehouse management—across system boundaries.

Advantages of BODs

Standardization:
Uniform formats reduce misunderstandings between systems and simplify maintenance.

Automation:
Processes are easier to automate because systems can process the data directly—without detours or additional translations.

Error reduction:
Fewer manual entries mean fewer human errors and higher data quality.

Integration:
The uniform structure also makes it much easier to integrate third-party systems into the Infor landscape.

And what does this have to do with Infor ION?

Infor ION is the integration platform through which BODs are transported. It ensures that documents reach their destination securely and that each system knows what to do with the data it receives.

The best part is that this architecture remains stable even after updates. In concrete terms, this means no nasty surprises after a system upgrade and no costly adjustments to interfaces.

In short

A BOD is the “common language” that Infor systems use to exchange data—standardized, secure, and upgrade-proof.

This makes it much more than just a technical format: it is the key to smooth communication between systems that would otherwise not talk to each other.

Curious? Simply ask us

Header image: Header- & featured image by FELLOWPRO

Share: