, , , , ,

SAP transaction MMSC_MASS is a good tool for Mass Extending multiple storage location for multiple material masters.  This transaction is especially useful in systems that do not allow the auto creation of the storage location view of material master when a material is first moved to a new storage location.

Going to skip the conversation as to why a company would not configure the auto creation of the storage location view of the material master.  Been through this debate several times and the bottom line is that some companies do not want the auto create storage location functionality turned on.

Transaction MMSC_MASS (Mass Maintenance: Materials) is actuality transaction MM17 with the fields/tables already selected for you.    If you do not have authorization for MMSC_MASS you might try MM17.  Check out the end of this blog to see how to use MM17.

Transaction MMSC_MASS can only be used for creation not changes or deletion of data.

Warning:  As with all “MASS” data maintenance transactions please be very careful.  Take the time to triple check your data and the steps in the transaction being used.  It takes less time to triple check everything before triggering the mass update then it will to correct the data if a mass load goes awry.

Recommendation:  It is highly recommended that you take a practice run in you Test / Quality environment before executing a Mass change transaction in Production.  This recommendation holds true no matter what Mass change transaction you are running.  Once you run the changes in Test / Quality have someone other than you validate that the changes are correct.

I have run more mass updates than I can count and I still execute the changes first in the Test/Quality environment.  Along with this I also do a test run in production of only a few materials/records.  If all goes well in Quality and test production run I run all the records.

One more recommendation run your mass change transactions during off peak hours especially if you are changing several thousand records.  This is as much about ensuring the records you are changing will not be locked as it is about system performance.

As I have mentioned in the past my goal is that any knowledgeable SAP person can successfully use the following information, however this is not a step by step instruction manual and does require a good understanding of SAP and SAP Material Masters.

Mass Extension of Storage Locations for a Multiple Material

  1. Transaction MMSC_MASS (Mass Maintenance: Materials (Industry))

On the following screen it is assumed that you know how to enter multiple entries for the material, plant and storage location fields if you do not you probably shouldn’t be using this transaction.

Note:  Small warning pop up boxes will appear when using MMSC_MASS &/or MM17.  Feel free to read them and then hit enter to go past the pop ups.  You can select the option on pop up boxes to not display them again.

Enter Selection Criteria

  • Enter Material Numbers (To be created – Either Range or List)
  • Enter Plants (To be created – Can enter multiple plants but recommend doing one plant at a time)
  • Enter Storage Location(s) (To be created).
  • Enter Reference Material (Optional but recommend)
  • Enter Reference Plant (Optional but recommended)
  • Enter Storage Location (Optional but recommended)

Blog 11 - Pic 1

Select: Enter new field values

Next step is to select the storage location related fields.

Menu: Mass Maintenance > Enter new Field Values

  • A pop up box will appear

Blog 11 - Pic 2

Enter new field values – Pop Up box

If you are not using a reference material you will want to enter your values in the appropriate fields.  I this example we are using reference material so we will leave the fields blank.

  • Hit Transfer Icon
  • Execute Transaction

Blog 11 - Pic 3

Depending on number of records being created you may receive a pop up asking if you want to display all records or change in background.  You can execute 1500 records in foreground with little performance problems.  Although it will take several minutes to complete the updates.

As a note you can also select the “fields” to be updated once the transaction has been executed (next step) but if running in background it is best to select them now.

Screen: Mass Maintenance: Material (Industry)

  • Verify data is correct
  • Post / Save changes – A stop light report will appear

Blog 11 - Pic 4

Warning:  The data can also be changed in mass or individually from this screen.  Only experts on MM17 should attempt this.  This example deals with extending material master storage locations views, which if done properly is a straight forward process.  And is why it is highly recommend that you use a reference material or entering the data in the “Enter new field values” pop up previously discussed.

Screen: Messages from the Updated Task (stop light report)

Report will show the material number with a brief message.  Green stop lights are good to go.  Red mean there was an issue that needs further investigation, see blow for more details on red lights.

Blog 11 - Pic 5

Green arrow out of transaction.  All materials with green lights have been extended.

RED Lights

If you receive a red light select the line and hit the details Icon.

Blog 11 - Pic 6

In this example the issue is that the material was locked by a user.

Blog 11 - Pic 7

  1. Transaction MM17: Using MM17 to mass extend material master storage location views.

As previously mentioned if you do not have access to MMSC_MASS you might have access to MM17.  The primary difference between the two is that MMSC_MASS brings you right to the selection screen for mass extending material masters.  Whereas with MM17 we have to work our way to the initial selection screen.

MM17 allows you to make mass changes to any and all material masters.  If you are not familiar with this MM17 be very careful when using it.  Please practice in Test/Quality environments before using in production.

Screen: Mass Maintenance: Material (Industry)

  • Select tables tab
  • Select table MARD (Storage Location Data for Material)
  • Hit Execute icon

Blog 11 - Pic 8

  • ON “Data Records to Be Changed” tab – select “Do Not Change Existing Data”

Blog 11 - Pic 9

  • Then select “Data Records to Be Created” tab – this is where MMSC_MASS starts. Note the “Data Records to Be Changed” tab should have red “X”.

Blog 11 - Pic 10

  • Return to step one to continue.

Big Warning:  MM17 and MMSC_MASS are mass change programs this means that aside from helping you make quick changes to a lot of records they can also help you quickly screw up a large number of master data all at once.  If you are not familiar with SAP mass change transactions we recommend you find someone in your company that is familiar with MM17 or other mass change transactions.

In hopes of driving this point home, no matter what your level of expertise please run your mass update in you Test / Quality environments before executing in Production.

If you have question on this or any other PortSAP Consulting blog please feel free to contact us at Blog@PortSAP.com.  Or if you are looking for Top Quality SAP Consultants please feel free to contact us.

The author, Ray Hornbrook, has over 18 years of SAP functional and technical experience.  Ray started his career in SAP as a Subject Matter Expert (SME) for a SAP implementation in 1998 and is now a senior level SAP Consultant.  Since Ray has worked both sides of SAP, business end user and IT professional, he is able to communicate effectively with both IT and Business team members.  Having a background as an SAP business end user has helped Ray greatly in his consulting career to better communicate with the business members of the team.  As well as helping bridge gaps in communication between the IT and Business team members.

To find out more about Ray Hornbrook please check out his LinkedIn profile by clicking HERE.

End of document – www.portsap.com

Neither PortSAP Consulting nor the author of this Blog is associated with SAP AG or with any of its subsidiary or alliance company. Trademarks used in our website are registered trademarks of respective companies and neither PortSAP Consulting nor the author of this Blog is associated affiliated with these companies.