on 08-19-2009 6:39 PM
Hi,
I am new to Webdynpro and I created my first application by following some blog on a portal.I was able to activate my application successfully and when I executed I get this below error message.
I checked the cardinality and it is 0..1.My Inti.Lead Selection is set to NO.
I mappedthe nodes in my views also. But still i don't know whay am getting this error.
Note
The following error text was processed in the system RS2 : Adapter error in &VIEW_ELEMENT_TYPE& "VBELN" of view "Z_MYFIRST_WEBDYNPRO.MAIN": Context binding of property VALUE cannot be resolved: Node MAIN.1.NODE_VBAK does not contain any elements
The error occurred on the application server ucerp18_RS2_00 and in the work process 11 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: RAISE_FOR of program CX_WDR_ADAPTER_EXCEPTION======CP
Method: RAISE_BINDING_EXCEPTION of program CL_WDR_VIEW_ELEMENT_ADAPTER===CP
Method: GET_BOUND_ELEMENT of program CL_WDR_VIEW_ELEMENT_ADAPTER===CP
Thanks
Kiran
There was some error in a method and I corrected it.
Thanks to you all for sharing your thoughts.
regards,
Kiran
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Kiran,
For your input fields cardinality must be 1:1 and also check the Initialization lead selection check box in properties.
Thank You,
Gajendra.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
I changed the cardinality to 1:1 and I can see the selection screen. But, can you please explain why I should change this from 0:1 to 1:1.
Now I have a new error:
After I enter the sales order Number and hit my FIND button, am getting this error:
The following error text was processed in the system RS2 : Could not find attribute VBELN
Thanks,
Kiran
Now am getting a different error:
Invalid operand type for the MOVE-CORRESPONDING statement
Thanks
Kiran
Edited by: kiran dasari on Aug 20, 2009 10:54 PM
Hi Kiran,
I faced similar kind of error when the binding was not created in the view properly.Check if the binding is proper and also the cardinality should be 0:n and selection 0:1
Thanks,
Deepthi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Main view is like my selection-screen so i have only input fields and my cardinality is therefore 0:1 .
My second view (Secondary) is ALV and i maintained 0:n cardinality. Pl let me know, if this is the right way.
Coming to binding on main view...in my input fields, i can clearly see the names like: MAIN.NODE_VBAK.VBELN & MAIN.NODE_VBAK.ERDAT in my 2nd input field. I think, this clearly indicates binding is done properly.
Please let me know if am wrong and any more clues.
Thanks
Kiran
Hi Kiran,
You have created a node in the context .to which UI element are you binding it..
Is it for table or some input field.
if its for table the cardinality should be 0:N
if its input field it should be 0:1 so that you dont get any errors has context doesny have any elements .
Regards,
Priya
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hello Kiran ,
just change the cardinality of the parent context node in your main view to 0..n
I hope u wud not get the run time error ..
regards,
amit
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Kiran,
Please Check your context binding in your Main View...
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
10 | |
10 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.