SAP TCodes · LessonBy Ravi M, SAP Trainer, 10 yrs · Published · SAP S/4HANA 2023 · all levels
MM02
MM02 is the SAP transaction code for Change Material (MM). It changes an existing material master, adding views or updating data (e.g. MRP settings, prices), across the functional areas that own each view.
Quick answer
MM02 changes an existing material master, adding views or updating data (e. g. MRP settings, prices), across the functional areas that own each view.
Key takeaways
- View(s) and organizational level to change.
- Editable fields per view.
- Add missing views here (e.g. extend a material to a new plant).
- Watch out: Using the wrong variant (e.g. create vs change vs display).
Purpose
It changes an existing material master, adding views or updating data (e.g. MRP settings, prices), across the functional areas that own each view.
Key fields and screen
- Material number.
- View(s) and organizational level to change.
- Editable fields per view.
- Change documents (history).
Tips
- Add missing views here (e.g. extend a material to a new plant).
- Coordinate changes with the owning function (each view has an owner).
- Use change documents to audit what changed.
Common errors
- Changing valuation-relevant fields with stock present (restrictions).
- Inconsistent data across views.
- Unauthorized change to another function’s view.
Common pitfalls
- Using the wrong variant (e.g. create vs change vs display).
- Missing prerequisite master data or config.
- Not checking the resulting document/postings.
Practice challenge
+0 XPStreak ×0
Question 1 of 3
Which statement is true of MM02?
Frequently asked questions
What does MM02 stand for in SAP?
MM02 is the SAP transaction code for Change Material (MM). It changes an existing material master, adding views or updating data (e.g. MRP settings, prices), across the functional areas that own each view.
What else is worth knowing about MM02?
Material number. View(s) and organizational level to change. Editable fields per view.
What is the practical takeaway on MM02?
Add missing views here (e.g. extend a material to a new plant). Coordinate changes with the owning function (each view has an owner). Use change documents to audit what changed.
What tends to go wrong with MM02?
Using the wrong variant (e.g. create vs change vs display). Missing prerequisite master data or config. Not checking the resulting document/postings.