Issue when Enhancing a view/context binding

[Former Member]

Hi

I'm enhancing an eRecruitment view for HRRCF_C_SEARCH_UI by adding a new column to an existing table.

I have created the UI element and a new attribute in the appropriate context node of the view. The column contains a textview and the text property is mapped to the context_node attribute.

However at runtime an error occurs with the following.The URL http://fcrsapderecfs.app.netr.kent.police.uk:8000/sap/bc/webdynpro/sap/hrrcf_a_unreg_job_search/ was not called due to an error

"ASSERTION_FAILED" " "

"CL_WDR_VIEW_ELEMENT_ADAPTER===CP" or "CL_WDR_VIEW_ELEMENT_ADAPTER===CM008"

"GET_BOUND_ELEMENT"

Termination occurred in the ABAP program "CL_WDR_VIEW_ELEMENT_ADAPTER===CP" -

in "GET_BOUND_ELEMENT".

The main program was "SAPMHTTP ".

In the source code you have the termination point in line 76

of the (Include) program "CL_WDR_VIEW_ELEMENT_ADAPTER===CM008".

I've tried debugging and used the usual resources but so far I've not uncovered the problem.

All suggestions gratefully accepted. Thanks in advance.

Jon

[ramakrishnappa · Accepted solution]

Hi Jon,

It looks like, the issue is with binding of context attribute with ui element or the cardinality settings of node.

I suggest you to look at this program CL_WDR_VIEW_ELEMENT_ADAPTER===CM008 and set the break point at line 76.

Use the call stack to determine from where the dump is triggering. I mean use STANDARD tab in debugging window and trace back till you the column name/ui element.

Try to re-do the binding of ui element to context attribute.

Could you share the screen shots of your view layout and context node, to investigate it further.

Regards,

Rama

[Former Member · Accepted solution]

Hi Rama

Thanks for such a swift response.

Here is the view layout.

And the context of the view

Can you give me a further pointer on how to debug that program please. I've set a breakpoint but how do I then interrogate the debugging window?

Thanks again

Jon.

[ramakrishnappa · Accepted solution]

Hi Jon,

Thanks for sharing the snap shots. The enhancements done look good.

To debug, please follow the below steps

Go to t-code ST22 and find out your short dump ( Run time error)  record on your name
Open the record and now you can see the run time error data
On top , please click on "ABAP_EDITOR" button and it takes you to the location where the exception is thrown
Now Please the "external break point"
Run your application ( as you do normally )
Now, debugger takes you to the point
Use "STANDARD" tab in debugging window
Follow the call stack to trace back till you find the place where its been originated.

Hope this helps you.

Regards,

Rama

[Former Member · Accepted solution]

Thanks again Rama

I still think I'm missing something! when you say 'Run your application ( as you do normally )' what exactly do you mean that? At present I'm using a URL on my Intranet which runs http://....sap/bc/webdynpro/sap/hrrcf_a_unreg_job_search?sap-wd-configId=ZUNREG_JOB_SEARCH&sap-ep-th... and loads the relevant page in a browser window.

If I set a breakpoint as you directed and use that URL it's not going into the debugger. Should I be running it from the Web Dynpro Explorer and if so how is that done?

Apologies if this seems obvious but it's not to me! Yet!!

Jon.

[ramakrishnappa · Accepted solution]

Hi Jon,

You can run application by using its URL or through se80 ( WD explorer ).

Please set the external break point as below

Now external debugging point has been set for the user "RAMAK".

Hope this helps you.

Regards,

Rama

[Former Member · Accepted solution]

That's brilliant Rama.

I've got the breakpoint set and working now. I hadn't selected the relevant Web Dynpro Application in the component when I was trying to debug in SE80.

I've now got the trace and hopefully will be a step closer to understanding what the error is.

In the debugger can you follow the attributes associated with the UI element and it's context node?

Thanks again.

Jon.

[ramakrishnappa · Accepted solution]

Hi Jon,

Yes, we can trace back to find out the context node and its data. Get into the method of component controller or view controller.

Use WD_CONTEXT / WD_THIS object to know all the available context data.

Regards,

Rama

[Former Member · Accepted solution]

Hi Rama

After several hours of debugging I've not been able to track down the issue. All the data and the context node is as I would expect.

I decided to remove my enhancement and all the changes and revert HRRCF_C_SEARCH_UI to it's original state. Doing this has not made a difference and I am still getting the same error as I originally got when I enhanced the view!

Is is possible for a web dynpro to be corrupted in some way?

Cheers

Jon.

[Former Member]

HI

No matter what we tried we could not sort this issue. It appeared that the component was corrupted in some way. By comparing it to the instance in QAS we could see the datasource for the table binding was incorrect but could not be altered or edited in our DEV system. It may have been something to do with a previous enhancement but very hard to tell

In order to expedite matters a copy of the QAS version was restored to DEV. In that way the component was a known working version and we could make the changes to it as necessary. Not an ideal solution.

Thanks for all you help.

Jon.