Free tool for Infor M3 (formerly Movex)

Infor M3 Integration and EDI Designer

Pick the business objects and the systems you need to connect, and get an Infor M3 integration inventory that names the real interface for each flow: BODs published by the M3 BOD Processor through Enterprise Collaborator and ION (Sync.SalesOrder, Process.ItemMaster), MI API transactions such as OIS100MI AddBatchHead or MMS200MI GetItmWhsBal, or the M3EDI BODs used for EDI. Switch to EDI mode to see how X12 850, 855, 856, 810 and their EDIFACT equivalents map to M3 orders, deliveries and invoices, field by field.

Business objects

Toggle what moves between systems. Presets add a typical set.

Targets, direction and frequency

Direction is seen from M3.

Nothing in scope yet

Pick an object or a preset in step 1.

Integration inventory

Outbound M3 BODs start as table events: Event Analytics rules filter them, the BOD Processor enriches them and Event Hub hands them to Infor Enterprise Collaborator (IEC), which publishes to ION. Each BOD must be enabled per company and division in BOD Processor Administration. Synchronous calls use MI programs through the ION API gateway at /M3/m3api-rest/v2/execute with OAuth 2.0.

Your inventory appears here

Each interface gets the M3 method, the exact artifact and a relative effort score.
Free, optional. Reopen it on any device.
Download the design:

Exports include the inventory, rationale, field maps with your target names, selected EDI maps and risks. No sign-in needed.

How to use it

  1. 1

    Pick the objects

    Select the business objects in scope, such as customers, items, customer orders and deliveries.

  2. 2

    Add the target systems

    For each object choose the system on the other side, the direction seen from M3 and how often it must move.

  3. 3

    Read the inventory

    Each row names the M3 interface (BOD, MI transaction or M3EDI BOD), why it fits and what to watch for.

  4. 4

    Check the field map

    Open the starter map for an object, fill in the target field names and note the keys and required MI fields.

  5. 5

    Export or save

    Download the design as PDF, Excel, Word or CSV, save it to your account, or send it to an engineer for review.

M3 interfaces in this tool

M3 BODs (BOD Processor, IEC, ION) asynchronous
Outbound Sync, Show, Process and Acknowledge BODs generated from M3 table events and published by IEC to ION; inbound Process, Sync and Load BODs run through IEC agreements named M3_<Noun>_<Verb>_In that call MI transactions.
M3 API (MI programs) over ION API REST synchronous
Synchronous MI transactions such as CRS610MI Add, OIS100MI AddBatchHead or MMS200MI GetItmWhsBal, called at tenantURL/M3/m3api-rest/v2/execute through the ION API gateway. The same business logic as the M3 programs runs on each call.
M3EDI BODs asynchronous
M3 specific BOD nouns for EDI, for example Load.M3EDISalesOrder inbound and Sync.M3EDIInvoiceCommon outbound. A translator or EDI service converts X12 or EDIFACT to and from these BODs; M3 publishes them through Event Hub and IEC.
Enterprise Collaborator custom mapping asynchronous
IEC (formerly MEC, M3 e-Collaborator) partner agreements with mappings built in the Business Document Mapper. Mappings can call MI APIs, translate partner codes through CRS881 and CRS882, and read or write flat files defined in the Flat File Definition tool.
Warehouse message interface (MHS850MI, MMS850MI) asynchronous
Message-based transactions for picks, receipts and stock adjustments, for example MHS850MI AddCOPick, AddPOReceipt and MMS850MI AddAdjust. Messages run interactively (*EXE) or in a batch job (*AUT) and failed ones are corrected and rerun in MHS850 or MMS850.
Read APIs (List and Get MI, EXPORTMI, Custom List MI, MDBREADMI) synchronous
Bulk and filtered reads: List and Get transactions of the standard MI programs, EXPORTMI Select queries, custom list MIs defined in CMS015 and MDBREADMI transactions defined in MRS010. Use them for extracts that no BOD covers.
Data Lake Publisher (Infor Data Fabric) asynchronous
Publishes selected M3 tables to Infor Data Lake, through ION or by streaming to Data Fabric. Infor states that only streaming ingestion will be supported in the future, and the switch to streaming is one way.
XtendM3 extensions synchronous
Custom APIs, transactions and dynamic tables written as XtendM3 extensions for CloudSuite M3, where modifications are not allowed. Use them when no standard MI transaction exposes the data or update you need.

Questions

What is the difference between M3 BODs and the M3 API (MI programs)?

BODs are asynchronous XML messages. M3 generates them from table events, filters them with Event Analytics rules, enriches them in the BOD Processor and publishes them through Event Hub and Enterprise Collaborator to ION. MI programs (for example CRS610MI, OIS100MI, MMS200MI) are synchronous APIs: you call a transaction and get the result immediately, which suits lookups, price checks and creates that need the new number back.

Why does M3 not publish a BOD that is in the list?

Each outbound BOD must be enabled per company and division in BOD Processor Administration (role M3EC-Administrator). Some BODs also need a rule enabled, for example the SyncInvoice rule per invoicing function. Check Event Hub for the M3BEBOD events and the Enterprise Collaborator Administration page for failed messages.

How do I create a customer order in M3 through the API?

Use the batch order transactions in OIS100MI: AddBatchHead with the customer number (CUNO) returns a temporary order number, AddBatchLine adds items (ITNO, ORQT), and Confirm converts the batch order into a customer order with M3 pricing, credit check and allocation. Process.SalesOrder is the BOD equivalent delivered for Infor CPQ, CRM and Rhythm for Commerce.

How does EDI work in Infor M3?

M3 does not parse X12 or EDIFACT in the Business Engine. A translator or EDI service converts partner messages to M3EDI BODs, for example Load.M3EDISalesOrder for incoming orders and Sync.M3EDIInvoiceCommon for invoices, and ION and Enterprise Collaborator move them in and out of M3. Custom partner agreements in IEC can also map messages directly and call MI APIs. Partner code translation uses CRS881 and CRS882.

How do I call the M3 API on CloudSuite?

Calls go through the ION API gateway. Create or download the .ionapi credentials, obtain an OAuth 2.0 token and call tenantURL/M3/m3api-rest/v2/execute followed by the program and transaction, for example OIS100MI and GetHead. The tenant URL is the part of the Infor M3 endpoint URL in API Gateway that comes before /M3/.

In what order should I load M3 customer BODs?

Infor documents the sequence: CustomerPartyMaster, then BillToPartyMaster, PayFromPartyMaster and ShipToPartyMaster, because each refers to the earlier ones. CustomerPartyMaster, BillToPartyMaster and PayFromPartyMaster come from OCUSMA and ShipToPartyMaster from OCUSAD.

How do I process inbound warehouse messages in batch?

Set the control property m3beWarehouseInterfaceProcessFlag on the M3_<Noun>_<Verb>_In agreements. *AUT processes messages in a batch job and is recommended for high volume; failed messages are corrected and rerun in MHS850. *EXE processes them interactively. Register the sending system as a message partner in MMS865 with message type BOD.

How do I get M3 data into a data warehouse?

Use Data Lake Publisher to publish the tables you need (for example MITMAS, OOHEAD, FGLEDG) to Infor Data Lake, through ION or by streaming to Data Fabric. Infor states streaming will become the only supported ingestion and the switch from ION is one way. For an initial load, Infor recommends the initial load function over the older EVS002MI Initiate method.