Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

System User lock

Former Member
0 Kudos

We have a system user set up in QA (version 4.6C) yesterday the interface programme failed to run as the user was locked, when I checked the change documents for the user, the user locked due to 'incorrect logon lock' today the user unlocked the account. Can anyone please advise as to how the account could have locked if it is not possibe to logon as a system user?

Thanks for your help

Anthea

2 REPLIES 2

Former Member
0 Kudos

> Can anyone please advise as to how the account could have locked if it is not possibe to logon as a system user?

This is an urban legend. If if were not possible to logon as them, they would not need to exist...

In this case of a password lock, the calling system has probably entered the password incorrectly into the connection data and when the interface run, the RFC call locks the SYSTEM user in the target after a number of repeated failed password-based logon attempts.

This should however not disrupt usual background processing in jobsteps, because the user ID is not locked - only the password.

So, you need to find out where the incorrect password is coming from and why it is incorrect.

Cheers,

Julius

Former Member
0 Kudos

Hi Anthea ,

SYSTEM user (user type B) is used for system dependent and system - internal operations .Features are as follows :

1) GUI log on is not possible.

2) Passwords cannot be initial passwords and there is no expiration for passwords as they are not subject to password change requirement.

3) Multiple log on is allowed and are mainly used for internal RFC , background processing , extrenal RFC

In your scenario you are saying that interface programme get failed as the user gets locked due to incorrect log on. In genaral when any external interface is connect to SAP system we connect them using system user. when you connect the external interface to SAP system using RFC you upadate system user Id password at both the sides. So when the interface tries to connect to the system it will check for the password which is updated on both sides and when the authentication gets succeeeded RFC connection takes place and the job gets run.

So when the authentication gets failed user will get locked automatically and job gets failed.That is it recommended the dialog users should not be used for background processing and RFC's.

Regards

Kanti