• Studio v11
  • CS01 step by step: Creating a Bill of Materials
  • FB01 step by step: Posting documents
  • FB50 step by step: Posting Journal vouchers
  • FB60 step by step: Entering invoices
  • FBS1 step by step: Posting Accrual/Deferral documents
  • ME21N step by step: Creating a purchase order
  • ME31K step by step: Creating a contract
  • MM01 step by step: Creating a material master
  • MM02 step by step: Changing a material master
  • PA40 step by step: Personnel Actions
  • VA01 step by step: Creating a sales order with reference
  • XD01 step by step: Customer Master creation
  • Enable GUI Scripting: Step by step
• Journal Entry 9.3 | 9.4
  • Cell-based
    • F-02 single company, cell-based
    • F-05 single company, cell-based
    • FB01 single company, cell-based
    • FB01 multi-company, cell-based
    • FB60 single company, cell-based
    • FB60 multi-company, cell-based
    • FB65 single company, cell-based
    • FB65 multi-company, cell-based
    • FB70 single company, cell-based
    • FB70 multi-company, cell-based
    • FB75 single company, cell-based
    • FB75 multi-company, cell-based
  • Column-based
    • F-02 single-company, column-based
    • F-05 single-company, column-based
    • FB01 single-company, column-based
    • FB01 multi-company, column-based
    • FB60 single-company, column-based
    • FB60 multi-company, column-based
    • FB65 single-company, column-based
    • FB65 multi-company, column-based
    • FB70 single-company, column-based
    • FB70 multi-company, column-based
    • FB75 single-company, column-based
    • FB75 mutli-company, column-based
• Transaction
  • CS01 step by step: Creating a Bill of Materials
  • FB50 step by step: Posting Journal vouchers
  • FBS1 step by step: Posting Accrual/Deferral documents
  • FK03 step by step: Read SAP fields into Excel
  • ME21N: Creating a purchase order
  • MM01 step by step: Creating a material master
  • MM02 step by step: Changing a material master
  • PA40 step by step: Personnel Actions
  • VA01 step by step: Creating a sales order with reference
  • XD01 step by step: Customer Master creation
  • Enable GUI Scripting: Step by step

XD01 step by step: Customer Master creation

This document describes how you can use Winshuttle Transaction in Studio v11 for customer master creation in the SAP Business Suite from data in Microsoft Excel using the SAP transaction XD01.

Steps

Record

1. Start Winshuttle Studio from the desktop shortcut or from the Windows Start menu.
2. Click New.

   

3. Click Transaction, and then click Create from Recording.

   

4. 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.

5. In the Transaction code box, type XD01.

   

6. 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).

7. Click Start Recording.

   

   The XD01 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 modifications to the process compared to how you would manually create a purchase order. These differences will be identified throughout the rest of this document.

8. Depending on your system configuration, enter data in all required fields.

   

9. Click the green check button or press Enter to continue.
10. Enter data into the fields on the next screen that will need to have data uploaded into them.
11. After you enter all of the data, click the Display next tab page button.

    

12. Continue to enter data into the appropriate fields for each tab and click the Display Next Tab Page button to move to the next tab. We show only some of the tabs here.

    

    

    

    

13. After you enter data on the last tab, click the Save button. This will end the recording and take you back to Transaction.

    

After Studio finishes compiling the script, it will take you to the Map tab.

Map

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 panel, you will see a preview screen of the selected data source type.

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 preview 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 SAP.

1. Drag column A up and drop it onto row 2.
2. Continue across the Excel preview by dragging column B up and dropping it onto row 3, column C onto row 4, and column D onto row 5, and so on until all the fields are mapped.

   

Add the data and run the script

1. 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 J).

2. Type the data in the columns.
3. 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.

   

The run is successful and the messages that are returned from SAP are entered into the log column.