Problem in ececuting the report when the database table is changed

[Former Member]

Hi,

I am executing a report for delivery creation . But due to overdelivery of items an error message pops up and the program returns to selection screen.

Now if i augment the quantity in database table , and execute from the selection screen again ( not the report ) , the message pops up again.

i checked in debugging, the data in internal tables is not augmented however the database table has been refeshed by that time.

What can be the reason ?

Any suggestions ?

Thanks in advance

vartika

[Former Member]

Don't know which report you are running but it could be local buffering (i.e. within the report or a called function or method there could be an internal tables holding the older version of data) or could be caching in the app server or database... if it is local code, you could try changing the select to include "bypassing buffer".

Jonathan

[Former Member]

Hi ,

It is a Z report that i created.

It is using a standard function module "SHP_GET_SD_DATA"

which is returning the old data.

Can there be buffering within this FM?

How can the problem be avoided.

TIA

Vartika

[Former Member]

Yes, function groups have global memory that can persist until you free it or return to the menu... here's a couple of ideas to solve it... easiest one to try is to re-submit your report via selection-screen which should give you a new "instance" of the function group... you could also have a hunt through the group to see if there is a function module specifically for freeing up the global memory - sometimes there is... you could also have a look at how SAP use the function in case there are some clues there too... it's quite common, though, to want to see the un-refreshed data within a transaction / report until the next time you execute it from a menu.

Jonathan