• 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 for customer master creation in the SAP Business Suite from data in Microsoft Excel using the SAP transaction XD01.

Steps

Record

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

   

3. Enter transaction code XD01 in the Transaction Code box, and then click Go.

   

   An SAP Log On screen appears.

4. Click the SAP system that you want to use, and then click OK.
5. Enter the appropriate User Data in the SAP Logon window, and then click the OK button.

   

   If you do not see the SAP system that you want, click the System button and choose a different system.

6. For the recording mode, choose Batch Input Mode.

   

   Note: 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 Central mode).

7. Enter any additional properties in the appropriate fields.
8. To prevent people from editing the script, check the Lock TRANSACTION script box. This will password-­protect the script, preventing anyone from changing it.
9. Click Next.

   You will now be launched into the XD01 transaction.

   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.

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

    

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

    

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

    

    

    

    

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

    

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 and in order. Because of the complexity of this transaction, we will choose the Create Mapping option instead.

1. Click the Create Mapping link on the Map pane.

   

2. The screenshot below shows the Expert 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.
   • Screen / Screen Number: Technical screen information from the recorded transaction.
   • Field Description: The label associated with the SAP technical field name.
   • Field Name: The SAP technical field name.
   • Mapping Type: 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 values to or from the assigned data source.
   • Notes: Free­format notes to provide useful information to runners of the Transaction script.

   

3. In the Data Source Preview section, you will see a preview screen of the selected data source.

   To change the Data Source, click the Change Source Type link at the top of the Expert Tab.

   This displays a drop-down box to switch to Microsoft Access.

   

   The Preview section will also change to reflect the choice.

   In this case, we will use Excel.

4. It is now time to begin the mapping process. It is easiest to map from the Basic tab (as shown below). Click the Basic tab.

   

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

   Drag column A 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 column D onto row 5, and so on until all the fields are mapped.

   

6. The next step is to save the script file (.TxR) and the Excel preview file (.xlsx). Click the Back arrow button at the top on the File menu.

   

   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.

   Note: If you want to use an existing Excel file that already has the data set up, you can skip saving the preview file and save the script file by clicking the Save button on the File menu.

7. Transaction prompts you to save the Excel preview file.

   

8. Click Yes, and then enter the Excel file name.
9. Transaction prompts you to save the script.

   

10. Click Yes, and then enter the script’s name.

Add the data

Transaction loads the Run pane.

If necessary, you can navigate back to the Mapper by clicking the Update Mapping link on the Map pane.

1. Click the Excel icon to the right of the Select Data File box. This will open the mapped Excel file that is listed in the Selected Data File box.

   

   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, and then save the Excel file.

   After you enter the data into the Excel spreadsheet, you can run the script.

Run

Back at the Transaction Run pane, you can specify a start and end row, specify the Excel sheet that contains the data, and change the Log column.

1. To execute the upload, click the Test button, if you are a Central user, or click the Run button if you are not a Central user.
2. In the SAP Logon window, if necessary, click the System button to select the appropriate SAP system.
3. Enter the appropriate user data, and then click OK.

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