Problems with timing issues - WFs CFM starts before DB commits

[Rick Sample]

Nope! But thanks for the attempt.
 
per Stephan Becker reply,
>>You can't do the wait, because the CFM runs in the context of the
caller.
Confirmed. The wait statement in the CFM is in the same context. It
just delays the problem.
 
>>Possible solution: Pass the info you need in the event parameter
container;
>>if it's a SAP standard event you're using, you'd need a modification
(with
>>probably the best reasoning for a modification in a long time), or
you could
>>ask SAP to make the change for you (don't hold your breath *g), or
you could
>>instead raise a custom event in a suitable exit and pass the
information yourself..
 
Here is a few more details.
WF def with type linkage to BO "LIKP Changed" event. Fairly straight
forward.
 
I would think that something is happening in the LIKP obj or linked
obj.
And, the table update is not completing until the " LIKP Changed" event
terminates. ?
 
Details on how-to "Pass the info you need in the event parameter
container;"
I just don't have the experience. Do you have any reference material to
review?
Any examples, links, etc.?
 
 
 
 
>>> skeohan at mit.edu 8/29/2002 12:01:22 PM >>>
Hi Rick,
 
You could try to put in an ABAP statement
 
WAIT up to 60 seconds.
 
That is just one solution.  I am sure our other experts will have
other
solutions.
Sue
 
Rick Sample wrote:
 
> I have a WF with Check Func Mod that starts and completes before my
DB
> is updated.
> My CFM executes a SELECT to examine a field state.
>
> What is the best methodology to delay (set timer?) the CFM to allow
the
> DB commit.
>
> Please be kind. I am a newbie!
> Rick Sample