Infor CloudSuite (M3, LN)
How Infor M3 and Infor LN reach BatteryPass through the ION API Gateway.
This page describes an integration pattern. BatteryPass ships no connector for Infor and has no partnership with Infor; nothing here is a vendor approval.
The LN OData entities and the BOD messages below are not checked against Infor's documentation (marked "not checked" in the table). Confirm protocol versions and entities with Infor or your partner before you build on them.
Every call goes through the ION API Gateway with OAuth 2.0 client credentials. The credentials come in an .ionapi
file; treat it as a secret like the BatteryPass key: keep it in a vault, never in a repository, and give each
integration its own. In M3 the middleware calls MI programs through the gateway; in LN it reads business data
entities.
For units from production the middleware reads the serial
numbers of finished orders and writes a file with the generic-csv preset. Infor ION can also publish Business Object
Documents (BODs) when data changes; use them as triggers and read the details through the gateway.
Interfaces and how they were checked
- Vendor
- Infor
- Deployments
- Cloud: Infor M3 and Infor LN on Infor OSOn-premise: Infor M3 and Infor LN with Infor OS on-premises
Every call goes through the ION API Gateway; the credentials are in an .ionapi file, which is to be treated as a secret.
An integration pattern, not a connector: BatteryPass ships no ERP connector and holds no vendor certification.
| Interface | Protocol | Sign-in | Events | Objects | Checked |
|---|---|---|---|---|---|
ION API GatewayAccess to the APIs of M3 and LN | REST | OAuth 2.0 client credentials | none | Product/material master, Batch/serial number, Production order, Delivery/goods issue, Return | checked in the vendor documentation, 24/10/2026 |
M3 MI programsM3 programs through the ION API Gateway | REST | OAuth 2.0 client credentials | none | Product/material master, Batch/serial number, Production order, Delivery/goods issue | checked in the vendor documentation, 24/10/2026 |
LN OData (BDE)LN business data entities | OData V4 | OAuth 2.0 client credentials | none | Product/material master, Batch/serial number, Production order | not checked |
Business Object Documents (BODs)Messages through Infor ION | BOD (Infor ION) | OAuth 2.0 client credentials | Business events (not signed) | Product/material master, Production order, Delivery/goods issue | not checked |
Notes
LN OData (BDE): Protocol version and entities not checked.
Import presets
Generic CSV file (generic-csv): For any ERP and for files a middleware writes itself: GTIN, serial number, manufacturing date, facility (name or GLN), model version and battery status, with German and English column names.
| Column in the export | Field in BatteryPass |
|---|---|
GTIN (also EAN, GTIN-13, GTIN-14) | GTIN (GS1) identification.gtin |
Serial number (also Seriennummer, serial_number) | Serial number identification.serial_number |
Manufacturing date (also Herstelldatum, manufacturing_date) | Manufacturing date identification.manufacturing_date |
Facility (also Produktionsstätte, Facility GLN, Werk-GLN) | Place of manufacture identification.manufacturing_place |
Model version (also Modellversion, model_version) | Model version model_version |
Battery status (also Batteriestatus, battery_status) | Battery status identification.battery_status |
Workflows
- Units from production: Serial numbers from the production confirmation or goods receipt are staged as an import; members review, commit and approve before any passport appears. Key scopes: import
- Passport links back into the ERP: The middleware follows the change feed and writes the GS1 Digital Link and the passport status to the serial number record in the ERP, so labels and delivery papers carry it. Key scopes: read
- Condition data from BMS and service: A battery management system or a service tool reports measurements such as capacity fade or cycles; BatteryPass accepts newer measurements and publishes according to the organisation's policy. Key scopes: readcondition
- Returns and repairs as lifecycle events: Completed repairs, inspections and component replacements from service or return orders appear as events in the unit's history. Key scopes: readcondition
- Product change leads to a new model version: A change to the product master in the ERP triggers a notification; a member creates a new model version in BatteryPass. Declared data is never written automatically. Key scopes: read