XD01 step by step: Customer Master creation - Automate_Studio - Latest

XD01 step by step: Customer Master creation

This document describes how you can use Automate 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 Automate 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 Automate 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.