HOW TO SAP

SAP SECURITY - MASS CHANGE USER LICENSE VIA SU10

SU10 > Authorization Data > User > Multiple Selection
Choose copy from txt file (if you have it in txt format) or clip board (if you click copy paste)
Click Copy and it will bring you back to previous screen
Click Execute
Select All user
Click Transfer
You will get back to SU10 main screen again
Click Change
License data Tab > Select your desired user license from drop down list
REMEMBER TO CHECK "CHANGE"
Now Save and continue
Once finish, log will be displayed for your reference

December 15, 2017 portal, user,

Schedule USER, ROLE, PROFILE SYNCHRONIZATION. This job is used for Batch Risk Analysis job later for reporting
GRC > CONFIGURATION > SCHEDULE JOB > Check only the 3 below > Then click schedule button at the bottom
Give a Job name > You may specify any options you like > Click Schedule. In our case, it will run weekly starting from 6th Oct 2011
Now schedule a new job > Select the 4 check box below > Click Schedule at the bottom
Same as before, just specify a job name and any option you like. Now click schedule again.
To check if the job you schedule is ready or running, just click "SEARCH"
Then enter the search criteria and result will show as below:

To extract user's email, you may search from table USR21 and ADR6

Alternatively, you may replace Table ADR6 with PA0105 but this table only exist in HR system.

SCUM SETTINGS - LOGON DATA TAB has the following settings as below:

Global	You can only maintain the data in the central system. The data is then automatically distributed to the child systems. These fields do not accept input in the child systems, but can only be displayed. All other fields that are not set to “global” accept input both in the central and in the child systems and are differentiated only by a different distribution after you have saved.
Proposal	You maintain a default value in the central system that is automatically distributed to the child systems when a user is created. After the distribution, the data is only maintained locally, and is not distributed again, if you change it in the central or child system.
RetVal	You can maintain data both centrally and locally. After every local change to the data, the change is redistributed to the central system and distributed from there to the other child systems.
Local	You can only maintain the data in the child system. Changes are not distributed to other systems.
Everywhere	You can maintain data both centrally and locally. However, only changes made in the central system are distributed to other systems, local changes in the child systems are not distributed.