MESSAGE_TYPE_X

[former_member747409]

MESSAGE TYPE X

[Sriram2009]

Hi Sunil ji,

Share the dump details and at what steps are you getting this dump?

Regards

SS

[Sandra_Rossi]

You need to things:

• Learn to read and interpret the contents of a short dump
• Read and understand what means MESSAGE ... TYPE 'X'

[former_member747409]

hi all,

Good Day....

thanks for the response...

while display/edit/delete : specific user id in SU01....leads to runtime error: MESSAGE_TYPE_X..

[former_member747409]

Category ABAP Programming Error

Runtime Errors MESSAGE_TYPE_X

ABAP Program SAPLSZA0

Application Component BC-SRV-ADR

Date and Time 08.08.2023 09:50:32

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

|Short Text |

| The current application has triggered a termination with a short dump. |

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

|What happened? |

| The current application program has detected a situation that should |

| not occur. A termination with short dump has therefore been triggered |

| by the key word MESSAGE (type X). |

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

|What can you do? |

| Note down which actions and inputs caused the error. |

| |

| |

| To process the problem further, contact you SAP system |

| administrator. |

| |

| Using Transaction ST22 for ABAP Dump Analysis, you can look |

| at and manage termination messages, and you can also |

| keep them for a long time. |

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

|Error analysis |

| Short text of the error message: |

| Internal error - index cannot be determined for address 37529 |

| Long text of the error message: |

| Technical information about the message: |

| Message class....... AM |

| Number.............. 889 |

| Variable 1.......... 37529 |

| Variable 2.......... |

| Variable 3.......... |

| Variable 4.......... " " |

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

|How to correct the error |

| Probably the only way to eliminate the error is to correct the program. |

| - |

| If the error occurs in a non-modified SAP program, you might be able to |

| find a solution in the SAP Notes system. If you have access to the SAP |

| Notes system, check there first using the following keywords: |

| |

| "MESSAGE_TYPE_X" |

| "SAPLSZA0" or LSZA0U80 |

| "

|

[mate_csak]

Hello,

AM889 usually means that the record from ADRC/ADRV is missing. As you get the dump in SU01 this is most likely related to the USCOMPANY record. In the dump variable 1 shows the address number from ADCP for which there is no ADRC/ADRV entry.

Best regards,

Mate

[Sriram2009]

Hi Sunil Ji.

It is happening in all the client machines or only one system? Could you share the SAPGUI and patch level? if it is low apply the latest patch and try the same

Regards

SS

[JoeyLi]

Hi,

Run Z_OSSNOTE_436119 and check if there is any inconsistencies.

Or check table ADCP to see if there is any blank address.

Best Regards,