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 Errors MESSAGE_TYPE_X AC_SYSTEM_FLUSH in REUSE_ALV_GRID_DISPLAY

Former Member
0 Likes
1,941

All,

Knowledge sharing purpose

ABAP dump in REUSE_ALV_GRID_DISPLAY

Category               ABAP Programming Error
Runtime Errors         MESSAGE_TYPE_X
ABAP Program           SAPLOLEA
Application Component  BC-FES-OAC
Date and Time          25.04.2014 04:49:35

Short text
     The current application triggered a termination with a short dump.

What happened?
     The current application program detected a situation which really
     should not occur. Therefore, a termination with a short dump was
     triggered on purpose 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

Long text of error message:

Diagnosis

     An error occurred when the system tried to process the commands

     from the Automation Queue on the presentation server.

     There are several possible reasons for this:

     - The installation of the SAP GUI on the presentation server is

     faulty or obsolete.

     - There is an error in the application program

     - There is an error in the SAPGUI or an integrated control

Procedure

     1. Make sure that you have imported the appropriate Support

     Package, the current kernel, and GUI patch for the release of your

     system

     2. Check whether the error occurs locally on one or a few PCs, or

     generally on all PCs. Note whether the error only occurs for some

     users, for example because of a specific Customizing setting.

     If it only occurs locally, this suggests an installation problem

     with the PC. Check the installation; if necessary, reinstall the

     software. In the dump, search for the SY-MSGLI field, since it may

     point to the cause of the error.

     3. Activate the Automation Trace (in accordance with SAP Note

     158985).

     4.Start the transaction and continue until the screen immediately

     before the dump.

     5. From the System -> Utilities menu, choose Autom. Queue,

     Synchronous Processing.

     The status bar of the GUI displays the text:

Root Cause:

We found that we user was using select option of mat. number it was around 2700 and results in above dump.

We checked for 2000 matnr it worked as all selection screen matnr was part of TOP-OF-PAGE display of ALV report.

ALV top of page do have limiation to display records not obivoius 2500 as it gave dump.

So we found that ALV top of page window do have limiation to show records around 2000 max, else above dump will result.

hope this sharing might help someone.

All,

Knowledge sharing purpose

ABAP dump in REUSE_ALV_GRID_DISPLAY

Category               ABAP Programming Error
Runtime Errors         MESSAGE_TYPE_X
ABAP Program           SAPLOLEA
Application Component  BC-FES-OAC
Date and Time          25.04.2014 04:49:35

Short text
     The current application triggered a termination with a short dump.

What happened?
     The current application program detected a situation which really
     should not occur. Therefore, a termination with a short dump was
     triggered on purpose 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

Long text of error message:

Diagnosis

     An error occurred when the system tried to process the commands

     from the Automation Queue on the presentation server.

     There are several possible reasons for this:

     - The installation of the SAP GUI on the presentation server is

     faulty or obsolete.

     - There is an error in the application program

     - There is an error in the SAPGUI or an integrated control

Procedure

     1. Make sure that you have imported the appropriate Support

     Package, the current kernel, and GUI patch for the release of your

     system

     2. Check whether the error occurs locally on one or a few PCs, or

     generally on all PCs. Note whether the error only occurs for some

     users, for example because of a specific Customizing setting.

     If it only occurs locally, this suggests an installation problem

     with the PC. Check the installation; if necessary, reinstall the

     software. In the dump, search for the SY-MSGLI field, since it may

     point to the cause of the error.

     3. Activate the Automation Trace (in accordance with SAP Note

     158985).

     4.Start the transaction and continue until the screen immediately

     before the dump.

     5. From the System -> Utilities menu, choose Autom. Queue,

     Synchronous Processing.

     The status bar of the GUI displays the text:

Root Cause:

We found that we user was using select option of mat. number it was around 2700 and results in above dump.

We checked for 2000 matnr it worked as all selection screen matnr was part of TOP-OF-PAGE display of ALV report.

ALV top of page do have limiation to display records not obivoius 2500 as it gave dump.

So we found that ALV top of page window do have limiation to show records around 2000 max, else above dump will result.

hope this sharing might help someone.

1 REPLY 1
Read only

Former Member
0 Likes
1,019

This message was moderated.