# Infor M3 ION BOD Message Volume Calculator

> Source: https://netray.co/tools/infor-m3-ion-bod-message-volume-calculator
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Size the BOD volume M3 13.x publishes through ION from your order lines and master data changes, with peak hour load and retention storage.

## Category

infor-cloudsuite

## Erp

Infor M3

## Audience

- Integration developer
- ION administrator
- M3 technical consultant

## Tool

**Kind:** calculator

**Inputs:**

#### Customer order lines per day

**Key:** co

**Type:** number

**Default:** 3000

**Min:** 0

**Step:** 100

**Unit:** lines

#### BODs per customer order line

**Key:** bco

**Type:** number

**Default:** 3

**Min:** 0

**Step:** 0.5

**Unit:** BODs

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

#### Purchase order lines per day

**Key:** po

**Type:** number

**Default:** 1000

**Min:** 0

**Step:** 50

**Unit:** lines

#### BODs per purchase order line

**Key:** bpo

**Type:** number

**Default:** 2

**Min:** 0

**Step:** 0.5

**Unit:** BODs

#### Item changes per day

**Key:** item

**Type:** number

**Default:** 200

**Min:** 0

**Step:** 10

**Unit:** changes

#### Customer and supplier changes per day

**Key:** party

**Type:** number

**Default:** 50

**Min:** 0

**Step:** 5

**Unit:** changes

#### Average BOD size

**Key:** kb

**Type:** number

**Default:** 12

**Min:** 1

**Step:** 1

**Unit:** KB

#### Retention in ION

**Key:** ret

**Type:** number

**Default:** 30

**Min:** 1

**Step:** 1

**Unit:** days

#### Peak hour share of daily BODs

**Key:** peak

**Type:** slider

**Default:** 20

**Min:** 5

**Max:** 100

**Step:** 1

**Unit:** %

**Outputs:**

#### BODs per day

**Key:** bods

**Expr:** co * bco + po * bpo + item + party

**Format:** integer

**Primary:** true

#### MB per day

**Key:** mb

**Expr:** bods * kb / 1024

**Format:** decimal

#### Peak BODs per hour

**Key:** peak_h

**Expr:** bods * peak / 100

**Format:** integer

#### Peak BODs per minute

**Key:** peak_s

**Expr:** peak_h / 60

**Format:** decimal

#### Storage at retention

**Key:** store

**Expr:** mb * ret / 1024

**Format:** decimal

**Primary:** true

**Description:** GB of message content held in ION for the retention period.

**Chart:**

#### BODs per day vs customer order lines

**Type:** line

**X:** co

**From:** 500

**To:** 20000

**Steps:** 40

**Series:**

- bods

**Disclaimer:** 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.

## Content

**Intro:** 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.

**Sections:**

#### How M3 produces BODs

**Body:** 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.

**Bullets:**

- 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

**Body:** 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

**Body:** 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

**Body:** 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.

**Cta:** 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.

**Faq:**

#### What is a BOD in Infor M3?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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.

## Search terms

infor m3 bod, infor m3 bod processor, infor ion bod volume, m3 ion sizing, ion oneview, m3 sync salesorder bod, infor ion message storage

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json