ECATT abends during recording when lead selection is set to 0 on web dynpro

Question

We have a web dynpro application that works ok when running by itself.   When we tried to record ECATT testing on it, it abended after we click on a selection from a list of values.    The error on the browser indicated an error on the "lead select".   After reviewing the dump, we found that it abends on an exception when the lead selection on the ALV is not set.   When we changed our code to set the lead selection to 1, the ECATT recording worked.
We have a requirement to set the lead selection of ALV to 0 so we need to change back our code.   We just did the setting to 1 just to get ECATT recording to work for now.    Does anybody know why ECATT requires this?   Is there a support packs that fixes this?
Here is a snippet from ST22 for more details on this:
Runtime Errors         UNCAUGHT_EXCEPTION
Exception              CX_WD_CONTEXT
Date and Time          2007/02/07 14:50:06
Short text
An exception occurred that was not caught.
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_NODE===========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:
The lead selection has not been set. VIEW_TABLE
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_NODE===========CP" or "CL_WDR_CONTEXT_NODE===========CM00V"
"_RAISE_ELEMENT_NOT_FOUND"
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.
System environment
SAP-Release 700
Application server... "torsapd01"
Network address...... "10.2.75.183"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "4x AMD64 Level"
Character length.... 8 Bits
Pointer length....... 64 Bits
Work process number.. 0
Shortdump setting.... "full"
Database server... "TORSAPD01"
Database type..... "MSSQL"
Database name..... "PR3"
Database user ID.. "dbo"
Char.set.... "English_United State"
SAP kernel....... 700
created (date)... "Aug 28 2006 22:20:27"
create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
Database version. "SQL_Server_8.00 "
Patch level. 75
Patch text.. " "
Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
Memory consumption
Roll.... 16128
EM...... 16759616
Heap.... 0
Page.... 0
MM Used. 12713776
MM Free. 4042608
User and Transaction
Client.............. 200
User................ "SIC0010"
Language Key........ "E"
Transaction......... " "
Program............. "CL_WDR_CONTEXT_NODE===========CP"
Screen.............. "SAPMHTTP 0010"
Screen Line......... 2
Information on Caller ofr "HTTP" Connection:
Plug-in Type.......... "HTTP"
Caller IP............. "10.49.77.47"
Caller Port........... 8000
Universal Resource Id. "/sap/bc/webdynpro/sap/zpr3_base_price/"
Information on where terminated
Termination occurred in the ABAP program "CL_WDR_CONTEXT_NODE===========CP" -
in "_RAISE_ELEMENT_NOT_FOUND".
The main program was "SAPMHTTP ".
In the source code you have the termination point in line 11
of the (Include) program "CL_WDR_CONTEXT_NODE===========CM00V".
Source Code Extract
Line
SourceCde
1
method RAISEELEMENT_NOT_FOUND.
2
data: l_count type I,
3
l_node_name type string.
4
5
l_node_name = if_wd_context_node~get_path( ).
6
7
l_count = if_wd_context_node~get_element_count( ).
8
if l_count = 0.
9
raise exception type cx_wd_context exporting textid = cx_wd_context=>NODE_EMPTY node_nam
10
elseif element_index = if_wd_context_node=>use_lead_selection.
>>>>>
raise exception type cx_wd_context exporting textid = cx_wd_context=>NO_LEAD_SELECTION n
12
else.
13
raise exception type cx_wd_context exporting textid = cx_wd_context=>ELEMENT_NOT_FOUND n
14
endif.
15
endmethod.
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
1
SY-TABIX
0
SY-DBCNT
2
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
HTTP Control
SY-MSGTY
E
SY-MSGID
TD
SY-MSGNO
600
SY-MSGV1
000003587101
SY-MSGV2
0001
SY-MSGV3
EN
SY-MSGV4
SY-MODNO
0
SY-DATUM
20070207
SY-UZEIT
145005
SY-XPROG
SAPCNVE
SY-XFORM
CONVERSION_EXIT

Answer 1

Hi Eugene,
i suggest you raise an SMP ticket for these.
Looks like a bug at first glance.
regards
Phil