How-toInfor M3 (M3 Business Engine)Item Master / MMS001

How to Create a New Item in M3 (MMS001)

Question

How do I create a new item in M3 (MMS001)

Also searched as

M3 MMS001 item setup steps
how to add a new item number in M3
M3 item basic data vs facility data difference
MMS001 required fields for new item

Short answer

A new item in M3 is created in two stages: item basic data in MMS001 (Item. Open), which defines company-wide attributes such as description, item group and unit of measure, then facility-level data in MMS002 (Item/Facility. Connect), which attaches the item to a specific warehouse or plant with purchasing, planning and costing parameters. An item is not usable for orders, purchasing or MRP until both stages are complete.

Applies to: Infor M3 Business Engine 10.x-14.x, M3 H5 Client and M3 UI Adapter

Create an item end to end in M3

1Open MMS001 (Item. Open) and create the item number, either manually or via the item number series defined in CRS165 (Number Series. Open) if automatic numbering is used.
2Enter the item basic data: item name/description, item group (MMS010), item type, basic unit of measure (weight/volume UOM if applicable), and statistics group.
3Set the item's responsible planner group and item category if your company uses them for reporting or MRP segmentation - these carry through to planning and purchasing screens later.
4Save the header record, then go to MMS002 (Item/Facility. Connect) and connect the item to the facility (warehouse) where it will be stocked, purchased or manufactured.
5On the facility connection, set the item type per facility (purchased, manufactured, phantom, etc.), planning method (MRP, reorder point, manual), lead time, and lot size rules.
6Enter costing data - standard cost elements or the cost model your company uses - since MRS/CRS costing programs and the manufacturing order costing all read from the facility item record.
7If the item is purchased, connect it to a supplier via PPS040 (Item/Supplier. Connect) or CRS620 so purchase orders can default price, lead time and supplier item number.
8If the item is sold, verify sales price and item text records exist (OIS011/CRS395 depending on version) before releasing the item for order entry.
9Run a test transaction - a purchase order line, a stock receipt, or an order line - to confirm the item behaves correctly in planning and costing before it goes into daily use.

Why item creation is split into two records

M3 separates item basic data (MMS001) from facility data (MMS002) because a single item number can be stocked, manufactured or purchased differently at different facilities within the same company - one plant might manufacture the item while another only stocks and sells it. The basic data record holds attributes that must be identical everywhere the item is used, such as description and base unit of measure, while the facility record holds everything that varies by location: planning method, lead time, safety stock, and cost.

This split trips up new users constantly: an item created in MMS001 with no facility connection will not appear on MRP runs, purchase requisitions, or most order entry pick lists, because those processes query the facility-level table, not the basic item table. If a planner reports an item is missing from MRP, the first thing to check is whether MMS002 exists for the relevant facility.

Fields that are easy to get wrong

Basic unit of measure and alternate units are set once and are expensive to change later - changing the basic UOM after transactions exist requires a conversion and can break historical reporting, so confirm it before the first receipt. Item type (raw material, manufactured, phantom, service) drives which programs treat the item as stockable versus non-stockable, and a phantom item set up as a normal manufactured item will show incorrect on-hand balances in MRP explosions.

Planning method on the facility record (MRP-planned, reorder point, or manual) determines whether MRS500/MRS002 planning runs generate suggestions for the item at all - an item left on manual planning by default will never get a planned order no matter how low stock runs.

Copying items instead of creating from scratch

For items in the same family (variants of a base product, or a new item that mirrors an existing supplier part), M3 supports copying an existing item's basic and facility data as a starting point rather than re-entering every field. This preserves item group, planning method, and cost model consistency across a product family and is the fastest way to avoid setup errors when adding many similar items during a new product introduction.

Common pitfalls

!Creating the item in MMS001 and forgetting MMS002 - the item silently does not exist for planning, purchasing or costing at that facility.
!Setting the wrong item type (for example manufactured instead of phantom) causes MRP to plan orders for a component that should net through instantly.
!Leaving planning method on manual by default means the item never generates MRP suggestions even when stock is negative.
!Changing basic unit of measure after transactions exist without running the proper UOM conversion, which corrupts historical quantity reporting.
!Not connecting a purchased item to a supplier record before purchasing tries to create a PO line, which forces manual price and lead time entry every time.
!Skipping the item/warehouse safety stock and lead time fields, which makes the first MRP run after go-live generate unrealistic order dates.

How an ERP-grounded AI assistant handles this

ERPray, grounded on a company's own M3 item and facility tables, can answer setup questions like which fields are mandatory for a given item type, or check on demand whether an item has a facility connection, a supplier link and a sales price before it goes live, flagging the specific missing record rather than making the planner click through MMS001, MMS002 and PPS040 to find the gap.

See ERPray

Frequently asked questions

Can an item exist in M3 without a facility connection?

Yes, the MMS001 basic record can be saved on its own, but the item will not appear in MRP, purchasing, or most order entry screens until an MMS002 facility connection is added for the relevant warehouse or plant.

What is the difference between item group and item category in M3?

Item group (MMS010) is typically used for accounting and costing default derivation, while item category is a free-form classification field used mainly for reporting and analysis; the exact use of category varies by company configuration.

How do I bulk-create items in M3 instead of entering them one at a time?

Use MMS850/MMS851 (Item. Import File) or an M3 API integration calling MMS200MI/MMS002MI transactions from a spreadsheet or middleware load, which is the standard approach for new product introductions involving many items.

Why does a new item not show up in MRP after MMS001 and MMS002 are both created?

Check the planning method on the facility record - if it is set to manual instead of MRP-planned or reorder point, the item is intentionally excluded from planning suggestions until that field is changed.

Error fix

M3 API Error: Record already exist

Record already exist means the MI Add transaction you called is trying to insert a key that is already present in the target M3 table, most often because a prior call succeeded and was retried, or because the key fields you built do not match what you think they match. Read the errorField and errorFieldGroup attributes on the response to see exactly which key field M3 flagged, then either switch to the matching Chg (change) transaction or fix the key construction in the caller.

How-to

How to Enter a Customer Order in M3 (OIS100)

OIS100 (Customer Order. Open) is the primary M3 program for entering and maintaining customer orders, built as a header-then-line workflow: you first create the order header with customer, order type and delivery terms, then add order lines that each carry their own item, quantity, price and delivery date defaulted from customer and item agreements.

Advanced

How to Call M3 API (MI Programs) Through ION API

Calling M3 from an external system today almost always means going through ION API rather than the older direct MvxAPI SOAP endpoint: you create an ION API authorized app or service account in the ION API portal, download its .ionapi credential file, obtain an OAuth 2.0 access token, and call the M3 MI program transaction through the m3api-rest execute endpoint with that token.

How-to

How to Run MRP in SyteLine

MRP in SyteLine runs from Planning > MRP Processing as either a full Regenerative run or a Net Change run against demand from customer orders, forecasts, and safety stock; results appear as planned orders and Action Messages in the Planner Workbench.

Advanced

Paging M3 API MI List Transactions Past the Default Record Limit

M3 List transactions (the read/browse transaction most MI programs expose, such as CRS610MI.LstByNumber or OIS100MI.LstOrderHead) cap the rows returned per call using the MaxReturnedRecords input field, and by default many clients leave it low or unset, which looks like the API silently truncating results. Set MaxReturnedRecords explicitly, then loop the call using the last key values from the previous page as the starting position until fewer rows than the limit come back.

Error fix

M3 API Error: Not Authorized to Program

Not authorized to program (or the equivalent transaction-level authorization error) means the M3 user ID the integration authenticates as can log in fine but has not been granted access to that specific MI program, transaction, or company/division through its authority group. Fixing it means adding the program/transaction to the integration user's authority group in M3, not changing anything in the calling code.

AI for ERP

AI for Infor M3: A Practical Path from MI Programs to a Private Assistant

Add grounded AI to Infor M3: natural-language answers over MI programs and MEC, agents for distribution and manufacturing, on-prem or private cloud in Europe.