Strange values for field USR02-UFLAG
Hello folks,
You may observe strange values for field UFLAG within table USR02, this is a quite recurrent problem…
Situations like this one are most likely caused by direct access to the table with database tools, improper handling of database entries, for example: through custom programs (that might set values to this field directly in database level); it’s also possible that the values have been set in debugging mode and were not adjusted afterwards by the author of this modification.
To address this situation and advice on how to identify the root cause of this issue, I have release an article that is availble in the below link:
1887820 – Incorrect User Lock Status (UFLAG) in table USR02
It’s important to say that such inconsistencies may cause errors during the execution of tasks that are related to the user master records, such as SUIM reports… a good example of this is the occurrence of short dumps like the following, caused because there was some entries in the table with value larger than the expected (max. is 255):
Feel free to share your thoughts on that matter.
Hope this helps you!
Felipe Fonseca
Hi,
maybe you want to provide feedback on this blog then:
http://scn.sap.com/community/security/blog/2013/04/04/uflag-values-1--65--97
BTW As this regularly creates big messes (particularly updating single fields of USR02!) I offer a freeware tool which uses BAPIs to lock and unlock users and remember which ones you changed and protect certains admins from locking themselves -> http://xiting.ch/en/produkte_user_locking_tool.php
Cheers Otto
Hi Otto, great to know that you've developed a tool for this! 😀
Warm regards, Felipe.
BTW: I wrote telling about my KBA 1887820 in that blog back in August, 10th. 😉
I didn't realize that, my apologies 😉