dynpro cache problem - how to clear?

[Former Member]

Hi,

I've had this problem before but I don't remember how I solved it. Maybe one of you has an idea.

I'm currently working (again - aargh...) on a 4.0B system. I changed some settings in a table control (3>2 fixed columns, and changed the field order).

I saved and generated the screen, and generated the main program, but when I execute the program, the dynpro still has the old table control.

I deleted all my variants for the table control, exited SAP, logged on again, and still the table control isn't changed...

Is there a program you can use to clear the table control cache like you can clear the alv cache in more recent versions?

thanks,

d.

[Former Member]

I'm intrigued... I still work on a 4.0B system from time to time (and have done for a few years), and I've not seen this problem... when you execute the program, what do you see when you do System > Status and drill into the dynpro - are you seeing your adjusted screen or the old version... and what happens if you add a bit of text or a standard input field on the same screen - do they show normally?

Jonathan

[Former Member]

Jonathan,

any way I open the dynpro (including the way you mentioned, or even just plain testing it in the graphical screenpainter) displays the correct version of the table control.

When I add anything else to the screen, it shows up correctly, but the table control is still wrong.

EDIT: I even tried to turn off 'configurable' for the table control. This made the 'configurable' button disappear, but the actual configuration/layout remained... Weirdness!

Message was edited by:

Rob Smeets

[Former Member]

A little more info - this gets weirder and weirder.

I copied the offending screen 0100 to screen 0900, deleted 0100 and adapted the call for 0100 to 0900.

I generate & test the program in debugging mode.

I see the abap code call for screen 0900, execute the call, and get a short dump complaining that screen 0100 doesn't exist.

WTF?

Someone isn't refreshing his own cache here

Also, when I rename the program to something else, it works correctly. When I then rename it back to its old name, it's broken again...

[Former Member]

Hi Rob,

I am not sure whether it works or not. Did you close your session and execute it again after few min's. Sometimes it would happen that the application server would use the buffer data instead of picking it from the data base.

Thanks,

Sam.

[Former Member]

Now you are making my head ache! Are you able to bounce the server to see if that fixes everything? { The thing I like most about ABAP is that it is predictable... your scenario, especially the 0900 that becomes 0100 is very odd indeed...}

Jonathan

[Former Member]

sam: yes, I've quit and restarted the sapgui.

Jonathan: weird, isn't it... I even asked their Basis guy to clear the buffers, but no dice.

In the end, he decided to stop and start SAP, and even that didn't fix a thing. (mind you, the database itself wasn't restarted, so it might even be a database problem)

I have a workaround in place, which was simply to rename the program (but renaming it back to its original name made it revert to the wrong behaviour). I asked the customer to try and rename the program again in a couple of days, to see if the issue is solved, but I think they'll just keep the program under the new name

R.

[Former Member]

Thanks for the update - I'm at a 4.0B site tomorrow, so if I get a few minutes I'll try to replicate it... but if the stop / start didn't work then it doesn't seem like a buffering problem.

Jonathan

[Former Member]

You probably need to maintain the table control settings (since you made some changes). Click on the 'configuration' button on the right, upper corner.

Go for instance to the the 'administrator' button, make your configuration and save

it. There shouldn't be much of a mystery left I hope.

Let me know if it worked

Vincent

[Former Member]

Won't be going back there in a while... but if and when I do, I'll try this.