AW: Workflow condition step returns wrong value

[Quenzer, Kenneth]

Hi Thorsten,
 
I have experience this problem before and it was my understanding that =
it
can occur because most updates to the database are executed =
asynchronously
in an update process on the application server.  Therefore, even if the
event is triggered at the same time that the SQL statement to insert =
the
record is executed the actual update to the database may not have =
occurred.
 
 
Kenny Quenzer
 
-----Original Message-----
From: Dr. Thorsten Wewers [mailto:thorsten.wewers at bmt-consulting.de]
Sent: Thursday, September 28, 2000 11:34 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: AW: AW: Workflow condition step returns wrong value
 
Patrik,
 
if in one SAP application, the event is triggered BEFORE the =
application
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 =
down
drastically. This is ofcourse depending on the type of workflow, the =
number
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 =
with
synchronisation. In some applications the, for example CREATED, event =
is
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 =
works
with
the first solution Sarah suggests since the slowness of the RFC could =
alow
the
database update to finish, but that doesn't seem like a very stabil =
solution
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 =
application
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