What is Batch-input user ?

[Former Member]

I see following user types in SAP.

A = Dialog user

D = Batch-input user

B = Background user

I know what is Dialog user, can you pelase let me know what the other user types allowed to do .

Thanks.

[Former Member]

You can find this information in the SAP help pages.

[Former Member]

Type 'D' users are an ancient and obsolete user type from the days when RFC connections used Communication type users and Batch-Data-Call processing was what background jobs were thought of being useful for as type 'D'.

However typ 'D' has been removed from the value range of the TYPE domain a long time ago and any old records in USR02 will automatically convert itself to the "new" typ 'B' System user if you save once in SU01 for that user.

Communication type users 'C' are also obsolete actually but still supported by the value range to keep urban legends alive. You should use typ 'B' users for all RFC and (periodic) background processing now. You can also use System type users for ICF services to make them safer, although the user Typ 'S' (Service) is commonly found to be understood to be intended for this.

A Service user is actually exactly the same as a System user, except that you can debug their sessions via external http-debugging.

Cheers,

Julius

[Former Member]

Thank you the information. This really helps me.

[Former Member]

Thank you the information. This really helps me.

[Former Member]

Actually Service users are not exactly as system users, since service users can logon into the system with credentials using saplogon. I´ll say service users are similar to a dialog user, but they do not follow the password rules and multiple logon is allowed.

Anyway, as response to the main question, you can get the details from SU01 just typing F1 on the user type field, you´ll get somehting like this:

Cheers,

User Type

Dialog 'A'

A normal dialog user is used by one person only for all types of
logon.

During a dialog logon, the system checks for expired and initial passwords
and provides an option to change the password.

Multiple dialog logons are checked and logged if necessary.

System 'B'

Use the system user type for internal system processes (->
background processing) or system-related processes (-> ALE, workflow, TMS,
CUA).

Dialog logon (using SAP GUI) is not possible.

A user of this type is excluded from the general settings for password
validity. Only user administrators can change the password using transaction
SU01 (Goto -> Change Password).

Multiple logons are permissible.

Communication 'C'

Use users of type Communication for dialog-free communication between
systems (-> RFC or CPIC) .

Dialog logon (using SAP GUI) is not possible.

The general settings for the validity period of a password apply to users of
this type. Users of this type can change their passwords (like dialog
users). The dialogs for changing the password must be provided by the caller
(RFC/CPIC client). You can use the RFC function module USR_USER_CHANGE_PASSWORD_RFC
or the RFC API function RfcOpenEx() to change the password.

Service 'S'

A user of the type Service is a dialog user that is available to an
anonymous, larger group of users. Generally, this type of user should only be
assigned very restricted authorizations.

For example, service users are used for anonymous system access using an ITS
service or a public Web service. Once an individual has been authenticated, a
session that started anonymously using a service user can be continued as a
personal session using a dialog user (see SUSR_INTERNET_USERSWITCH)

During logon, the system does not check for expired and initial passwords.
Only the user administrator can change the password.

Multiple logon is allowed.

Reference 'L'

Like the service user, a reference user is a general
user, not assigned to a particular person. You cannot log on using a reference
user. The reference user is only used to assign additional authorization.
Reference users are implemented to equip Internet users with identical
authorizations.

On the Roles tab, you can specify a reference user for additional
rights for dialog users. Generally, the application controls the allocation of
reference users. You can allocate the name of the reference user using
variables. The variables should begin with "$". You assign variables to
reference users in transaction SU_REFUSERVARIABLE.

This assignment applies to all systems in a CUA landscape. If the assigned
reference user does not exist in one of the CUA child systems, the assignment is
ignored.

[Former Member]

Thank you the information. This really helps me.