WD ABAP: Lead selection on a recursive node

Hi,
I would like to know if lead selection is permitted on a recursive node in WD ABAP.
As of now, methods 'set_lead_selection_index' or 'set_lead_selection' do not cause lead selection to change in my view, and the lead selection rests only with the first row in my table..(I have set the rowSelectable property to YES for my table.)
Also, method call 'set_selected' performed on my target element does not solve the problem.
Any help much appreciated!
Best Regards.

Hi Adithya,
Yes, you can have a leadSelection on a recursive node and it can be changed by the same methods that are used for non-recursive ones.
Best regards,
Thomas

Similar Messages

Obtain a reference to the element at lead selection

I am trying to obtain a reference to the element at lead selection of a context node (Node name is Person) of component controller, i had a method initPerson() to initialize the values, so when i am writting
IPersonElement personEl = wdContext.nodePerson().currentPersonElement();
to obtain a reference , at IPersonElement it is giving me an error
IPersonElement can not be ressolved or is not a type !
can anyone help me on this
Thanks in advance.
Rashmi.
Edited by: Rashmi Gupta on Nov 6, 2008 11:40 AM
Edited by: Rashmi Gupta on Nov 6, 2008 11:41 AM

Hi
Usse
view/controllerName.IPersonElement
Just like given example below
IPublicAllInOne.IFlight_List_1Element ELE = wdContext.nodeFlight_List_1().createFlight_List_1Element(new Bapisfldat());
PS: Orgine the import files. by pressing control+Spece button at time
or
controlSpeceO
Thanks

WDABAP: note of change of Lead Selection overall component

Hi,
I would like to build a similiar wd-application like wd-component 'wdt_master_detail'. There you will see a table with fly-data and below some details of the actual selected row of the table (by lead selection).
The difference is that I want to seperate the data retrieval in a model-component(z_model) and for the table / details two seperate wd-components(z_table / z_detail) which mapps the fly-data. The wd-application instantiate a wd-component (z_container) which includes in its view z_table and z_detail.
When the lead selection changes(by selecting a new row in the table of z_table) the details of z_detail should change to the details of the element with the lead selection. But this does not work! By node->get_lead_selection_index in z_detail I get only the inital lead-selection. node->get_lead_selection_index in z_table provides the right index.
I tried also following: z_table calls z_model->set_lead_selection and this method set the lead selection of the original node new. But this does not help.
Has someone an idee what I have to do that the component z_detail receive the information? Has the z_model to raise an event with the information of the new index? I hope not.
Thanks a lot!
Regards,
Marcel
added 1:
I have an assumption why it does not work:
Maybe z_table and z_detail instantiates two separate z_model.
So a solution would be that z_container instantiates z_model and provide this instance to z_table and z_detail but I have absolutly no idee whether and how this could be working... Please kindly help.
added 2:
I thinking further a little bit loud...
I have the idea that z_container mapps the context from z_model and set this these to input-node.
z_table and z_detail mapps from z_container. ok, if I would like to create many application then I have to create related components(z_comp_appl_xx) and these components includes z_container. This would be maybe the solution if there is a instance problem(see added1) but I have tested and the details screen gets NOT the lead selection
Message was edited by: Marcel Schreier

Hi Marcel,
to extend Thomas comments, here are some suggestions to turn it into code. Hope it helps.
option A)
assuming you name the usages in z_container "usage_z_model", "usage_Z_table", "usage_Z_detail":
in componentcontroller of z_container methode wddoinit() do the following:
DATA lr_model_usage    TYPE REF TO    if_wd_component_usage.
lr_model_usage =   wd_this->wd_cpuse_usage_z_model( ).
IF lr_model_usage->has_active_component( ) IS INITIAL.
lr_model_usage->create_component( ).
ENDIF.
DATA lr_usage    TYPE REF TO    if_wd_component_usage.
lr_usage =   wd_this->wd_cpuse_usage_z_table( ).
IF lr_usage->has_active_component( ) IS INITIAL.
lr_usage->create_component( model_usage = lr_model_usage ).
ENDIF.
lr_usage =   wd_this->wd_cpuse_usage_z_detail( ).
IF lr_usage->has_active_component( ) IS INITIAL.
lr_usage->create_component( model_usage = lr_model_usage ).
ENDIF.
Following this way, it is required to name the usages of z_model in component z_table and z_detail "MODEL_USAGE".
option B)
in componentcontroller of z_table and z_detail create an interface-methode set_usage() with one parameter ir_usage type if_wd_component_usage
DATA lr_usage TYPE REF TO if_wd_component_usage.
lr_usage = wd_this->wd_cpuse_usage_z_model( ).
lr_usage->enter_referencing_mode( ir_usage ).
in component z_container method wddoinit() do the following:
DATA lr_usage    TYPE REF TO    if_wd_component_usage.
DATA lr_if_ctr_z_table TYPE REF TO iwci_z_table.
DATA lr_if_ctr_z_detail TYPE REF TO iwci_z_detail.
DATA lr_model_usage    TYPE REF TO    if_wd_component_usage.
*-- create instance of z_model
lr_model_usage =   wd_this->wd_cpuse_usage_z_model( ).
IF lr_model_usage->has_active_component( ) IS INITIAL.
lr_model_usage->create_component( ).
ENDIF.
*-- create instance of z_table
lr_usage =   wd_this->wd_cpuse_usage_z_table( ).
IF lr_usage->has_active_component( ) IS INITIAL.
lr_usage->create_component( ).
ENDIF.
*-- set usage
lr_if_ctr_z_table =   wd_this->wd_cpifc_usgae_z_table( ).
lr_if_ctr_z_table->set_usage( model_usage = lr_usage).
*-- create instance of z_deatil
lr_usage =   wd_this->wd_cpuse_usage_z_detail( ).
IF lr_usage->has_active_component( ) IS INITIAL.
lr_usage->create_component( model_usage = lr_model_usage ).
ENDIF.
*-- set usage
lr_if_ctr_z_detail =   wd_this->wd_cpifc_usage_z_detail( ).
lr_if_ctr_z_detail->set_usage( model_usage = lr_usage).
regards, Ulli

Why does GET_STATIC_ATTRIBUTES or SET_STATIC_ATTRIBUTES change lead selecti

I loop over all elements of a context node, and change some attributes.
The code looks like this:
      LOOP AT lt_element_list INTO lo_el_element.
        lo_el_element->get_static_attributes( IMPORTING static_attributes = ls_element ).
        ls_element-created_by_name = get_user_name( iv_user_id = ls_element-created_by ).
        ls_element-changed_by_name = get_user_name( iv_user_id = ls_element-changed_by ).
        lo_el_element->set_static_attributes( EXPORTING static_attributes = ls_element ).
      ENDLOOP.
This coding seems to change the the lead selection of the context node, which leads to problems somewhere else.
Why does it change the lead selection and how can I prevent it?

hi daniel.....
         i dont think there is a need for looping in this manner.
         you just get all the values of a node into an internal table.
         and then loop the internal table an make changes in it.
         then clear the node and pass this currently changed internal table into the node.
          the lead selection changes because you are setting the attribute and it might be stored in index 1 or the to the index where the lead selection is referred to. this might be your problem.
---regards,
   alex b justin

Breifly xplain wht lead selection ,cardinality &singleton&supply function

Hi Friends ...
             Let plz xpalin in breif   wht is lead selection ,cardinality &singleton&supply function and how these all helpfull whtz the relation ship between while creating a table...
itz bit urgent for me am working with dynamic tables and am in confuse...plz make it out this query...

Lead selection
     Leadselection is the property which is used to get the index of the selected row of the table
"OnLeadSelect" is the method used to fire an action when a row is selected
     The Method wdContext.<node>().getLeadSelection() can be used to
find out the index of the selected element.
Cardinality
Any node or attribute that has the context root node as its immediate parent, is known as an independent node or attribute.
Any node or attribute that has some other node as its immediate parent, is known as a dependent node or attribute.
All context nodes are collections.
A node collection is composed of elements, where an element is an aggregation of the nodes immediate children (attributes and/or other nodes).
The cardinality property controls the number of elements a node collection may hold at runtime.
Every context node has a property called Cardinality. This property is composed of two values that
taken together, describe the maximum and minimum number of elements the node collection may hold
at runtime.
Cardinality Minimum: 0 or 1
Cardinality Maximum: 1 or n
Therefore, there are four possible cardinality values (specified as <Min>..<Max>)
0..1 Zero or one elements permitted
0..n Zero or more elements permitted
1..1 One and only one element permitted
1..n One or more elements permitted
Singleton
All independent nodes are forced to be singletons. This is because the context root node has one and only one element.
Singleton is boolean
TRUE : One instance will be created for all te nodes
FALSE : Every Element in the parent node collection,there will be a distinct instance of the child node.
Why Singleton
     -Efficiency
     -Less Memory
     -Lazy Data Access(Creates instance only when needed,till then it will remain unprocessed)
Supply functions
     Supply functions are the mechanism to repopulate child nodes when the lead selection in the parent node
changes. When a singleton child node is declared, you must also write an accompanying supply function.
The Web Dynpro Framework will then automatically call your supply function when the lead selection
in the parent node changes.
Regards
Chaitanya.A

Error "Lead selection not set for context node"

Hi everyone,
I've got a Tree control in WebDynpro ABAP and I've implemented an "expand all" button.
Here's the coding:
METHOD expand_node_rec.
DATA lo_el_child TYPE REF TO if_wd_context_element.
DATA lo_node_children TYPE wdr_context_child_map.
DATA wa_lo_node_children LIKE LINE OF lo_node_children.
DATA lo_nd_child TYPE REF TO if_wd_context_node.
DATA lo_kschl TYPE klschl.
DATA lv_has_children TYPE boolean.
lo_el_child = node->get_element( ).
lo_node_children = node->get_child_nodes( ).
node->get_attribute( EXPORTING name = 'KSCHL' IMPORTING value = lo_kschl ).
node->get_attribute( EXPORTING name = 'HAS_CHILDREN' IMPORTING value = lv_has_children ).
IF lv_has_children = abap_true.
    node->set_attribute( name = 'IS_EXPANDED' value = abap_true ).
ENDIF.
LOOP AT lo_node_children INTO wa_lo_node_children.
    lo_nd_child = wa_lo_node_children-node.
    me->expand_node_rec( node = lo_nd_child ).
ENDLOOP.
ENDMETHOD.
However I'm getting the error above: "Lead selection not set for context node".
Any suggestions?
Edited by: DEVELOPMENT THEMIS on Jul 7, 2011 6:34 PM

hi developement Themis,
I think u didn't diclare "node" as context node. So declare it as a context node before using as a context node..as below
DATA node TYPE REF TO if_wd_context_node.
or u can use "lo_nd_child " as ur context node in ur program in place of "node"
then I think this error will be removed.
thanks,
simadri

How to identify the current lead selection is child or parent in rec node

Hi
I am using a recursive node to populate a table with TreeByNestingTableColumn as master column. Now my problem is how do I identify if the current selected row in the table is a child or parent? When I get the lead selection value, I find that its the same for the parent and the child. I am setting the isLeaf and hasChildren boolean properties appropriately as false and true for parent and true and false for child. But since the lead selection is returning the same the below rsTableElement always gives me the parent, I always get those parameter values as that of parent. I am writing this inside the onleadSelect event of the table.
IRsTableElement rsTableElement = (IRsTableElement) wdContext.nodeRsTable().getElementAt(wdContext.nodeRsTable().getLeadSelection());
In this scenario how do I know if the current selection is made on a child?
Appreciate for all help and any code snippets.
Thanks,
KN.

Hi KN,
I guess you want to check if the node that you selected is parent or child.. This can be achieved by using getTreeSelection() method of IWDNode.
If you write following code in your lead selection action, you can determine the if it is a parent or child node.
wdComponentAPI.getMessageManager().reportSuccess(wdContext.nodeRsTable().getTreeSelection() +"");
the output will be something like
<ViewName>.RsTable.0.ChildRsTable.1.ChildRsTable.0.. depending upon which node you have selected.
That way you can find out if it is a parent or child node.
Abhinav

Dynamic context in web dynpro abap: recursion node is possible?

Hi,
i'm working with web dynpro ABAP and I need to create a dynamic recursion node. Is possible?
thank you.
Regards.
Al

Hello Saravanan,
this is my code that creates a context node with recursion node, but supply_method i never called. why? could you help me?
      CALL METHOD lr_root_info->add_new_child_node
        EXPORTING
          name                         = y_name
          is_mandatory                 = abap_false
          is_multiple                  = abap_true
          is_mandatory_selection       = abap_false
          is_multiple_selection        = abap_true
          is_singleton                 = abap_true
          is_initialize_lead_selection = abap_true
          is_static                    = abap_true
          supply_method                = 'SUPPLY_NAV_LIST'
        RECEIVING
          child_node_info              = lr_node_info.
      ls_attribute-name = 'TEXT'.
      ls_attribute-type_name = 'STRING'.
      CALL METHOD lr_node_info->add_attribute
        EXPORTING
          attribute_info = ls_attribute.
      ls_attribute-name = 'ENABLED'.
      ls_attribute-type_name = 'WDY_BOOLEAN'.
      CALL METHOD lr_node_info->add_attribute
        EXPORTING
          attribute_info = ls_attribute.
      lr_node_info->add_recursive_child_node( child_name = y_name_nav child_info = lr_node_info is_static = abap_false ).
Thank you.
Al

WD ABAP: Recursion Nodes that Repeat Tree Nodes with Embedded Tables ???

At Rich H's suggestion, I'm posting this here as well as in the blogs.
Suppose you've got a tree context with a node that has a table embedded under it. (For example, the TREE_WITH_TABLE view of WDR_TEST_EVNT has this kind of context substructure.) Call this node "NODE_WITH_TABLE."
You now define a recursion node underneath "NODE_WITH_TABLE" and specify "NODE_WITH_TABLE" as the repeated node for this recursion node. Call this recurion node "RECURSION_NODE".
Lo and behold - the table fills properly when you're on any instance of "NODE_WITH_TABLE", but not when you're on an instance of "RECURSION_NODE".
I'm hoping that:
a) I'm doing something wrong;
OR
b) There's an easy work-around/alternative I'm not seeing
OR
c) SAP will give recursion nodes enough memory to carry any table(s) embedded in the nodes they're repeating.
'Cause I sure don't want to have to define "n" levels of tree-nodes that have different copies of the same table(s) embedded in them.
Message was edited by: Armin Reichert

/people/david.halitsky/blog/2006/08/16/recursion-nodes-that-repeat-tree-nodes-with-embedded-tables-in-wd-abap-not
Maybe you might want to back out your weblog as it is not really a place to ask these types of questions. Think of it this way, if you are allowed to do this type of weblog, what is stopping any other weblogger. Hence the weblogs would just be another forum, which I don't think anyone wants.
Regards,
Rich Heilman

Set node to lead selection.

Hi Gurus,
I have a requirement where my current data which is displayed is from node 4.
But i need to manipulate some data in the table of node 3.
I have coded as follows:
open_alv = wd_context->get_child_node( name = 'NODE_OPEN' ).
OPEN_ALV->GET_STATIC_ATTRIBUTES(
                                   IMPORTING
                                   STATIC_ATTRIBUTES = LT_OPEN ).
But i am getting error saying following node not set to lead selection.
Can someone tell me workaround for this..?
Best Regards,
navin fernandes.

Hi,
Use the above mentioned method get_static_attributes_table to fetch data of both Node 3 and 4.
To delete rows from Node 3 which are selected for Node 4, just loop at fetched data of Node 3, then inner loop at data of Node 4, compare row of node 3 against Node 4 and delete that row from that loop index.
Bind the internal table back to Node 3.
Sample Algo -
loop at node3 into wa_3.
lv_tabix = sy-tabix.
loop at node4 into wa_4.
    if wa_3 = wa_4.
     delete node3 index lv_tabix.
   endif.
endloop.
endloop.
Regards
Manas Dua

WD:ABAP change lead selection

Hi all,
I need to change the lead selection according to a particular table column. The lead selection is set to the first row of the table. The table has some input fields which already contain values. If the user changes the value of the input field in any row, the lead selection has to be changed to that row of the table without having to select that row. I wrote the code in onEnter event of the table, but it is returning the values of the first row that has the lead selection. How do I change it? It would be helpful if u could please post the code too.
Thanks,
Sravanthi

Hi,
You can change it in ModifyView method. You can use setLeadSelection method.
Regards,
Parminder

Regarding lead selection?

i m getting this error when i clivk on one button.
how can i resolve this
Error when processing your request
Note
The following error text was processed in the system CGD : The lead selection has not been set. NURSING
The error occurred on the application server cgslsvr3_CGD_20 and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: RAISEELEMENT_NOT_FOUND of program CL_WDR_CONTEXT_NODE===========CP
Method: PATH_TABLE_GET_ELEMENT2 of program CL_WDR_CONTEXT_NODE===========CP
Method: GET_BOUND_ELEMENT of program CL_WDR_VIEW_ELEMENT_ADAPTER===CP

there can be many possibilities for this, without knowing what you have done it is difficult to answer
There are no Elements in the Context node, change the cardinality of your context node to 1..1 or 1..n
Abhi

Reading and modifying data in a recursive node

Hi All,
I am using a TreeByNesting column in a table UI element of my component.
For this purpose I have created a node in the context - ('TREE') which contains a recursive node - ('RECURSIVE_TREE').
What would be the simplest way to read the data from this node ? And how do I go about changing a single line of information
within the node ?
Thanks,
Fathima

What would be the simplest way to read the data from this node?
Reading data from a recursive node is no different to reading any normal node. It's just that you have a very simple way of holding the same structure.
Once you have a reference to the element of a node (a single line of data), then updating it is no different to updating a line of a table.
More issues are associated with making and setting lead selections for an element (all parent elements also need to be lead selected and no child elements). Searching through the hierarchy, etc.
Where I have used this functionality I have often set up search tables with the key data that I want to search in a flat table and a reference to the corresponding element - much easier to search then - without having to resort to recursive coding!
Could you elaborate a little on what exactly you are having an issue with?
Cheers,
Chris

RE:Web dynpro in ABAP _lead selection

Hi all,
What do you mean by Lead Selection in Web dynpro ABAP.What is its use.
Regards,
Alex.

hi ,
refer this SAP online help
http://help.sap.com/saphelp_erp2005/helpdata/EN/7a/787e40417c6d1de10000000a1550b0/content.htm
eg u can select the particular row of a table via lead selection
reading context node cn_table
DATA : lo_nd_cn_table TYPE REF TO if_wd_context_node ,
         lo_el_cn_table TYPE REF TO if_wd_context_element ,
         ls_cn_table    TYPE wd_this->element_cn_table.
*   navigate from <CONTEXT> to <CN_TABLE> via lead selection
lo_nd_cn_table = wd_context->get_child_node(
                   name = wd_this->wdctx_cn_table ).
**    get element via lead selection
lo_el_cn_table = lo_nd_cn_table->get_lead_selection( ).
lo_el_cn_table->get_static_attributes( IMPORTING
             static_attributes = wa_table ).
regards,
amit

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

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

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

WD ABAP: Lead selection on a recursive node

Similar Messages

Maybe you are looking for