1. Article – Creating mass users using eCATT scripts
Applies to:
SAP All Versions
Summary
This knowledge base article will provide you the steps to create mass users using eCATT scripts.
Author(s): Raghu Boddu
Created on: 10 July 2011
Author Bio
Raghu has excellent command over SAP R/3, BI, HR, and GRC. He is good known to the community for
easy to understand articles. He has authored 30+ articles for Microsoft knowledgebase and also an xMVP
in Windows shell area (2005-2008). He also bagged the SAP SDN Community Contributor award for 2008.
His exclusive documents, FAQs, and recommendation papers are available in his blog.

2. Table of Contents
Introduction............................................................................................................................................ 3
Procedure.............................................................................................................................................. 3
Phase – I – Recording the user creation:.............................................................................................. 3
Phase – II – Creating the Parameters:.................................................................................................. 5
Phase III – Creating Test Configuration:............................................................................................... 7
Phase – IV – Updating and Uploading the Variant file:......................................................................... 8
Additional References ......................................................................................................................... 10

3. Introduction
During the implementation or system migrations it might be required to create mass number of users in the
system. The traditional SU01 process may require more number of man hours, if the user count is too high. This
article will explain you the process of using eCATT script to create mass users, following which you can create
mass number of users in minutes.
Procedure
Goto SECATT transaction code and execute the entire process in 4 different phases as shown below:
Phase – I – Recording the user creation:
1. Enter Test Script name (recommended to start with Z to easily identified that it is a user defined
script)
2. Click Create icon
3. The personal Responsible will be back filled automatically and is normally the user who is creating
the script.
4. Enter the Script Title
5. Select the component (even though no validation is done, it is recommended to select appropriate
component)
6. Click Save
7. Click Pattern button

4. 8. When prompted with the Create Object Directory entry dialog box, select Local object.
9. Select UI Control for Group
10. Select TCD (Record) for Command
11. Enter SU01 as Transaction and press Enter. The Interface will be displayed automatically as
SU01_1
12. Click Continue check mark.
From this step, ensure that you don’t click any options that are not required, since every click or entry is
recorded. Unnecessary clicks/entries may show you more Fields.
Upon clicking the continue check mark, you will see the User Maintenance (SU01) screen. Follow the
steps as you create a user ID and click Save.
13. To end the recording, click the button in SU01 screen and click Yes when prompted with
the below screen:
14. Click Save to save the recorded test script.

5. Phase – II – Creating the Parameters:
Once the user creation is recorded, the VALINs (Values that were entered during the recording) should
be changed to parameter values. The below process will explain you the steps to create the
parameters:
1. Double-click the interface(SU01_1)
2. Expand DYNPRO mode
3. Expand 1st set of screen
4. Double-click on Field mode
5. Double-click on the value that was entered (in this example test001)
You may need to double-click until you see blank area with the VALIN as below:
6. Change the VALIN name with a parameter name (to ZUSERNAME as shown in the example below)
7. Click the Back button.

6. 8. Select Import when prompted with the Parameter Maintenance screen
9. Click Yes.
10. Repeat the same steps for the other values that are entered during recording.
NOTE: While recording the script, I’ve entered Username, last name, User group,
Initial password, Repeat Initial password, and a Role. Hence, I have the below 6
parameters.

7. 11. Once you are sure that all the parameters are created, click Save button.
Phase III – Creating Test Configuration:
1. Enter the test configuration name.
2. Click Create icon
3. Enter a description for the test configuration
4. Select the component
5. Click Save
When prompted to Select the package, use Local object as did in step 8 for test script creation.
6. Select Configuration tab.
7. Enter the test script name that was created in the Phase - I
8. Select Utilities, Settings

8. 9. Select eCATT tab, and External Tab
10. Change the path for eCATT Objects, Variants, and WebDynpro to Desktop.
11. Download Variants using the “Variant download” button
NOTE: Select Yes for any prompts.
Phase – IV – Updating and Uploading the Variant file:
The variant file (VAR_ECTC_Z_USER_CREATE as per this example) will be saved on the Desktop. To
modify the variant file, perform the following:
1. Open MS Excel
2. Click File Open, select the Variant file.
3. Click Next, Next, Finish in the Text Import Wizard.
4. The file should look like as follows:
Keep the highlighted area intact, which means you should not modify any of these
values. You can add your own values from Row 4.

9. In the below example, I’ve updated the spreadsheet with 10 users information.
Save the file in the same format. (Since Excel file can’t be read by the script).
5. Click Variants tab.
6. Select the Variant file as shown below.
7. Click Execute
Save the configuration, when prompted.
Once the script is successful, you can see the log as below:

10. Additional References
NA

11. Community Disclaimer
Important note: sapsecurityexpert.com grants free access to the content posted. However, if you are redistributing, we
recommend not removing the author names. Statements and opinions expressed in articles, reviews and other materials
herein are those of the authors.
While every care has been taken in the compilation of this information and every attempt made to present up-to-date
and accurate information, we cannot guarantee that inaccuracies will not occur.
sapsecurityexpert.com will not be held responsible for any claim, loss, damage or inconvenience caused as a result of any
information within these pages or any information accessed through this site. No responsibility is assumed by
sapsecurityexpert.com for the contents of these pages.
All the images (SAP screens and descriptive images) are copyrighted by SAP AG, and the other images are copyrighted by
the respective companies. sapsecurityexpert.com thanks them for allowing third party web sites to include their respective
copyright images.
For completed Disclaimer, refer the Disclaimer page @ www.sapsecurityexpert.com
sapsecurityexpert.com support “Go Green” and encourage the readers to read this document only online. Print access
has been revoked on this document.