Buffer Refresh

[Zmudzin,Tomasz,VEVEY,GL-IS/IT]

This is an update timing issue -- the "Before" method probably does an
asynchronous update, so when the main method is started it still picks =
the
old data (just before the new one is fully posted...). To fix this (in =
the
simplest dirty way) you can try
 
1. making the "Before" method synchronous
2. ...and updating the DB via "COMMIT WORK AND WAIT" instead of a =
simple
COMMIT
 
To have a proper fix please check for the documentation on DB updates =
(ABAP
reference manual) and asynchronous methods (Workflow reference manual) =
on
help.sap.com.
 
Kind regards,
Tomasz
 
 
-----Original Message-----
From: Falk, Simone [mailto:SIMONE.FALK at airbus.com]
Sent: Wednesday,21. May 2003 15:16
To: SAP-WUG at MITVMA.MIT.EDU
Subject: AW: Buffer Refresh
 
 
Thanks Marek !
 
OK that worked but unfortunately it did not resove my problem:
 
I have a task with one before method. That method changes the status of =
my
object ( QM-TASK) to 'RELEASED' in background.=20
The main method calls QM02 (Dialog) and I still see status Task =
outstanding
so the before method did not work.
 
Is it a synchronization Problem ?
 
Best Regards
Simone
 
 
 
-----Urspr=FCngliche Nachricht-----
Von: Marek Dziewulski [mailto:marek.dziewulski at polkomtel.com.pl]
Gesendet: Mittwoch, 21. Mai 2003 14:31
An: SAP-WUG at MITVMA.MIT.EDU
Betreff: Re: Buffer Refresh
 
 
call funcion module:
rh_wf_om_indices_timestamp_rfs
 
regards
 
marek
 
-----Original Message-----
From: Falk, Simone [mailto:SIMONE.FALK at airbus.com]
Sent: Wednesday, May 21, 2003 2:27 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Buffer Refresh
 
 
Dear all
how can I refresh th WF Buffer in 4.5B ?
In 4.6 it is SWU_OBUF.
 
Thanx Simone
 
This mail has originated outside your organization,
either from an external partner or the Global Internet.=20
Keep this in mind if you answer this message.