Skip to content
Blog
Benedikt Weiss13. June 2023

Material Master creation in SAP ERP

Home / Blog / Material Master creation in SAP ERP

Key takeaways

Multiple creation options in SAP ERP: SAP offers six main methods to create or update material master data, ranging from manual entry (MM01) to automated interfaces and third-party MDM solutions.

MM01 for standard manual processing: MM01 (and MM02/MM03) is the standard transaction for creating, changing, or extending materials at the plant level and can be executed directly by business end users.

MM17 and MASS for bulk updates: MM17 and MASS enable mass maintenance of material data, including file uploads via structured templates. These require elevated business user permissions and are suited for controlled bulk changes.

LSMW and BAPI for technical data loads: LSMW and BAPI methods support structured bulk creation and integration scenarios. They typically require IT resources (developers and functional specialists) and are commonly used for migrations or system integrations.

Integration and MDM for scalable governance: Interfaces such as the SPARETECH API and third-party MDM solutions (including SAP MDG) enable governed, large-scale material master management and synchronization, but require dedicated implementation projects and IT involvement.

Material Master creation in SAP ERP

There are 6 methods / transaction codes for material master creation in SAP ERP. These are listed and described in the following table.

Method / Transaction code Description What How Ability to implement Existing resource
MM01 Material Master Transaction (MM01/MM02/MM03): This is the standard transaction in SAP to create, change, or display material master data. Creation/Change/plant extension   Can be done by business users (end users)  
MM17 (MASS identical with MM17, but also used for other master data objects) Both MASS and MM17 are transactions used for mass changes to material master data in SAP.

Note that in both MASS and MM17 you can also use the "Import Data" option to upload data from an external file instead of entering each material manually. The data in the file must be in a specific format and follow the field structure of the material master.
Mass maintenance Go to transaction MM17.

1. Select the appropriate table that needs to be updated.

2. Specify the fields to be imported, their order and the values to be assigned to specific fields.

3. Upload the file via "Import data from file".

4. Review the data: Once the file has been uploaded, check the data to ensure that it has been imported correctly.

5. Activate the materials: if the data looks correct, you can activate the materials.
Business users (not end users) need additional permissions to execute this transaction code. https://www.guru99.com/mass-creation-of-material-master.html
LSMW LSMW (Legacy System Migration Workbench): LSMW can be used to create, change or update material master data in SAP. Usually used for bulk data upload during data migration. Creation/Change/plant extension The specific details of the recording and mapping process may vary depending on your particular requirements and system configuration. IT resource is required (developer / consultant) https://blogs.sap.com/2012/12/27/lsmw-material-master-by-bapi-method-part-1/

https://blogs.sap.com/2012/12/27/lsmw-material-master-by-bapi-method-part-2/
BAPI BAPI (Business Application Programming Interface): BAPI is a programming interface that allows external applications to interact with SAP. Material master data can be created or updated via BAPIs. Creation/Change/plant extension Program development with UI IT resources are required (developer + functional specialist)  
SPT API Interface Creation of materials in SPARETECH and synchronization with SAP ERP via SPARETECH API Creation/Change/plant extension Integration with SPARETECH via SPARETECH API for material events IT resources are required (developer + functional specialist)  
MDM Solutions Use of various third-party solutions for master data management Creation/Change/plant extension The steps will vary based on the MDM solution. Note: SAP MDG provide the functionality of Product data upload. Use the templates provided by SAP to upload creations/changes to SAP through “Master data Governance Consolidation” app. (Fiori App ID F1047) An implementation project is required  
 

FAQs

Why does technical completeness in SAP MM01 not guarantee operational readiness of a material?

Because a material can be technically created in SAP while still lacking the semantic, sourcing, and governance attributes required for reliable procurement and cross-plant transparency.

  • Define a minimum viable MRO dataset (e.g., manufacturer part number, standardized description, criticality, sourcing status, lifecycle state) before release to purchasing.
  • Implement a two-step release process: technical creation (MM01) followed by procurement validation and data quality approval.
  • Use controlled value lists for fields like material group, valuation class, and MRP type to prevent inconsistent downstream planning logic.
  • Measure “first-time-right” material creation rate and target >95% to reduce correction cycles and emergency buys.

For a broader perspective on why structured MRO data is foundational to strategic advantage, explore why MRO could be manufacturing’s next strategic win.

When should companies avoid mass uploads (MM17/LSMW) despite their efficiency?

When data quality rules, duplicate logic, or governance workflows are not yet standardized, you scale errors across the enterprise.

  • Run a duplicate simulation before activation using the manufacturer part number + normalized description as matching logic.
  • Enforce pre-upload validation rules (e.g., mandatory fields, naming conventions, unit consistency).
  • Pilot uploads in a single plant and compare inventory duplication rate before scaling globally.
  • Track post-upload correction effort; if >10% of materials require manual cleanup, governance maturity is insufficient.

How does decentralized plant extension in SAP increase hidden inventory risk?

Plant-level extensions without cross-site visibility often create parallel stock positions for identical parts.

  • Require a global availability check before extending materials to a new plant.
  • Implement shared stock transparency dashboards across plants to identify redistribution potential.
  • Standardize manufacturer and supplier identifiers across all sites to prevent fragmented records.
  • Quantify inventory overlap; organizations typically uncover 10–25% redundant stock value in multi-site environments.

For insight into replacing high inventories with transparency-driven availability, see our article about spare parts on demand.

 

What governance risks arise when BAPI or API-based integrations bypass structured workflows?

Automated creation without embedded validation logic can introduce compliant-looking but strategically misaligned materials at scale.

  • Introduce API-level validation rules (duplicate detection, lifecycle checks, sourcing completeness).
  • Log every automated material event with approval traceability for audit readiness.
  • Separate technical interface ownership (IT) from data ownership (maintenance/procurement governance board).
  • Monitor automated vs. manual creation ratios and associated correction rates.

How can a global spare parts search reduce unnecessary material creation in SAP?

By enabling cross-plant semantic search before MM01 execution, organizations prevent duplicate records and reduce working capital.

  • Integrate search capability directly into the material request workflow before creation.
  • Use the manufacturer part number and AI-based similarity logic to flag near-duplicates.
  • Block creation if a functionally identical part exists unless a documented exception is approved.
  • Track avoided creations; mature organizations reduce new material growth by 15–30% annually.

Explore SPARETECH’s platform capabilities.

Why is material master creation inseparable from lifecycle and obsolescence management?

Because every new material introduces long-term risk if obsolescence, substitution strategy, and sourcing resilience are not defined upfront.

  • Assign lifecycle status at creation (active, phase-out, strategic spare, consumable).
  • Link materials to approved substitutes during initial data entry.
  • Define review intervals for low-usage materials to prevent “sleeping inventory.”
  • Calculate obsolescence exposure as % of inventory value; best-in-class organizations reduce it by >20% through proactive lifecycle governance.

Explore our 5-step guide on structured obsolescence management.

About the AuthorBenedikt Weiss, Solution Engineer at SPARETECH, works at the intersection of sales, product, customer success, and marketing, translating complex enterprise requirements into scalable SaaS solutions for digital spare parts management in manufacturing.
Benedikt Weiss
Benedikt Weiss Solution Engineer

Benedikt Weiss, Solution Engineer at SPARETECH, works at the intersection of sales, product, customer success, and marketing, translating complex enterprise requirements into scalable SaaS solutions for digital spare parts management in manufacturing.

Expert tip: Restrict material creation channels and enforce one governed entry point

Multiple technical options are not a strategy; uncontrolled entry points create duplicates, data gaps, and inventory distortion.

  • Define one primary creation path (e.g., MDG workflow or governed API), and decommission uncontrolled alternatives.
  • Separate clearly: single creation (MM01) vs mass maintenance (MM17/MASS) vs integration-based creation (BAPI/API).
  • Remove end-user creation rights where possible; use request-and-approve workflows.
  • Make manufacturer + MPN + lifecycle status mandatory at creation for MRO materials.
  • Embed an automatic duplicate check before material number assignment.
  • Log and monitor: materials created per month, % without OEM reference, % corrected post-creation.
Material creation governance directly determines duplicate rate, stock fragmentation, and downstream downtime risk.

More contributions