AW: AW: Workflow condition step returns wrong value

[Patrik vanOdijk]

Thorsten,
 
In our case it was parking of an invoice and we used object FIPP. I agree that
it would be nice if this really was an error, but as I remember it the database
update was made before the triggering of the event as an asynchronous update. If
the system is a bit slow this will be delayed enough for the event to be
triggered before the actual update has finished. This would apply both to a
check function and a WF step that accesses an attribute directly after a
creation step.
 
I don't know how to go around this without a synchronous call.
 
/Patrik
 
 
 
 
"Dr. Thorsten Wewers" <thorsten.wewers at bmt-consulting.de> on 2000-09-28 17:33:47
 
Please respond to "SAP Workflow Users' Group" <SAP-WUG at MITVMA.MIT.EDU>
 
To:   SAP-WUG at MITVMA.MIT.EDU
cc:    (bcc: Patrik van Odijk/GBG/FRONTEC)
 
Subject:  AW: AW: Workflow condition step returns wrong value
 
 
 
-------------- next part --------------
Patrik,
 
if in one SAP application, the event is triggered BEFORE the applicatio=
n
data are written on the database, this is worth an OSS message to SAP. =
It
mustn't occur.
 
Could you tell me which business object and method you're talking about=
?
 
Cheers,
 
Thorsten
 
-----Urspr=FCngliche Nachricht-----
Von: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU]Im Auftrag von
Patrik vanOdijk
Gesendet: Donnerstag, 28. September 2000 17:54
An: SAP-WUG at MITVMA.MIT.EDU
Betreff: Re: AW: Workflow condition step returns wrong value
 
 
 
 
Thorsten, Sarah.
 
I agree with what you say Thorsten. We did the workflow branch solution=
 and
saw
alot of RFC's. We changed that to a checkfunction and the load did go d=
own
drastically. This is ofcourse depending on the type of workflow, the nu=
mber
of
flows started and the percentage of flows that are terminated ofcourse.=
 
 
One issue that also needs to be adressed concerning this is a problem w=
ith
synchronisation. In some applications the, for example CREATED, event i=
s
triggered before the database update has been done. This means that the=
 
access
to the object is not succesful in the check function. Sometimes this wo=
rks
with
the first solution Sarah suggests since the slowness of the RFC could a=
low
the
database update to finish, but that doesn't seem like a very stabil sol=
ution
really.
 
We had to build an exit for one application to check a status for one
created
object and skip the triggering of the created event within the applicat=
ion
instead of with the check function just of the above described problem.=
 
 
Whats your opinion on this?
 
/Patrik
 
 
 
 
"Dr. Thorsten Wewers" <thorsten.wewers at bmt-consulting.de> on 2000-09-28=
 
16:34:10
 
Please respond to "SAP Workflow Users' Group" <SAP-WUG at MITVMA.MIT.EDU>
 
To:   SAP-WUG at MITVMA.MIT.EDU
cc:    (bcc: Patrik van Odijk/GBG/FRONTEC)
 
Subject:  AW: Workflow condition step returns wrong value
 
 
 
 
=