MM17 Tcode in SAP: Mass Maintenance of Material Master

What is Mass Maintenance in SAP MM?

Mass maintenance means applying the same master data operation to many records in one execution instead of opening each material individually. A project that loads two thousand materials during a go live, or a business decision that moves an entire product group to a new unit of measure, is impractical through MM01 and MM02 alone.

Two distinct needs sit behind the term, and they are often confused:

• Masovno stvaranje builds material master records that do not yet exist. It requires a data load tool that can drive the full creation transaction with different values per record.
• Masovna promjena updates a field on records that already exist, or extends existing materials to further organizational levels. This is what transaction MM17 performs.

The distinction matters because MM17 cannot invent a material number or populate every mandatory field of a new record. It writes one supplied value across a selected set. Genuine creation at volume therefore uses LSMW, eCATT, a BDC recording, or a BAPI call, all of which read a source file containing a different row per material.

The comparison below shows where each tool fits before the MM17 procedure is demonstrated.

SAP Vodič za masovno održavanje

Kako biste stvorili više materijala odjednom, trebali biste imati pristup funkciji kao što je

1. eCatt alat
2. LSMW (Legacy System Migration Workbench)
3. BDC (Batch Data Communication) snimke
4. BAPI (Business Application Programming Interface)

Također možete koristiti transakciju masovnog održavanja MM17 za stvaranje pogleda u nekim slučajevima. Ali morate imati na umu da ne bi sve organizacijske razine trebale sadržavati iste podatke (MM17 zahtijeva da svi podaci za materijale i organizacijske razine koje odaberete trebaju biti isti).

Mass creation is never considered to be end user responsibility. But as a module specialist you may need to work on MM17. U slučaju LSMW, BDC ili BAPI, it is considered to be developer or consultant work. So you do not have to understand in detail, you just have to know the concept, and that there is this kind of possibility for mass data maintenance.

Možete koristiti MM17 za masovnu promjenu matičnih podataka o materijalu (ako se nešto ne može postići ovom transakcijom, to se može učiniti pomoću LSMW, BDC ili BAPI).

Mass Creation Tools Compared: MM17, LSMW, eCATT, BDC and BAPI

Each tool trades setup effort against flexibility. The table summarises which one to reach for in a given situation.

BAPI is the most robust choice because it validates data through the same business logic as the transaction without depending on screen sequence. A BDC recording, by contrast, breaks whenever the underlying screen changes.

How to Use MM17 for Mass Maintenance

Korak 1)

1. Unesite transakciju MM17
2. Odaberite vrstu podataka koju trebate promijeniti, na primjer, moramo promijeniti polje u općim podacima.
3. Izvršiti.

The tables listed on this first screen correspond to the material master views. MARA holds general data, MARC holds plant data, and MVKE holds sales data, so the table chosen here decides which fields become available later.

Korak 2)

1. Unesite raspon materijala ili popis za koji želimo promijeniti podatke
2. Izvršiti

Korak 3)

1. Kada kliknete na gumb prikazan ispod – dobit ćete Odaberite polja zaslon.
2. Označite odgovarajuće polje (mijenjamo osnovnu mjernu jedinicu za naša dva materijala).
3. Pritisnite strelicu koja pokazuje lijevo kako biste odabrano polje dodali na popis polja koja treba promijeniti.
4. Pritisnite gumb U redu.

Korak 4) Sada nam se prikazuje sljedeći zaslon na kojem možemo unijeti našu vrijednost za prijenos. Recimo da smo zadržali PAL – paletu kao osnovnu mjernu jedinicu za naše televizore od 24 inča i 32 inča i to moramo promijeniti u PCS – komade.

1. Unesite vrijednost koju želite kopirati u okvir.
2. Kliknite na naslov stupca.
3. Odaberite gumb za brisanje starih vrijednosti s “PCS”.
4. Izvršiti.

Sada su vaše postavke spremljene, a vaši matični podaci o materijalu promijenjeni.

MM17 Limitations and Best Practices

MM17 writes directly to master data with no approval step, so a mistake propagates across every selected material at once. The following practices keep that risk under control.

• Test in a sandbox first. Run the identical selection and field change in a non productive client and inspect a sample of records before repeating it in production.
• Start with a narrow selection. Execute for two or three materials, verify the result in MM03, then widen the material range.
• Understand the overwrite button. Choosing to overwrite replaces existing entries, while the alternative fills only fields that are currently blank. The wrong choice silently destroys maintained values.
• Watch for dependent data. Changing the base unit of measure, as in the example above, is rejected when stock exists or open documents reference the old unit.
• Record the selection. Save the material list used, so the change can be traced or reversed if a downstream report looks wrong.
• Check the results log. MM17 reports which records were updated and which failed. A run that ends without a green message has not fully applied the change.

When a requirement genuinely needs different values per material, or fields that MM17 does not expose, escalate to LSMW or a BAPI load rather than forcing the transaction. For single record work, the copy material master i change material master tutorials remain the correct route.

Pitanja i odgovori