OBJECTS_OBJREF_NOT_ASSIGNED error on selection

[Former Member]

Hi Experts,

I am getting crazy trying to figure out whats going on here. I have a Webdynpro screen for creating purchase requisitions and it has been showing a OBJECTS_OBJREF_NOT_ASSIGNED runtime error to the test user when he selects a value on a RadioButtonGroupByIndex control. I was able to see the error only twice and I have been trying all day to reproduce it with no luck. The onSelect event of my control is binded to a dummy action that does nothing but a round trip to the server, this is to update some values of a node (with supply function) that gets invalidated from the view's WDDOMODIFYVIEW everytime.

The short dump doesn't show any of my code, its all standard calls from the HTTP request until it gets to CL_WDR_CONTEXT_ELEMENT=>IF_WD_CONTEXT_ELEMENT~GET_ATTRIBUTE_REF line 24:

attr_info = me->node_info->if_wd_context_node_info~get_attribute( name_only ).

This is crashing because for some strange reason me->node_info comes null, and the most weird thing is that the attribute info that its trying to get is from a VENDOR field of other node that has nothing to do with the invalidated node, and the active calls doesn't even get me to the invalidate function.

I know its almost impossible that someone can solve my problem only with this data since its a complex and weird thing but maybe if God exists someone here has experimented something similar and can bring some light to me pleaseeeee

Thanks all!

[Lukas_Weigelt · Accepted solution]

Maybe you defined some node/attribute with a kardinality 0...n or the like and in some cases you try to access this node/attribute via lead selection and it's initial..... other than guessing it's hard to help here indeed :-///

[Former Member]

Hi ,

Seems to me that the node is initial as already suggested by Lucas.You can change the cardinality to 1..1 or 1..n

[Former Member]

Hi Lukas and Baskaran, thanks for your answers.

The attribute VENDOR is from a node (0..N) binded to a table, but I initialize the table with 100 lines on the component controller WDDOINIT. Additional to that, I cant reproduce the error, it happened to me only twice yesterday and I have been trying to see it again since then (no luck). My test user gets the error a lot more often and I dont know why.

Thanks for the answers and I will be posting my findings (if any)

Regards

Daniel

[Former Member]

I found it!

With a lot of help of the test user, he found the sequence to reproduce the error.

The problem was the method

cl_wdr_value_help_handler=>handle_value_help

that I use to show the value help dialog and this was causing the problems, the error came up only when this method was executed without the import parameter VIEW, which is optional, and be careful because it actually works without it.

SAP doesn't support this class for customer development since its a CL_WDR* (internal use only) but it seems the execution without the parameter VIEW leave the application on an inconsistent state, and this was causing the problem.

Hope someone finds this useful.

Regards

Daniel

[Former Member]

Hi Daniel!

Yes, we found this Post very useful, because we were having the same Short Dump!!!

In our case, we were trying to develop a custom Search Help, that was called by the press button User-Event. For that, we were invoking "cl_wdr_value_help_handler=>handle_value_help".

At first, everything seemed to work fine..., but when the WD popup screen got closed, we got the same Short Dump as you were describing in your post!

So for us, the solution was also the same: Inform the Optional VIEW parameter into the method call.

Regards!

Carles