MM17 Código T en SAP: Mass Maintenance of Material Master
⚡ Resumen inteligente
Mass creation of material master records replaces repetitive single entry with tools such as MM17, LSMW, eCATT, BDC, and BAPI. Transaction MM17 changes or extends many materials at once when the target data is identical.

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:
- Creación en masa 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.
- Cambio de masa 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 Tutorial de mantenimiento masivo
Para crear varios materiales a la vez, debe tener acceso a una función como
- herramienta eCatt
- LSMW (Banco de trabajo de migración de sistemas antiguos)
- BDC Grabaciones (comunicación de datos por lotes)
- BAPI (Business Application Programming Interface)
También puede utilizar la transacción de mantenimiento masivo MM17 para crear vistas en algunos casos. Pero debe tener en cuenta que no todos los niveles organizativos deben contener los mismos datos (MM17 requiere que todos los datos de los materiales y niveles organizativos que seleccione sean los mismos).
Mass creation is never considered to be end user responsibility. But as a module specialist you may need to work on MM17. En caso de LSMW, BDC o 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.
Puede usar MM17 para cambios masivos de datos maestros de materiales (si algo no se puede lograr con esta transacción, se puede hacer usando LSMW, BDC o 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.
| Creates new records? | Different value per record? | Who normally uses it | Mejores adecuados para | |
|---|---|---|---|---|
| MM17 | No, changes and extends only | Yes, values can be typed per row in the grid | Module specialist | Uniform field updates across a material list |
| LSMW | Sí: | Yes, read from a source file | Consultor | One time migration and repeatable loads |
| eCATT | Sí: | Yes, driven by a test data container | Consultant or tester | Loads combined with system testing |
| BDC recording | Sí: | Yes, from an internal table | ABAP developer | Screens without a standard load option |
| BAPI | Sí: | Yes, per call | ABAP developer | Interfaces and recurring automated loads |
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
Paso 1)
- Introduzca la transacción MM17
- Seleccione el tipo de datos que necesita cambiar, por ejemplo, necesitamos cambiar un campo en datos generales.
- Ejecutar.
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.
Paso 2)
- Ingresar el rango o lista de materiales para los cuales queremos cambiar los datos
- Implementación
Paso 3)
- Al hacer clic en el botón que se muestra a continuación, obtendrá el Seleccionar campos .
- Marque el campo correspondiente (estamos cambiando la unidad de medida base para nuestros dos materiales).
- Haga clic en la flecha que apunta hacia la izquierda para agregar el campo seleccionado a la lista de campos que se van a cambiar.
- Haga clic en el botón Aceptar.
Paso 4) Ahora se nos presenta la siguiente pantalla donde podemos ingresar nuestro valor a transferir. Digamos que hemos mantenido PAL – pallet como unidad de medida base para nuestros televisores de 24″ y 32″ y necesitamos cambiar eso a PCS – piezas.
- Introduzca el valor que desea copiar en el cuadro.
- Haga clic en el encabezado de la columna.
- Seleccione el botón para sobrescribir los valores antiguos con “PCS”.
- Ejecutar.
Ahora se guardan sus configuraciones y se cambian los datos maestros de materiales.
MM17 Limitations and Mejores 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 y change material master tutorials remain the correct route.




