CL_GUI_ALV_TREE =============== CP/NODE_NOT_FOUND in Z program

[Former Member]

heloo guys,

I have the following system: Linux SLES 10 (x86_64) / Oracle 10.2.0.4.0 / SAP ECC 6.0 Kernel Patch 221 (SAP_APPL 600 Patch: SAPKH60014).

In st22 i have the following error "RAISE_EXCEPTION" / "NODE_NOT_FOUND".

Error Analysis: A RAISE statement in the program "CL_GUI_ALV_TREE =============== CP" raised the exception condition "NODE_NOT_FOUND.

Information on where terminated: Termination occurred in the ABAP program "CL_GUI_ALV_TREE =============== CP" - in "EXPAND_NODE.The main program was "Z *************".

In the source code you have the termination point in line 10 of the (Include) program "CL_GUI_ALV_TREE =============== CM00L.

Source Code Extract:

Line SourceCode

1

2 METHOD EXPAND_NODE.

3 * Ensure node in control

4 DATE LT_NODE_KEY TYPE LVC_T_NKEY.

5 APPEND tag I_NODE_KEY TO LT_NODE_KEY.

6 CALL METHOD ME-> ENSURE_NODES_VISIBLE

7 Exporting IT_NODE_KEYS = LT_NODE_KEY

8 EXCEPTIONS NODE_NOT_FOUND = 1.

9 IF SY-SUBRC = 1.

>>>>> RAISE NODE_NOT_FOUND.

11 ENDIF.

I searched a few notes, after "NODE_NOT_FOUND", "CL_GUI_ALV_TREE =============== CP" and i found only 797734 Notes - Program terminates when you choose "Expand in new window" => Valid since 31/08/2006.

But, because, error occurs in execution of a Z program , I do not want to implement a SAP note before I convinced that the error does not occur due to programming errors.

Can you help identify why the error occurs?

Thanks a lot,

Regards

[Former Member]

heloo guys,

I have the following system: Linux SLES 10 (x86_64) / Oracle 10.2.0.4.0 / SAP ECC 6.0 Kernel Patch 221 (SAP_APPL 600 Patch: SAPKH60014).

In st22 i have the following error "RAISE_EXCEPTION" / "NODE_NOT_FOUND".

Error Analysis: A RAISE statement in the program "CL_GUI_ALV_TREE =============== CP" raised the exception condition "NODE_NOT_FOUND.

Information on where terminated: Termination occurred in the ABAP program "CL_GUI_ALV_TREE =============== CP" - in "EXPAND_NODE.The main program was "Z *************".

In the source code you have the termination point in line 10 of the (Include) program "CL_GUI_ALV_TREE =============== CM00L.

Source Code Extract:

Line SourceCode

1

2 METHOD EXPAND_NODE.

3 * Ensure node in control

4 DATE LT_NODE_KEY TYPE LVC_T_NKEY.

5 APPEND tag I_NODE_KEY TO LT_NODE_KEY.

6 CALL METHOD ME-> ENSURE_NODES_VISIBLE

7 Exporting IT_NODE_KEYS = LT_NODE_KEY

8 EXCEPTIONS NODE_NOT_FOUND = 1.

9 IF SY-SUBRC = 1.

>>>>> RAISE NODE_NOT_FOUND.

11 ENDIF.

I searched a few notes, after "NODE_NOT_FOUND", "CL_GUI_ALV_TREE =============== CP" and i found only 797734 Notes - Program terminates when you choose "Expand in new window" => Valid since 31/08/2006.

But, because, error occurs in execution of a Z program , I do not want to implement a SAP note before I convinced that the error does not occur due to programming errors.

Can you help identify why the error occurs?

Thanks a lot,

Regards

[Clemenss]

Hi Indubitabil,

>

> But, because, error occurs in execution of a Z program , I do not want to implement a SAP note before I convinced that the error does not occur due to programming errors.

Yes, good idea. I do not know the Z program but I am convinced the error is caused by program error in Z program. In the dump, or better in debugger when program dumps, you can check the call stack and possibly you find out where and why the method EXPAND_NODE is called for an invalid tree node.

It is not very easy to help if nearly no details are given.

Regards,

Clemens

[Former Member]

Hi,

This is happens when the node is not assigned a proper Node Key. The Node Keys are assigned in a sequence. So, based on that the Tree is created. I guess, in the Z Report, after the data is populated, the node keys are not properly sequenced. Have a look at the demo code BCALV_TREE_01. Here look at the section

4.Create hierarchy (nodes and leaves)

• 4a. Select data

• 4b. Sort output table according to your conceived hierarchy

• 4c. Add data to tree

Hope this will help you to resolve your problem.

Thanks,

Samantak.