Infor M3 Item Master Upload Worksheet (MMS001 and MMS200MI Load Template)
Item master loads fail on small things: duplicate item numbers, an item group that does not exist, a unit that was never created. This worksheet gives you a clean grid with M3 field codes, a status column and an opening value check so the file is reviewed before it touches M3.
| ITNO Item number | ITDS Name | FUDS Description | ITTY Item type | ITGR Item group | UNMS Basic unit | RESP Responsible | Std unit cost | Opening qty | Opening value | Load status | |
|---|---|---|---|---|---|---|---|---|---|---|---|
$3,000 | |||||||||||
$4,736 | |||||||||||
$2,720 | |||||||||||
$4,250 |
Field codes follow the usual M3 item fields (ITNO, ITDS, FUDS, ITTY, ITGR, UNMS, RESP). The item types, groups and responsible codes in the sample rows are examples; they must exist in your own settings before a load. Mandatory fields and loading transactions (for example in MMS200MI) vary by version, so validate with a small batch in a test tenant first.
Item master clean-up review
Optional: a review of your source item data for duplicates and missing attributes before an M3 load.
Optional. The tool and every export work without this. No spam.
How to use the worksheet
Replace the sample rows with your items. Keep one row per item and use the load status column to track Draft, Reviewed, Approved and Loaded, so a partial load can be resumed. Fill in opening quantity and standard cost if you are also loading balances and the value column will calculate. Export to Excel or CSV and map the columns to your loading tool, such as MMS001 import or MMS200MI calls.
What to validate before loading
Check each value against the settings it points to. Item type, item group, unit of measure and responsible must exist in the corresponding M3 settings programs. Check item number format and length rules from your numbering convention, and make sure descriptions are not truncated by the field length. Duplicates are the most common cause of rejected rows.
- No duplicate ITNO values, including different case
- Every ITTY, ITGR and UNMS exists in M3 settings
- Names within field length limits
- Opening value equals cost times quantity and ties to the finance cut-over
Common mistakes
Loading items first and warehouse data later is fine, but forgetting the warehouse connection (MMS002) leaves items that cannot be used in orders. Another mistake is loading cost through the item and again through a costing program, which doubles setup. Run a pilot of ten items through the whole flow, including a customer order and a purchase receipt, before you load thousands.
Frequently Asked Questions
Which M3 fields are mandatory for an item?
It depends on the version and on settings, but item number, name, item type, item group and basic unit are normally needed. Run a test load in a non-production tenant and read the error messages to learn exactly what your setup demands.
Can I load through MMS001 and through an API?
Yes. Many projects use the standard import functions or the item MI program. The API route gives row-level error messages that are easy to log and retry, which helps on large loads.
How do I load warehouse data?
After items exist, connect them to warehouses in the item warehouse program and set planning parameters. The worksheet only covers basic item data, so create a second sheet for warehouse level fields.
Does this file get uploaded anywhere?
No. All editing happens in your browser and nothing is sent to Netray. Export the file and load it yourself.
For large item clean-ups and duplicate detection before an M3 migration, Netray can run an assisted review over your source data on your own infrastructure.
Related Tools
Infor 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 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 Facility and Warehouse Structure Worksheet
Design the M3 hierarchy of division, facility, warehouse and locations on one sheet, with storage capacity totals.
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.
More Infor M3 & CloudSuite tools
See all- Infor M3 Customer Order Status Tracking Worksheet
- Infor M3 MEC Mapping Design Template
- Infor M3 H5 Script Review Checklist
- 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