Creating a SAP Account / User Creation in SAP (SU01)
•To create an SAP user you should run transaction SU01 or Tools-> Administration->Maintain Users-> Users. Then enter a user name for the user you want to create.
•When creating a user, remember that that user only exists in that client. If you want a user to have access to another client, you must create the user in that client.
•When you create a new user, that user has various types of information associated with it.
•Entering a password.
•The first field that you edit in a new User Master Record is the password field. You must add a password for a new user. To protect against typing errors, you must enter the password twice.
•SAP user passwords have various properties. SAP passwords :
–are not case-sensitive (the R/3 System does not differentiate between upper- and lowercase letters)
–must be at least three characters long. have a maximum length of eight characters
–may contain any characters which can be input from the keyboard. This includes digits, spaces and punctuation marks
–cannot begin with a question mark or exclamation mark
–may not contain spaces within the minimum length. This is normally the first three characters
–may not begin with three identical characters
–may not be PASS or SAP*
–may not be used if its use has been forbidden
–may not start with a sequence of three characters which appears in the user name
When the user logs on for the first time, he or she must enter a new password.
When a user changes his or her password, the new password must be different to each of that user’s last five passwords.
Step 3 (Optional)
•A user group is the name of the group User Master Records to which this user is assigned.
•If you plan to divide maintenance of User Master Records among user administrators, then you must assign the user to a user group. If a user is assigned to a user group, then only an administrator who is authorized for the user group can maintain the user.
•A User Master Record that is not assigned to a user group can be altered by any user administrator.
Step 4 (Optional )
•Account Validity and Account Number
•The account valid dates are the dates during which this account is valid. If you do not enter any information in these fields your account will be valid immediately and never expire.
•Account number: Enter a freely-selectable account name or number. The user’s system usage is assigned to this account if you are using the SAP accounting system. The account name or number may be unique to each user or can be shared among groups of users.
•SAP recommends entering a user’s cost center or company code as the account number.
•If you are using the accounting system, then you should always enter an account name or number. Otherwise, the user’s usage will be assigned to a collective “No account” category by the accounting system.
Step 5 (Optional)
•A normal dialog user is used by exactly one person for all logon types.
•Dialog logons are checked for obsolete/initial passwords which must be changed.
•Multiple dialog logons are checked and logged.
•Use the user type System for dialog-free communication within one system. (for RFC or CPIC service users) or for background processing in one system.
•Dialog logon is not possible.
•A user of this type is excluded from the standard settings for password validity period. The password can only be changed by user administrators or in transaction Su01 (Goto -> Change Password)
•Use the user type Communication for dialog-free communication between systems (for RFC or CPIC service users of different applications, for example, ALE, Workflow, TMS ZBV).
•Dialog logon is not possible.
•A user of type Service is a dialog user available to a large anonymous set of users. It usually has closely-restricted authorizations.
•Service users are e.g. used for anonymous system access via an ITS service. You can change a session which began as an anonymous session with a service user into a personal session under a dialog user with an individual authentification.
•There is no check for obsolete/initial passwords at logon. Only the user administrator can change the password.
•Multiple logon is allowed.
•Reference ‘L’ A Reference user is a general impersonal user like the Service user. You cannot logon with a Reference user. The Reference user is to give Internet users identical authorizations.
•You can specify a Reference user for additional dialog user authorizations, in the Roles tab. The application generally controls the assignment of Reference users. The name of the Reference user can be assigned in variables which should begin with “$”. The assignment variable-Reference user is made in the transaction SU_REFUSERVARIABLE.
•This assignment applies to all systems in a CUM landscape. If the assigned Reference user does not exist in a CUM subsidiary system, the assignment is ignored.
•Use the user type System for dialog-free communication between systems (for RFC or CPIC service users) or for background processing in a system. Dialog logon is not possible.
A user of this type is excluded from the general password validity period settings. The password can only be changed by the user administrator in the transaction SU01 under Goto -> Change Password
Put details like name
•Communication type with which you can exchange documents and messages with a business partner.
•In the central address management you can specify a standard communication type which can be used by programs to determine the communication type for sending messages.
Step 7 (Optional )
•Name of an output device in the SAP System. The name is entered in the definition of the output device. Users in the SAP System use this name (or the long name) to select the output device.
•Maintaining the name: Enter any name you choose to identify an output device in the SAP System. If you have many printers, they should be named according to naming convention. This makes it easier to select a printer in spool administration using a generic selection.
•Processing a spool request: Enter the SAP name of the output device you want to execute your output request. Display a list of available printers and other devices with Possible entries . To set a default name, choose System -> User profile ->Own data.
•Selecting spool requests: Enter the SAP name of an output device to display the spool requests to be executed by this device. Use Possible entries to display a list of available devices.
Step 8 (Optional )
•A field can be filled with proposed values from SAP memory using a parameter ID.
•A user only has authorization for company code 001. This company code is stored in memory at the beginning of a transaction under the corresponding parameter ID. Fields that refer to the data element are automatically filled with the value 001 in all subsequent screen templates.
•A field in the screen template is only filled automatically with the value stored under the parameter ID of the data element if this was explicitly permitted in the Screen Painter.
•The SAP standard contains more than 1200 predefined single roles from all application areas.
•If you assign a predefined role to a user, he or she is automatically given the user menu required for his or her daily work and the authorizations required for it, when he or she logs on to the SAP System.
•He or she can also define his or her personal Favorites from the functions assigned to him or her. The user calls transactions, programs or internet/intranet applications from the Favorites or the job structure tree.
•Before you start to create your own roles for your staff, check whether the roles delivered by SAP can be used for the job descriptions in your company.
•The bottom row of the Maintain User screen contains fields for entering the names of profiles which can be associated with the user. We will discuss how to add user profiles in a later chapter.
•The SAP System contains predefined profiles:
–SAP_ALL: assign the profile SAP_ALL to users who are to have all R/3 authorizations including super user authorization.
–SAP_NEW: assign this profile to users who are to have access to all not yet protected components.
Step 11 (Optional)
•A User group is a logical grouping of users
•The purpose of a user groups is to :
a.Provide administrative groups for users so they can be managed in these groups.
c.Create the group “Trmin” for terminated users. Lock all users in this group.
User Creation Complete