Workflow Timing

[Francois Beaubien]

Hello,
=20
I have use the enqueue function in situation like this to validate that =
the
LUW is completed. The lock object is release (dequeue) after the V1
functions are completed. Be aware that the change documents are =
probably
inserted with a V2 function module.=20
=20
You could call the EVVBAKE enqueue function in a loop until the order =
is
save and add a delay for the V2 function to complete.=20
=20
You can see the lock entries in SM12 and the update module in SM13 (you =
must
set the "update debugging" setting in the debugger to see them).=20
=20
To be 100% certain, you must query the VBHDR table to confirm that all
update function modules are completed.=20
 
Fran=E7ois Beaubien, ing.=20
 
 
-----Message d'origine-----
De : Czerwiec, Phil [mailto:Phil.Czerwiec at andrew.com]=20
Envoy=E9 : lundi 18 mars 2002 11:26
=C0 : SAP-WUG at MITVMA.MIT.EDU
Objet : Workflow Timing
 
 
 
We have several workflows that are triggered on the event of the Sales =
Order
Change.  One of the sub-workflows that is triggered by this event is to
check the document change log (tables CDHDR & CDPOS).  Occasionally, =
there
seems to be a timing problem.  It appears that the document change log =
is
read before the tables have been updated.  We are using the SAP =
supplied
function module 'CHANGEDOCUMENT_READ_WITHOUT_ED' to identified which =
type of
change was made.  How can we ensure that the document change log has =
been
updated before it is read?    =20
 
Phil Czerwiec=20
Andrew Corporation=20
P - (708) 873-2223=20
C - (708) 218-3120=20
 
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20020319/7978ea46/attachment.htm