SAP TCodes · LessonReviewed by Anitha M, SAP Trainer, 13 yrs · Updated · Published · SAP S/4HANA 2023 · all levels
SAP MM01
MM01 is the SAP transaction code for Create Material (MM). It creates a material master record, choosing the views (basic, purchasing, sales, MRP, accounting, etc.) to maintain, the foundational logistics master data.
Quick answer
MM01 creates a material master record, choosing the views (basic, purchasing, sales, MRP, accounting, etc. ) to maintain, the foundational logistics master data.
Key takeaways
- Watch out: material type and base unit of measure are effectively permanent once set.
Purpose
It creates a material master record, choosing the views (basic, purchasing, sales, MRP, accounting, etc.) to maintain, the foundational logistics master data.
Key fields and screen
- Material number (or auto), material type, industry.
- Views to maintain and their organizational levels (plant, sales org, storage location).
- View data (descriptions, units, MRP, valuation).
- Accounting view (valuation class, price).
Tips
- Maintain all views the process needs (esp. accounting to post, purchasing to order).
- Material type controls behaviour/defaults.
- Use a reference material to speed creation.
Common errors
- Missing view blocks a downstream process.
- Wrong material type/valuation class.
- Duplicate material (governance/MDG prevents this).
Common pitfalls
- Copying a reference material without reading every field. The copy brings settings nobody chose, and a wrong MRP type or valuation class inherited this way is discovered months later.
- Choosing a material type for convenience. It drives the number range, the procurement type, the valuation and which views exist, and it cannot be changed afterwards.
- Setting the base unit of measure carelessly. Everything converts from it, and changing it once stock or documents exist is effectively impossible.
- Creating in production before the process owner has agreed the values. Each view has an owning function, and creating first means correcting later across all of them.
- Extending views one error at a time. Decide the full set the process needs before you start, or you will meet each missing view as a failure in a different transaction.