Causing Runtime error

Question

Hi,
I am getting the Following runtime error, can u please tell me the cause for this.
What happened?                                                                                |
The exception 'CX_WD_CONTEXT' was raised, but it was not caught anywhere along
the call hierarchy.
Since exceptions represent error situations and this error was not
adequately responded to, the running ABAP program
'CL_WDR_CONTEXT_ELEMENT========CP' has to be
terminated.
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
An exception occurred which is explained in detail below.
The exception, which is assigned to class 'CX_WD_CONTEXT', was not caught and
therefore caused a runtime error.
The reason for the exception is:
Element Is Not (or No Longer) Bound to a Node
Error analysis                                                                                |
An exception occurred which is explained in detail below.
The exception, which is assigned to class 'CX_WD_CONTEXT', was not caught and
therefore caused a runtime error.
The reason for the exception is:
Element Is Not (or No Longer) Bound to a Node
How to correct the error
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"UNCAUGHT_EXCEPTION" "CX_WD_CONTEXT"
"CL_WDR_CONTEXT_ELEMENT========CP" or "CL_WDR_CONTEXT_ELEMENT========CM00I"
"IF_WD_CONTEXT_ELEMENT~GET_INDEX"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.           
Information on where terminated
Termination occurred in the ABAP program "CL_WDR_CONTEXT_ELEMENT========CP" -
in "IF_WD_CONTEXT_ELEMENT~GET_INDEX".
The main program was "SAPMHTTP ".
In the source code you have the termination point in line 4
of the (Include) program "CL_WDR_CONTEXT_ELEMENT========CM00I".
Source Code Extract
Line
SourceCde
1
method if_wd_context_element~get_index .
2
3
if me->node is not bound.
>>>>>
raise exception type cx_wd_context exporting textid = cx_wd_context=>element_not_bound.
5
endif.
6
7
read table node->collection with key table_line = me transporting no fields.
8
assert sy-subrc = 0.
9
my_index = sy-tabix.
|   10|endmethod.                      
Thanks In advance.
Mary

Answer 1

Hi Mary
It is clearly saying the elements are not bound to the node and you are trying to access the node..
i.e. you have not binded internal table to the node.
Abhi