MM01 — Create Material Master Record

MM01 builds the material master, the shared record that purchasing, inventory management, production, sales, and accounting all read against a single material number. The structural fact that drives most confusion: there is no one 'material record'. Data is stored client-wide (descriptions, units of measure, basic data), at plant level (MRP, work scheduling, plant-specific purchasing), at storage location level (bin data), at sales organization/distribution channel level (sales view), and at valuation area level (accounting, costing). MM01 presents this as a sequence of selectable views, and the views offered are filtered by the material type (FERT, ROH, HAWA, etc.) and industry sector chosen on the initial screen. Change that combination later and the available fields change with it, which is why two materials of different type can look completely different in the same transaction.

Used at the start of the procure-to-pay or plan-to-produce chain, before any purchase requisition, purchase order, or production order can reference the material. A consultant reaches for MM01 specifically when a genuinely new material number is needed, or when an existing material must be rolled out to a new plant or sales area for the first time. If the material already exists everywhere it is needed and only a value needs to change (price, MRP type, lot size), MM02 is the correct transaction, not MM01. In S/4HANA landscapes, mass creation or governed creation often runs through a Fiori app or a data migration tool instead, with MM01 reserved for one-off manual creation or troubleshooting.

To confirm whether a material was created or merely extended, check MARA for the material number first; if it already exists, MM01 on that number only ever extends, regardless of what the user intended. Then check MARC filtered on material number and plant to see which plants the material is already extended to, and inspect the MMSTA/plant status and deletion flag fields there. For valuation issues, check MBEW filtered on material and valuation area for price control and valuation class. If a view seems to have vanished, cross-check the material type in MARA against the industry sector, since that combination is what determined view availability at creation time.

MM01 itself still exists and behaves the same way in S/4HANA; the underlying view structure and organizational-level logic are unchanged. What has moved is the preferred entry point for high-volume or governed creation, which shifts toward Fiori apps and API-based mass creation, with MM01 remaining the manual fallback and the tool most consultants still use for quick single-record creation or diagnosis. Material type and industry sector configuration continue to drive view availability exactly as before.

Functional (MM) territory for view selection, organizational level entry, and field content. Configuration questions about which views a material type offers, or field selection group behavior, belong to whoever owns material type customizing, often the same MM consultant. A clean handover to Basis or ABAP only applies if the transaction itself errors (authorization objects, dumps); include the material number, material type, industry sector, and the exact view/organizational level combination attempted.

Move to MM02 for anything that is a change to an existing, fully extended material rather than a first-time creation or extension. Use MM03 to inspect what MM01 actually wrote, view by view, before assuming a field is wrong. ME11 is the natural next step once a material has a purchasing view, since a purchasing info record links the material to a vendor and price. MB52 is useful for confirming that a newly extended plant or storage location is actually visible in stock reporting once the material master save is done.