Infor M3 & CloudSuiteFree calculatorPDF, Excel, Word exportInfor M3All Infor M3 tools

Infor M3 ION BOD Message Volume Calculator

This calculator estimates how many BODs an on-prem Infor M3 13.x system publishes to ION per day from order and master data activity, and what that means for peak load and message storage. Every per-event count is an input, because it depends on your configuration.

Your numbers

lines
BODs

Sync messages over the line lifecycle (entry, changes, allocation, delivery). Count it in ION for a sample day.

lines
BODs
changes
changes
KB
days
20 %

Your results

BODs per day
11,250
Storage at retention
3.8624
GB of message content held in ION for the retention period.
MB per day
131.8359
Peak BODs per hour
2,250
Peak BODs per minute
37.5

Per-event BOD counts are inputs; they depend on which BOD processors and noun publications are enabled in your M3 and on how often records change. Measure a real day in ION before sizing infrastructure.

Save results:

BODs per day vs customer order lines

Sweeps Customer order lines per day from 500 to 20000, holding your other inputs fixed.

Get your ION volume estimate reviewed

Send a day of BOD counts from OneView and we will review the sizing and which publications you could switch off.

Optional. The tool and every export work without this. No spam.

Was this tool useful?

How M3 produces BODs

M3 publishes BODs (business object documents) to ION when records change and the corresponding BOD publishing is enabled. Order lines that are changed several times in their life produce several Sync messages, which is why the per-line factor is often greater than 1. Master data such as items, customers and suppliers is published when it changes. Which nouns M3 publishes, and with which verbs, is covered in the companion BOD verbs and nouns reference.

  • BODs per day = CO lines x BODs per line + PO lines x BODs per line + item changes + party changes
  • MB per day = BODs x KB / 1024
  • Storage GB = MB per day x retention days / 1024

Measuring real counts

Use ION OneView to look at the messages for one ordinary business day, filtered by the M3 logical ID and by document type, and count them per noun. Divide the sales order and purchase order counts by the order lines entered that day to get the per-line factors. Take the average message size from a sample of documents in OneView. Repeat for a month-end day, which is often the real peak.

Worked example

3,000 customer order lines at 3 BODs each plus 1,000 purchase order lines at 2 each, 200 item changes and 50 party changes give 11,250 BODs per day. At 12 KB that is about 132 MB per day, and with 30 days of retention about 3.9 GB. If 20 percent of the day falls in the busiest hour, ION must handle about 2,250 BODs in that hour, around 38 per minute.

Common surprises

Mass updates, for example a price list or item attribute change run as a batch job, can publish thousands of master data BODs in minutes and dwarf the daily order traffic. Enabling publishing for nouns no subscriber uses adds load for nothing, so check subscribers in your document flows. Retention set long for troubleshooting multiplies storage; agree retention with whoever supports the integrations.

Frequently Asked Questions

What is a BOD in Infor M3?

A BOD is an XML business object document based on the OAGIS standard that Infor applications exchange through ION. It has a verb such as Sync, Process or Acknowledge and a noun such as SalesOrder, PurchaseOrder or ItemMaster. M3 publishes and receives BODs to integrate with other Infor and third-party applications.

What is the M3 BOD processor?

It is the part of M3 that creates outbound BODs from M3 data changes and processes inbound BODs into M3, depending on what is enabled for each document type. Its settings decide which events publish which nouns, and therefore drive the per-event counts you enter in this calculator.

How can I reduce BOD volume from M3?

Disable publishing for nouns no document flow subscribes to, avoid mass updates in business hours, and check whether a subscriber really needs every change or just a daily snapshot. Measure in ION OneView before and after each change.

Does message size matter for ION sizing?

Yes, for storage and network. Count drives processing load, while size times count times retention drives storage. Large documents such as orders with many lines can be many times the average, so take the average from a real sample.

If you want people to ask questions about M3 orders and their integration status in plain English on your own servers, we can set that up.

ArchRay builder
Design the on-prem AI stack for Infor M3: model, GPUs, RAG pipeline, guardrails
See memory, speed and cost as you swap parts, then export the diagram. Free, in your browser.
Open the builder

Keep exploring

Free tools

ERP fixes and how-tos

Runs with your ERP

Guides

AI on your ERP

Integrations

Comparisons

Software