How to Change Material Master Data (MM02, MM03) in SAP

⚡ Smart Summary

Changing Material Master Data in SAP requires transaction MM02 for editing fields and MM03 for read-only display. This tutorial explains the difference between MM01, MM02, and MM03, then walks through five clear steps to update a Material Master record safely and verify the change.

🔑 Transaction Codes: MM01 creates, MM02 edits, MM03 displays Material Master data in read-only mode with greyed-out fields.
🗂️ View Selection: Pick only the views you need to change (for example Sales Organization Data 2) to minimize accidental edits.
🏢 Organizational Levels: Choose the correct plant, sales organization, and storage location before editing to keep changes scoped.
✅ Validation Step: Always click the Check button after edits so SAP highlights missing or inconsistent fields before saving.
💾 Save and Audit: Save the change and verify it through MM03; the change history feeds SAP audit logs for traceability.

What are MM02 and MM03 in SAP?

You may need to change certain options in the Material Master because of organizational changes or evolving business processes. Transaction MM01 cannot be used for these updates because MM01 only creates views that are not yet maintained for a material. To edit existing data you use MM02, and to view data without the ability to change it you use MM03.

In SAP, transactions that end with 01 are used for creating records, transactions ending with 02 are used for editing or changing them, and transactions ending in 03 are used for viewing records in read-only mode.

How to Change Material Master Data in SAP MM02

Follow the five steps below to update a Material Master record through transaction MM02 and verify the change.

Step 1) Open MM02 and Enter the Material Number

Enter transaction code MM02 in the command prompt.
Enter the material number whose Material Master data you want to change.

Step 2) Choose the Views and Organizational Levels

The next step is to choose the views for which data must be changed. For this example, we select Sales Organization Data 2. You can choose one or more organizational levels for the change.
Click on Organizational Levels.
Make your organizational-level selection (plant, sales organization, distribution channel as required).

Step 3) Make Changes and Run a Check

Make the desired changes in the editable fields.
Click the Check button so SAP validates the edits and flags any inconsistencies.

Step 4) Verify the Updated View

After the changes are made, verify them in the corresponding view to confirm that every field reflects the intended update.

Step 5) Save the Material Master

Click the Save button to commit the changes to the Material Master record. SAP records the change in the document history for audit purposes.

NOTE: Use transaction MM03 to display Material Master Data. In MM03 you can only display the data with no ability to change it (fields are greyed out).

FAQs

MM01 creates a new Material Master record or new views. MM02 edits existing Material Master data. MM03 displays the record in read-only mode with greyed-out fields. This 01/02/03 pattern is a common convention across many SAP master-data transactions.

MM02 does not have a built-in undo. Reversing an MM02 change means manually editing the field back to its previous value. SAP records every change in the document history, so administrators can refer to the audit log to identify the original value.

MM03 is a display-only transaction. Fields are greyed out to prevent accidental edits and enforce read-only access for users who need to view Material Master data without authorization to change it. Use MM02 instead when editing is required.

AI identifies duplicate Material Master records, predicts missing fields, recommends classification codes, and detects data anomalies. AI copilots also suggest enrichment values from supplier catalogs, reducing manual effort and improving downstream procurement, planning, and reporting accuracy.

Yes. AI models compare proposed MM02 edits against historical patterns, related materials, and master-data rules. If a change deviates significantly, the AI flags the risk before save, preventing pricing errors, incorrect units of measure, or broken downstream MRP planning.