MM02 step by step: Changing a material master
This document describes how you can use Winshuttle Studio v11 to edit a Material Master in the SAP Business Suite from data in Microsoft Excel using the SAP transaction MM02.
- Start Winshuttle Studio from the desktop shortcut or from the Windows Start menu.
- Click New.
- Click Transaction, and then click Create from Recording.
- Choose the SAP system that you want to use, enter the appropriate user data, and then click Log On to SAP.
If you do not see the SAP system that you want, click Advanced SAP Logon, click Add System, provide the system information, and click OK.
- In the Transaction code box, type MM02.
- Leave the recording mode as Standard. If you do not see Standard, click Change, click Non-Batch Input Mode Without SAP Controls, and then click OK.
Note: For most transactions, the default mode is Standard, and the Winshuttle Function Module (WFM) selects the optimum mode for the t-code that is being recorded. If the WFM is not installed, Non-Batch Input Mode Without Controls will work for most transactions. Non-Batch modes are necessary for downloading information from SAP transactions, or for Finance or HR transactions in which there are Dynamic Actions executing or user parameter values being used; otherwise, if you do not have access to Non-Batch modes, you can try recording in Batch Mode. The difference between Without SAP Controls and With SAP Controls is just a matter of what tools are on the transaction screens. For more information, see the Recording modes topic (Connect mode or Foundation mode).
- Click Start Recording.
The MM02 transaction starts.
Note: The following screens may vary according to the way your SAP system has been configured.
To make this process repeatable by Transaction, there will be a few changes to the process compared with how you would manually update a material. These differences will be identified throughout the rest of this document.
- Enter the Material Number and click Select view(s).
- If your Select view(s) page has been set up with a default set of selections, click the Deselect all button at the bottom of the page first. This will clear out any entries prior to selecting the views required for your recording.
- Select only Basic Data 1.
Note: This step in the recording differs from manual data entry and makes the selection repeatable.
- Click the green checkmark button to continue.
- Enter data into all the Basic Data 1 fields that you want to include when you upload data to SAP, and then click the Tab List drop-down button.
- Select the next tab that you want to update.
- Enter the plant number and click the green checkmark button.
- Update the fields on any additional tabs that you want to include.
- When you have made all the updates that you want, click the Save button. This will also end the recording.
After Studio finishes compiling the script, it will take you to the Map tab.
It is now time to create the mapping for this transaction. Mapping a script is just a matter of connecting SAP fields to fields in your data file. Transaction provides a Mapper to facilitate this process.
Auto Mapping will map the entire script to an Excel spreadsheet in the order that they appear in the Mapper. Because of the complexity of this transaction, we will map the fields manually instead.
The screenshot below shows the Basic View tab of the Mapper.
Each row of the Mapper displays the following:
- Mapper row number: This is just a reference number.
- Enable flag: only enabled Mapper rows will be executed by Transaction.
- Field Description: The label associated with the SAP technical field name.
- Field Name: The SAP technical field name.
- Field Type & Length: For example, String or Decimal, and the padding options.
- Mapping direction: Fixed Value, Excel to SAP, SAP to Excel (or, if mapping to Access: Access to SAP, SAP to Access).
- Value: Values assigned to the SAP field; either fixed values or mapped locations in the associated data source.
Note: The Properties pane is also displayed, but it is not shown below.
In the Data Set Preview panel, you will see a preview screen of the selected data source.
To change the data source type, click the drop-down menu under the Data Set tab and choose the data source type that you want.
The Data Set panel will change to reflect the choice. In this case, we will use Excel.
To map the script to the data source, you will drag in the direction that the data will move. For this script, you are uploading data from Excel to SAP, so you will drag from Excel to the Mapper.
- Click in column A, drag it up, and drop it onto row 2.
- Continue across the Excel preview by dragging column B up and dropping it onto row 3, column C onto row 4, and so on, until all the fields that you want have been mapped.
Add the data and run the script
- Click the Run tab.
Note: Transaction will automatically assign the Log column to the next available column after the last mapped column (in this case, column L).
- Type the data in the columns.
- To execute the upload, click the Test button, if you are a Foundation user, or click the Run button if you are not a Foundation user.
Studio prompts you to save the script and data files.
The best practice is to name the Excel spreadsheet the same name as the script unless an Excel spreadsheet will be used for multiple scripts.
After you save the script and data files, the script runs.
The yellow message bar displays a message when the run has finished.
- Check the log column. The run was successful and the messages returned from SAP were entered into the log column.