Application Development Blog Posts
Learn and share on deeper, cross technology development topics such as integration and connectivity, automation, cloud extensibility, developing at scale, and security.
Showing results for 
Search instead for 
Did you mean: 
Former Member

Someone asked me about Uflag value in table USR02 and of course I knew the most common ones but he asked me about values I had never seen like 1 - 33- 97 (so regular values +1).

In the help of the system we only can see this, it was fast and easy to understand that 96 came from 32 + 64 and so on. But I had no idea about the +1 !

User status



User not locked

32 (Hex 20)

Locked by CUA central administrator

64 (Hex 40)

Locked by administrator

128 (Hex 80)

Locked after failed logon


Locked by administrator + Locked after failed logon


Locked by CUA central administrator + Locked after failed logon


Locked by CUA central administrator + Locked after failed logon

I googled it for 30 minutes but didn't find a clear answer, so I asked my colleagues who didn't know neither.

I finally asked my boss, who worked for SAP BC Team and has a good knowledge about SAP.

Here is the explanation about the 1 value !

When SAP BC team locks the users to do their job (maintenance, upgrade or whathever), they use a program to add 1 in the Uflag. So when they have to unlock the users they know which ones they locked and which ones were already locked by admin or other reasons.

So when they have finished their job, they launch another program to do -1 to Uflag. So logically, if the job is correctly done, the results is always equal to the figures from the table above.

It can happen that the administrator does the unlock before SAP BC, so the calculation is : +64 locked by admin +1 locked by BC -64 unlocked by admin which gives 1

Another example : user locked by CUA + administrator + BC Team : 32 + 64 + 1 ==> 97

For a reason or another the -1 work is not performed so the values are addioned by 1.

This rule can be applied to all values.