Application Development and Automation 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: 
Read only

Runtime error MESSAGE_TYPE_X when user is deleted through SU01

Former Member
0 Likes
3,110

Dear all,

I'm trying to delete a user id in SU01 but it is throwing the dump error "MESSAGE_TYPE_X".

Category                           :   ABAP Programming Error
Runtime Errors                 :   MESSAGE_TYPE_X
ABAP Program                 :   CL_ADDR_PERSISTENCY_SZA0======CP
Application Component    :   BC-SRV-ADR
Date and Time                  :   01.4.2016 08:51:09
----------------------------------------------------------------------------------------------------

Please help me how to resolve this issue.  I have attached the Shot dump (ST22) details.

Your Help is highly appreciated.

Thanks in Advance

Dear all,

I'm trying to delete a user id in SU01 but it is throwing the dump error "MESSAGE_TYPE_X".

Category                           :   ABAP Programming Error
Runtime Errors                 :   MESSAGE_TYPE_X
ABAP Program                 :   CL_ADDR_PERSISTENCY_SZA0======CP
Application Component    :   BC-SRV-ADR
Date and Time                  :   01.4.2016 08:51:09
----------------------------------------------------------------------------------------------------

Please help me how to resolve this issue.  I have attached the Shot dump (ST22) details.

Your Help is highly appreciated.

Thanks in Advance

4 REPLIES 4
Read only

RaymondGiuseppi
Active Contributor
0 Likes
1,771

Did you check if user has an infotype 0105, in this case, look for OSS notes.

(Error may be triggered when two users are deleted without restart of the transaction)

Regards,

Raymond

Read only

0 Likes
1,771


Hi Raymond,

Users has infotype 0105 Only. But i didn't find any suitable OSS notes to correct this issue.  There is one OSS note 2034113 i have found but the issue is not resolved.

Thanks.

Read only

0 Likes
1,771

Consider raising an incident to OSS (They already corrected such problem twice ( 2034113 and 1974264, never two without three?)

Hint: If database was corrupted, you should look at correction reports of 436119 - Correction report for communication data inconsistencies.

Regards,

Raymond

Read only

Former Member
0 Likes
1,771

Hi,

It could be due to inconsistency in the Address Number across the tables ADRVP and USR21. You should check the tables for the PERSON_NUMBER (2586509) from the dump.

Thanks,

Shashank Sahay