AW: AW: Workflow condition step returns wrong value

[Dr. Thorsten Wewers]

Hi Kenny,
 
right, therefore the function module that raises the event in update task
must be called as the last thing, i.e. after all the insert, update etc.
statements. Then, with a commit work right after that function module, th=
e
event is "committed" (raised) after the database contents have been
"physically" updated (in update task, right before the event). If it's no=
t
implemented this way by SAP, it's plainly wrong.
 
Please tell me the business objects and events where you encountered such=
 a
problem. My former workflow development colleagues in SAP will definitely=
 be
happy to know about this.
 
Thorsten Wewers
http://www.bmt-consulting.de/
 
-----Urspr=FCngliche Nachricht-----
Von: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU]Im Auftrag von
Quenzer, Kenneth
Gesendet: Donnerstag, 28. September 2000 19:37
An: SAP-WUG at MITVMA.MIT.EDU
Betreff: Re: AW: Workflow condition step returns wrong value
 
 
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 asynchronousl=
y
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 occurre=
d.
 
 
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 a=
nd
saw
alot of RFC's. We changed that to a checkfunction and the load did go dow=
n
drastically. This is ofcourse depending on the type of workflow, the numb=
er
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 wit=
h
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 work=
s
with
the first solution Sarah suggests since the slowness of the RFC could alo=
w
the
database update to finish, but that doesn't seem like a very stabil solut=
ion
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 applicatio=
n
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