Explain Cardinality,Singleton Property & Lead selection

Hi All,
Please explain me in detail the concepts of Cardinality,Singleton Property & Lead selection.
I had already gone through enough documents and have very vague idea.
Regards,
Venkat.

Hi Venkat,
Please check the [document|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a048387a-0901-0010-13ac-87f9eb649381?quicklink=index&overridelayout=true]
Hope that will helps you.
Thanks
Arun

Similar Messages

Concept behind Cardinality, Singleton property?

hi,
      will anyone explain me the concept of cardinality, singleton & Initialize lead selection properties of noce. by example... when i need to set singleton /Initialize lead selection property true / fasle for perticular node...
suppose i am having node structure like this ..
                 CLAIM                                   Node1
                        CLAIMITEM                    Node2
                                 EXPENSETYPE    Node3 ... Comes under node2
                                      key
                                      value
                                Claimid                attribute.. Comes under node2
                                Description          attribute.. Comes under node2
                                Amount               attribute.. Comes under node2
if Node CLAIMITEM is bind to table on view....having 4 column ,
first as dropdown by index bind to EXPENSETYPE value...
second as inputfield bind to Claimid....
third as inputfield bind to Description....
fourth as inputfield bind to Amount....
table is having multiple rows so Node CLAIMITEM must have cardinality 0...N
what abt others...
please dont give me any link which is alreay on sdn...
jst try to explain me how does it go and why if possible ..
thanks
saurin shah

Hi Saurin,
Please check this Article which explains in detail about Context,cardinality and singleton properties with examples.I hope it will help you.
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/60730016-dbba-2a10-8f96-9754a865b814

What is the role of singleton property in clustered environment.

Hi
Could anyone suggest links or tutorials explaining the singleton property and its importance in clustered environment(both active-active and active-passive).
Please anyone explain this .
I've googled and couldn't understand the explanations which I've gone through.
Appreciate your help.
Regards,
Dev...

HI,
click on ur node and on the singleton proprty click F1. u will get the full detail.
The property "Singleton" specifies the number of instances that can exist in a dependent context node (that does not belong directly to the root node).
If the property "Singleton" is set, exactly one instance of the node exists. Its content changes when the lead selection of the parent node changes.
If the property "Singleton" is not set, one instance per parent instance exists. The content of the instances does not change when the lead selection of the parent changes.

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

Cardinality - Singleton - Selection

Hi All,
Can anyone explain me detaily about these -
1.what is cardinality,Singleton and selection.
Regards,
Karthick

Hi Karthick,
Please find the answers below:
Cardinality: The cardinality defines how often a node is to be instantiated at runtime u2013
that is, how many elements of this node are available at runtime.
u25CF 1u20261
Only one element is instantiated.
u25CF 0u20261
At runtime, no more than one element is instantiated, but it is also possible that no
element is instantiated.
u25CF 1u2026n
n elements can be instantiated, but at least one element must be instantiated.
u25CF 0u2026n
The number of instantiated elements of the context node can vary.
Example:
The context node "Vehicle" is used to describe the fleet of a car rental company. It has the
cardinality 1u2026n and is filled from a database table. A number of attributes of this node have a
specific value for each vehicle.
The database table indicates that the company owns three vehicles, each with unique
registration dates and unique license plate numbers. Thus, to display this table in the Web
Dynpro application, 3 elements of the context node Vehicle must be instantiated; the
cardinality of the node must therefore be 0u2026n or 1u2026n. (If the Vehicle node is to be filled with
values in the context of another function u2013 for example, from a table of all currently available
cars u2013 the cardinality 0u2026n should be used since this table could very easily be empty u2013 that
is, if all cars are rented out.)
*The u201CSingletonu201D Property:*
For each customer of a car rental company, the two attributes u201Crented fromu201D and u201Crented tillu201D
are listed in the context. At runtime, the context then contains the additional relevant values:
If each customer has multiple addresses, it may be necessary to include a child node for the
addresses below the Customer child node. In this manner, the data content of a root node
can rapidly become very large if, at runtime, all customers are displayed with all their
addresses for each vehicle of the of the car rental company. _*To limit the content of a context*_
_*node at runtime, the context node can be assigned the u201Csingletonu201D property*. As a result, the_
_elements of the relevant node are instantiated for only one element of the parent node._
_In other words:_Unlike the cardinality of a node, which describes the number of possible elements within the
node, the u201Csingletonu201D property determines whether or not these elements are set for all
elements of the parent node (non-singleton) or for exactly one element of the parent node
(singleton).
The elements of the child node Customer are only available to one element of the parent
node Vehicle and not to all other elements. However, if you want to instantiate the elements
of the Customer node for all vehicles, you must remove the singleton property for the
Customer node.
*Lead Selection*:
At runtime, every child node set as a singleton contains the elements for exactly one element
of the parent node. For this purpose, one element from the set of possible elements of the
parent node must be highlighted. This is achieved by initializing lead selection. For each
newly created context node, lead selection is initialized automatically, but this setting can also
be deactivated. However, lead selection must generally be initialized for every context node.
u25CF Using the preset automatic initialization of lead selection:
In this case, the first element of a node is always assigned the lead selection
property.
u25CF Manual initialization of lead selection:
If the automatic initialization was deactivated, the lead selection must be programmed
manually. However, in this case it is possible to assign this property to an element
other than the first element of a node.
For the above example, this means:
The singleton property of the context node Customer specifies that the elements of this node
are only instantiated for one of the three vehicles at runtime u2013 that is, the element that bears
the lead selection. Since the lead selection was initialized automatically, this is the first
element of the Vehicle node, which in this case is the element Red Car. However, it would
also have been possible to manually set lead selection for one of the other two elements (for
example, using an index).
Edited by: Vinay Kumar Amruth on Jun 26, 2009 8:00 AM

EXPLAIN LEAD SELECTION WITH AN EXAMPLE? WHY IT IS IMPORTANT?

HI ALL,
please explian me lead selection with an example? what is the significance of lead selection?

This is something that is not well explained anywhere, and it probably won't be well explained by me, either, but maybe when the clever people finish correcting me, we will have a good story.
Lead selection is a mechanism that WDA uses to define a default row in a multi-element (e.g. table) node in the context.
For example, lets say you display a list of flights in a table in WDA.
You put them into an internal table and bind them to a context node.
If the user selects one (by clicking the button beside the row of the table) then your program would like to know which row was selected. You could loop over the whole table looking for some indicator, but that is tedious and time consuming.
Because of the lead selection mechanism, you can call GET_STATIC_ATTRIBUTES which gets the values for a single row of the table. Which row? Well, the row selected by the user, which is called the lead selection. I think it is called 'lead selection' because if you select a range of rows, then the first or leading row is set as the lead selection and that is the one you will get if you ask for a single row.
Of course, nodes don't have rows, they have elements, but if you promise not to say it out loud, you can think of them as rows.
So lead selection is all about providing easy access to the selected element of a multi-element node If you ask the table for just one row, it will give you the selected row.
With lead selection, asking a table for one row without saying which one would probably be an error, but with lead selection, it makes sense. There are many node functions that work on a element that use lead selection to choose the element when you call them for a node with cardinality > 1.
There are a bunch of methods in IF_WD_CONTEXT_NODE that allow you to set and get the lead selection, and use it to do various things. This is useful, because with a big list of data, the thing you are probably interested in is the one the user has clicked.
For example you can write a program that displays spfli and a button that calls lr_node->GET_STATIC_ATTRIBUTES and displays the selected row's carrid and connid in a message. You can then select a row of the table and your button will always know which one you have chosen. It might be psychic, but it is probably really lead selection at work.
Or you can have an input field where you enter a row number and click a button. If you call
. lr_node = wd_context->get_child_node( 'SPFLI' ).
. lr_element = lr_node->get_element( index i ).
. lr_element->set_lead_selection( )
in the button action method you will see the button for that row suck into the screen as if you had clicked it.
I hope this does more good than harm.
Edited by: Russell Day on Feb 16, 2008 1:47 PM

Empty table & lead selection

Hi folks,
We are having a small problem with our new web dynpro application. Basically we have table, which is populated when the application is started. Under the table we have "detail area", and it shows more detailed information about the selected element in the table. This works basically without problems.
The problems appear when the table happens to be empty. In that situation we got a runtime error saying "Context binding for property VALUE of <attribute name> cannot be resolved: Node <context node> does not contain any elements".
We have also functionality to delete elements in the table, and this causes the same problem. Even if the table contains elements, but we delete those, then when the last element gets deleted, we got the runtime error.
How to handle this kind of situation? My guess is that the lead selection functionality is causing the problem. If the table is empty, no element can be set as selected.
The cardinality of the relevant context node is 0...n, and selection 0...1.
Regards,
Karri

Hi Niraja,
I am displaying data from 2 tables VBAK & VBAP. Depending up on the lead selection in VBAK am filling the data in VBAP. I can delete all the records from first table & still not end up in any error. I will try explain my procedure to you.
Below are the properties for my 2 context nodes:
VBAK:
Cardinality : 0..n
Selection : 0..n
Initialization Lead Selection: Unchecked
Singleton:   No
VBAP:
Cardinality : 0..n
Selection : 0..1
Initialization Lead Selection: Checked
Singleton:   Yes
Supply Function: SUPPLY_FETCH_VBAP_DATA
The 2 tables have the following properties set:
selectionChangeBehaviour : Auto
selectionMode: Auto
As you can see by default the leadSelection isn't set for the 1st table. But as soon as the user selects any record the leadSelection is set & the corresponding data is fetched into the 2nd table element.
METHOD supply_fetch_vbap_data .
DATA: ls_vbak TYPE ig_componentcontroller=>element_vbak,
        lt_vbap TYPE ig_componentcontroller=>elements_vbap.
CALL METHOD parent_element->get_static_attributes
    IMPORTING
      static_attributes = ls_vbak.
SELECT * FROM vbap INTO TABLE lt_vbap WHERE vbeln = ls_vbak-vbeln.
node->bind_table( new_items = lt_vbap ).
ENDMETHOD.
The user first enters a customer number & the corresponding orders are fetched from VBAK & bound to the first table. Below is the coding for the buttons action handler:
METHOD onactionfetch .
DATA : wd_node   TYPE REF TO if_wd_context_node,
         it_vbak TYPE ig_componentcontroller=>elements_vbak,
         lv_kunnr TYPE ig_componentcontroller=>element_vbak-kunnr.
wd_node = wd_context->get_child_node( name = 'PARENT1' ).
CALL METHOD wd_node->get_attribute
    EXPORTING
      name = 'KUNNR'
    IMPORTING
      value = lv_kunnr.
wd_node = wd_context->get_child_node( name = 'VBAK' ).
SELECT * FROM vbak INTO TABLE it_vbak WHERE kunnr = lv_kunnr.
IF sy-subrc EQ 0.
    wd_node->bind_table( new_items = it_vbak ).
ELSE.
ENDIF.
ENDMETHOD.
Regards,
Uday

Cardinality & singleton

HI Friends
Can anyone explain me regarding "cardinality&Singleton"
with a small example
I have gone through some of the blogs but I am not getting that much clarity regarding these terms
Thanks in advance

Hi,
The cardinality property
The cardinality property is composed of a pair of values that control the maximum and minimum number of elements may contain at runtime.
The cardinality property may have four possible values:
     0..1     Zero or one
     0..n     Zero or more
     1..1     One and only one
     1..n     One or more
The first part of the cardinality describes the minimum number of element s element collection may contain. This value is either zero or one, and is stored as a Boolean value. This value can be obtained at runtime by calling the method node.getNodeInfo().isMandatory().
The second part of the cardinality describes the maximum number of elements s element collection may contain. This value is either a 1 or an n (meaning many) and is stored as a Boolean value (false = 1, true = n). This value can be obtained at runtime by calling method node.getNodeInfo().isMultiple().
If has a cardinality of 1..<something>, then it can be assumed that after the context has been initialised, there will be at least one element present in the node collection. This element is known as the default element and cannot be deleted!
If you attempt to perform some action on a node that would violate the constraints of the cardinality, then you will get a runtime exception in the context. E.G., trying to add a second element to a node of cardinality 0..1, or trying to delete the last element from a node of cardinality 1..n.
The singleton property
The singleton property critically affects the relationship between the child node and its parent node .
If is declared at design time, then the generated interface for this node will vary depending on whether it is a singleton or non-singleton node.
Important:
     All non-singleton child nodes are associated with their parent node on a per parent element basis
There is a one-to-one relationship between each element in the parent nodes element collection and the corresponding child node.
If has n elements in its element collection, then you will have n distinct instances of the non-singleton child node .
Non-singleton child nodes can be created by their respective parent element.
     Singleton child nodes however, are associated with their parent node on a per node basis.
Irrespective of the number of elements in the parent nodes element collection, there will only ever be one instance of the singleton child node .
The singleton child node holds the data relevant for the element at the lead selection in the parent nodes element collection.
Singleton child nodes must be created by their parent node. Since there can only ever be one instance of a singleton child node, it is impossible for an element in a parent node collection to create a singleton child node.
From Inside Webdynro For Java
Regards
Ayyapparaj

Hi! regarding the singleton property in webdynpro abap

Hi experts ,
Could anyone explain me in detail the property of singleton and wht r the conditions tht we should use wht will represents..
plz explain me in detail......rather than sending links plz do explain me in detail....
Regards,
Sana...

Cardinality : number of possible elements within the node.
Singleton property means whether or not all instances of this node get created at runtime or not.
Singleton property is mostly used to save memory & increase performance. we would go for singleton nodes in cases where UI needs only display from one-instance of data from my node.....
What happens when you set singleton property to YES for a node?? Assume you have context structure like
Context
     Vehicle( parent node )
       ( attribute veh-ID primary key for all types of vehicles, dealer, area )
          twowheeler( subnode of vehicle with cardinality-0..n singleton-NO)
                    ( attributes veh-ID, regno, model, color)
          fourwheeler( subnode of vehicle with cardinality-0..n singleton-YES)
                   ( attributes veh-ID, regno, model, color)
At design time you fill the data within this context. Now you have 100 entries under the subnode twowheeler & 90 entries under the subnode fourwheeler . You create UI elements to display the node twowheeler details in a View . At runtime when user selects the veh-ID and identifies that a twowheeler data needs to be fetched/displayed all the 100 entries for the twowheeler node get created in the background although you are displaying only the ONE corresponding to the veh-ID.
if Veh-ID selected coresponded to fourwheeler( singleton property -yes) only ONE row of the data from the fourwheeler entries would have been fetched and ONLY Once instance of the fourwheeler would be created by background process!!
thus saving memory & processing time.
Scenarios singleton-YES
If i were required to display details of only ONE vehicle based on the entered Veh-ID , i will make twowheeler & fourwheeler nodes singleton-YES.
Scenario singleton-NO
if i were required to show all the vehicles that belong to one particular Area.

What is the significance of Singleton Property?

Hello guys!!!
Can some one elobarate the significance of Singleton Property?
Also, please suggest me a scenario, where we use Singleton Property.

HI,
click on ur node and on the singleton proprty click F1. u will get the full detail.
The property "Singleton" specifies the number of instances that can exist in a dependent context node (that does not belong directly to the root node).
If the property "Singleton" is set, exactly one instance of the node exists. Its content changes when the lead selection of the parent node changes.
If the property "Singleton" is not set, one instance per parent instance exists. The content of the instances does not change when the lead selection of the parent changes.

Unable to change singleton property of context parent node.

Hi
I am having a view context node structure as follows.
Root context Node
|__Parent
*****|__child 1
*****|__child 2
I have created a table view which is using above structure.
Now I have selected "Selection Mode" property of my table to "Multi", as i intend to select multiple rows in this table.
When i tried to run this application..I got following error :
com.sap.tc.webdynpro.progmodel.context.ContextException: Node(TableView.Person): selection cardinality does not allow multiple selection
What i traced from this problem is that i have set "singleton" property of my "Parent" context node to "true".
But what if i wish to change it to "false"...
I AM UNABLE TO DO THAT !!
Please help me out.
Thanks in anticipation.
Edited by: Saurabh Agarwal on Jun 23, 2008 8:20 AM

Yes....
Now i changed my Selection property of my component context...
and that change was automatically reflected to my view context...
Actually what is happening..
if mapping to component context is set in view context..
then Properties could not be changed directly from view context.
Thanks all....for your help..
my problem is solved now....
Thanks...

What is singleton property in Webdynpro

Hi,
What is singleton property in Webdynpro?
please explian along with diagram
Regards,
Sid.

hi,
Singleton Nodes
     It is very important to remember the difference in runtime behaviour between a singleton node and a non-singleton node. When a node is declared to be singleton, there will only ever be only one instance of that node-irrespective of the number of elements found in the parent nodes element collection. This is not the case for the non-singleton node. In this case, there will be as many instances of the non-singleton child nodes as there are elements in the parent nodes element collection.
     The significant point here is that when the lead selection in the parent element collection changes, the contents of the singleton child node become invalid. Consequently, the next time data is required from the singleton child node, the entire element collection must be rebuild in order that it match the data in the newly selected parent element.
     The task of rebuilding singleton child node must be performed by a dedicated supply function.
[http://help.sap.com/saphelp_nw70/helpdata/EN/81/95384162316532e10000000a1550b0/frameset.htm]
regards,
pinki

How to tackle the error - " The Lead Selection has not been set in view "?

Hi Guys,
I'm getting this error " The Lead Selection has not been set in view " . If any one has faced the same problem , then please guide me . I am new to WD ABAP so finding it difficult to track the reason.
TIA,
Vishesh

Hi Pradeep,
I have already checked "Initialisation Lead Selection" property . I have faced the same problem in another view also there it got solved by changing the cardinality. In this case, I had tried both cardinality and Lead selection property but nothing is working.
Thanx.

Getting "The Lead selection has not been set in view"Error during runtime

Hi Guys,
I'm getting this error " The Lead Selection has not been set in view " . If any one has faced the same problem , then please guide me . I am new to WD ABAP so finding it difficult to track the reason.
TIA
Moderator Message: Please search the forum before posting basic messages. Thread locked
Edited by: Neil Gardiner on Oct 1, 2010 3:48 PM

Hi Pradeep,
I have already checked "Initialisation Lead Selection" property . I have faced the same problem in another view also there it got solved by changing the cardinality. In this case, I had tried both cardinality and Lead selection property but nothing is working.
Thanx.

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

Explain Cardinality,Singleton Property & Lead selection

Similar Messages

Maybe you are looking for