Lets go through the steps for Mass User creation.
(1) Step 1 – Recording the tcode execution
- In this step we need to create a script. Since the task is to do mass user creation, lets name the script as Z_MASS_USER_CREATE.
- Click on Create Icon as shown in the figure below:
- Under header data, Enter the Script Title. We have entered “Test Script for Mass User Creation”.
- Enter the component – BC-SEC-USR-ADM
- Click Save
- Click Pattern
- The system will then prompt with Create Object Directory Entry Box. Click on “Local Object”.
- Now in Insert Statement Dialog window, select UI Control for Group.
- Select TCD (Record) for Command.
- Select SU01 for Transaction. Press Enter. The Interface will get populated automatically with SU01_1.
- Click Continue check mark.
From this step onwards every step is recorded. So we need to be a little careful not to click any option which is not required.
Clicking the continue check mark takes to the User Maintenance (SU01) screen. Follow the steps for creating a user id and click Save.
- Once the user id creation process is over and we have clicked the save button, its time to end the recording. To end the recording, click the button in SU01 screen. You will be prompted with the “Recording Ended” dialog window. Click “Yes” as shown below:
- In the next screen, Click Save to save the recorded test script.
(2) Step 2 – Creating the Parameters
As already discussed during the earlier discussion on SECATT, the next step after “Recording of tcode execution” is Creating the Parameters. Here, the VALINS (Values that were entered during the recording) are converted to Parameter Values. Lets see how this is done.
- Double click the interface value SU01_1.
- After we double click the above mentioned interface, we get “Command Interface” on the right side. In the command interface, there is an option DYNPRO MODE . Expand this Dynpro Mode by clicking on the arrow on its left.
- On expanding the dynpro mode, we get various sets of screens numbered , ,  etc. Expand the 1st  set of screen.
- Double click on FIELD MODE (as shown in the figure below)
- On the right side of the screen, we get certain values for interface SU01_1. Double click on the value that was entered during user creation. For example, we had used user id as ZTEST. Double click on the value (ZTEST here).
Change ‘ZTEST’ to ZUSERID and click Back button as shown below:
(3) STEP 3 – Creating Test Configuration
- Enter Test Configuration Name and click create icon as shown below:
- Enter Description of the Test Configuration (Here we have entered description as “Test Config for Mass User Creation”. Enter Component as “BC-SEC-USR-ADM”. Click Save.
- System will prompt with “Create Object Directory Entry” dialog window. Click Local Object.
- Now select “Configuration” tab.
- In the “Test Script” text box, enter the Test Script name that we had created in the Step – 1. (We had created Test Script Z_MASS_USER_CREATE)
- Select Utilities -> Settings
- Now select eCATT tab and then External tab
- Also set the path for eCATT Objects, Variants and WebDynpro. We have set the path to Desktop as shown in the figure below:
- Click Continue check mark
- Now download variants using “Download Variants” button as shown below:
- By default it will be downloaded to Desktop as we had set the path for variant download as Desktop in our previous step.
- The system will prompt with “Download Variant Data” dialog box. Click Yes:
The variant file (VAR_ECTC_Z_MASS_USER_CREATE.TXT) gets downloaded to the desktop.
The file is in .txt format. The values present in this file should not be modified. For creating mass users, we need to update this file with the list of users which need to be created. The best way to do that is to open this file in .xls format (right click on the file and open with Microsoft excel).
- Click Variants tab and select External Variants/Path. Select the Variant file and click execute.
Make sure that the variant file is not open while execution. When system prompts to save the configuration, save it.
Mass users get created with the following log: