Short dump AC_FLUSH_CALL_INTERNAL (MESSAGE_TYPE_X using CL_GUI_SIMPLE_TREE

[Former Member]

Hi all!

I have created a Drag and Drop-Report between ALV list and a tree, using cl_gui_alv_grid and cl_gui_simple_tree.

The report works fine with SAP GUI for Java, but not for Windows. I installed the latest patch on my GUI for Windows to see if this helped, but it still dumps. I am now on GUI 710, patch level 14.

The SAP GUI for Java is version 7.10 rev 3.

It seems like the report works fine in Windows only when it builds a tree with few nodes. When the tree has many nodes ( >6000 entries in the table) the report dumps in GUI for Windows, but not in GUI for Java.

I get the following runtime error:

MESSAGE_TYPE_X

The termination occurred in the ABAP program "SAPLOLEA" in "AC_SYSTEM_FLUSH".

The termination occurred in line 29 of the source code of the (Include) program "LOLEAU02".

I also tried to turn on the automatic queue: Synchronous Processing. I then got the following runtime error:

RAISE_EXCEPTION

The termination occurred in the ABAP program "SAPLOLEA" in "AC_FLUSH_CALL_INTERNAL".

The termination occurred in line 259 of the source code of the (Include) program "LOLEAU10".

It looks like the dump occurs in the method cl_gui_simple_tree->add_nodes, where I send in the internal table with the nodes, and table structure name 'MTREESNODE', but it doesn't throw any exceptions here.

Thanks for all replies!

Best regards,

Ellen

Moved to the correct forum

Edited by: Rob Burbank on Sep 7, 2009 3:18 PM

[Sandra_Rossi]

this is how sap works, it does not check coherence at the abap side, and it's only when the true call is made at the frontend what we see the issue. The only way to find the bug is to check all values of the internal table (try to test a simple tree first, and increase complexity step after step, until you find what is incorrect). One of the errors I made in the past was the way I defined the folders, I forgot to define ISFOLDER = 'X', and that used to trigger this error.

[Former Member]

Hi!

The problem was solved with using a diferent way to put together the internal table that the tree is created from. It was very important that the internal table was sorted correctly also.

[LeonvNiekerk]

Make sure the node that it is referring to, already exists in the internal table. So the parent item line should first occur in the table, then the child can be added.:
The fields RELATKEY and RELATSHIP defined the related nodes of the node that you want to insert. This must already exist in the tree, and may therefore not occur after the insertion point in the node table. If the node with key RELAT_KEY is the parent node of the new node, it may not be a leaf. Note: The node table is processed line by line. Each line corresponds to a node that is positioned in the tree contorl. The fields RELATKEY and RELATSHP describe where a node should be inserted. They do not define a permanent relationship between nodes.