SALV_WD_TABLE refresh problem

[Former Member]

Hi Experts,

right now we're patching our Neweaver 7.0 System from SP14 to SP16 and my Web Dynpros are not running correctly anymore. I'm using the SALV_WD_TABLE Component for several occasions and it seems, that it's not getting its data correctly anymore.

I've bound a contextnode (cardinality 0..n) to the DATA contextnode of the SALV_WD_TABLE via interfacecontroller_usage.

What happens now is, that the first time, I put some data into the contextnode, everything is fine and the data is shown in the SALV_WD_TABLE. The next time and every following try, the SALV_WD_TABLE more or less keeps the old data. There's also some weird behavior when scrolling the table. sometimes it also mixes up old an new data.

I've checked the context. It's filled correctly. It's just the display. I also tried DATA_CHECK and REFRESH on the SALV_WD_TABLE-Interface with no result at all. Before SP16 it all worked quiet well. I'm kind of lost...

Regards

Torsten

[Former Member · Accepted solution]

Hi Torsten

Check the following thread, it has some note numbers mentioned, check if they are implemented in your system

Regards

Manas Dua

[Former Member · Accepted solution]

Hi Experts,

thanks for your quick answers.

Manas, your link refers to a thread that describes exactly the same problem as mine. Unfortunatly it does not tell how to solve it. The mentioned notes are not for the problem at hand. The Questioner only says, that he has fixed the problem by himself. That's something I really hate.

Thomas, the context is usually filled after a button action from another view. I've checked the context in the WDDOMODIFYVIEW of the target view and it is filled as it meant to be.

I also haven't found anything useful in the notes. That's why I was asking here . I guess you're right and I have to open a ticket.

Regards

Torsten

[Former Member · Accepted solution]

Hi Torsten,

Yeah in the note 1319829 , the description of problem is somewhat different, but it solves your mentioned problem.

Even we encountered the same problem during development and were provided with same notes from ALV colleagues.

Just try implementing the note or the relevant SP.

[Former Member · Accepted solution]

All right! That's worth a try. I will report the results

[Former Member · Accepted solution]

Yes, it worked! Manas, many thanks to you. In fact we've used note 1390681 which includes 1319829. My mistake was, that we have an overall SP level of 16, but our basis component is at 19. It's somewhat confusing. So I guess I was looking for the wrong notes

Regards

Torsten

[thomas_jung]

If the applications were working fine before the SP, then you should consider opening a support ticket. Try and recreate the problem in one of the ALV SAP-Supplied Sample Applications. That will speed up the troubleshooting time from the SAP side as it will prove the problem is on the SAP side. Also when are you filling the data in your component. Make sure you aren't filling the data in the WDDOMODIFYVIEW or some other action that might be triggered more than once. Set a breakpoint in the method that fills the context to make sure.

I searched the notes database and I didn't find anything in BC-WD_ABA or BC-SRV-ALV or BC_WD-CMP-ALV-ABA that really matched your description for SP16 - but I only did a quick scan.