Infor M3 MEC Mapping Design Template (Enterprise Collaborator Interface Spec)
Most MEC problems start with a vague spec. This template gives you a structured design document for each M3 Enterprise Collaborator interface: partner and flow, field mapping, error handling and test cases, ready to export to Word or PDF.
Fill in
Infor M3 MEC Mapping Design Template
MEC Mapping Design: EDI 850 purchase order inbound
Project: Acme M3 EDI rollout Partner: Northwind Components Direction: Inbound to M3 Format: X12 M3 target: OIS100MI AddBatchHead and AddBatchLine Frequency: Every 15 minutes Author: Integration consultant Date: 2026-10-20
1. Purpose and scope
Describe the business process this interface supports, the trigger in the source system and the expected volumes per day and at peak. State what is out of scope.
2. Partner, agreement and flow
List the MEC partner, the agreement, the flow and the channels used (for example AS2, SFTP, HTTP or file). Record IDs, certificates and the test and production endpoints.
3. Field mapping
| Source field | Source rule | M3 field | Transformation | Mandatory | Comment |
|---|---|---|---|---|---|
| PO number | BEG03 | CUOR | Direct | Yes | |
| Ship-to code | N104 where N101=ST | ADID | Lookup in partner cross-reference | Yes | |
| Item (buyer) | PO107 | ITNO | Cross-reference to M3 item | Yes | |
| Quantity | PO102 | ORQT | Number, decimal check | Yes | |
4. Error handling
Rejected messages are written to the MEC error queue and an email goes to the order desk. Corrected messages are resubmitted from Partner Admin after the master data fix.
5. Testing
Describe test cases: valid message, unknown item, unknown ship-to, zero quantity, duplicate message, oversized message. Record expected results and the test partner contact.
6. Approvals
The field mapping rows are examples for an X12 850 into customer order batch transactions; the segment references and M3 field names must be checked against your partner implementation guide and your M3 version. This template is a starting point for documentation and does not replace the MEC tool configuration.
MEC interface backlog review
Optional: a short review of your EDI and integration backlog to see which mappings could be drafted with assistance.
Optional. The tool and every export work without this. No spam.
How to use the template
Fill in the fields at the top, then export the document and complete the mapping table by hand or in your editor. Keep one document per interface and per direction. Share it with the partner and the business owner before you build the map, so the segment rules and the expected M3 result are agreed in writing.
What a good MEC mapping spec contains
It states the source rule for each field, the target M3 field, the transformation and whether the field is mandatory. It lists cross-reference tables for partner codes versus M3 codes, which are the most common source of rejected messages. It also states what happens on error, who is told and how a message is resubmitted.
- Partner, agreement, flow and channel identifiers
- Source rule, target field and transformation per row
- Cross-reference tables with an owner for upkeep
- Error queue, notification and resubmission process
- Test cases with expected outcomes
Common mistakes
Do not leave cross-references to the end; unknown item or ship-to codes cause most failures in the first week. Avoid hardcoding partner codes inside the map when a lookup table can be maintained by business users. Test with real partner messages, not only with your own cleaned samples, because production data has optional segments, long text and unexpected qualifiers.
Frequently Asked Questions
What is MEC in Infor M3?
MEC is M3 Enterprise Collaborator, the integration and EDI component used with M3. It receives and sends messages, applies mappings between external formats and M3 interfaces, and provides tooling to configure partners, agreements and flows.
Do I need a separate document for each interface?
Yes, one per interface and direction is the practical rule. It keeps the mapping, the test cases and the approvals tied to one change and makes later support easier.
Can this template cover non-EDI integrations?
Yes. Choose XML, CSV or JSON as the format and describe the channel. The mapping structure of source field, rule, target field and transformation is the same.
Is the example mapping correct for my partner?
It is only an illustration. Segment references and required fields come from your partner implementation guide. Always replace the rows with the ones from the guide.
If your EDI mapping backlog is long, Netray can help draft and check mapping specs against your message samples, with your consultants approving the result.
Related Tools
Infor M3 MI API Transaction Call Generator
Fill in program, transaction and parameters to get a ready M3 REST call as URL, curl and a JavaScript fetch snippet.
Infor M3 & CloudSuiteInfor M3 Program Reference (MMS001, OIS100, PMS100)
Searchable lookup of frequently used Infor M3 programs by code, area and purpose, so you stop hunting through menus.
Infor M3 & CloudSuiteInfor M3 Upgrade Test Checklist
A structured test checklist for an M3 upgrade or update, covering technical checks, core processes, integrations and cut-over.
Infor M3 & CloudSuiteInfor M3 H5 Script Review Checklist
A review checklist for H5 Client scripts covering design, coding, security, testing and upgrade risk.
More Infor M3 & CloudSuite tools
See all- Infor M3 Customer Order Status Tracking Worksheet
- Infor M3 Item Master Upload Worksheet
- Infor M3 Facility and Warehouse Structure Worksheet
- Infor M3 Fit-Gap Analysis Worksheet
- Infor M3 Interface and Integration Inventory Worksheet
- Infor M3 Functional Specification Template
- Infor M3 User Acceptance Test Script Template
- Infor M3 Implementation Effort Estimator
- Infor M3 Go-Live Readiness Checklist