topic Re: Runtime error MESSAGE_TYPE_X when user is deleted through SU01 in Application Development and Automation Discussions

Runtime error MESSAGE_TYPE_X when user is deleted through SU01

Former Member — Mon, 04 Jan 2016 12:22:51 GMT

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

Re: Runtime error MESSAGE_TYPE_X when user is deleted through SU01

RaymondGiuseppi — Mon, 04 Jan 2016 12:35:41 GMT

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

Re: Runtime error MESSAGE_TYPE_X when user is deleted through SU01

Former Member — Mon, 04 Jan 2016 13:27:45 GMT

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

Re: Runtime error MESSAGE_TYPE_X when user is deleted through SU01

Former Member — Mon, 04 Jan 2016 14:32:12 GMT

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.

Re: Runtime error MESSAGE_TYPE_X when user is deleted through SU01

RaymondGiuseppi — Mon, 04 Jan 2016 15:43:13 GMT

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