AW: AW: Workflow condition step returns wrong value

[Stephan Becker]

Hi there,
 
I had this conversation with SAP about a timing issue in BSEG_MMIV about tw=
o years back, and after a lot of going back and forth (in all fairness, onc=
e we were talking to the guys in Walldorf in the Process Technology group a=
nd in development, it went very quickly), they changed the call to the even=
t creation module from the end of the dialog task (if I remember correctly)=
 to the end of the update task. That did it for us, and we were creating of=
ten hundreds of workflows within one minute (large invoices creating multip=
le line item workflows), and all of that in connection with a check functio=
n module..
 
Having just implemented a large parked document workflow, we have just yest=
erday encountered some of the same kind of problem: in the production syste=
m the update was quicker than in the other systems we had tested, and sudde=
nly the database update of the change of a parked document (and thus the ev=
ent creation for the FIPP CHANGED event) was overtaking the workflow proces=
sing, and we were losing some data (an agent) in the workflow because worki=
tems got cancelled through a wait event before they were finished.. in our =
case, it was a problem in the modelling (we shouldn't have relied on any da=
ta being processed after calling the change method because we knew we had a=
 wait event that would cancel the main processing), and we could get around=
 it by getting the required data (person changing the document) from the ev=
ent parameter container..
 
Stephan
 
 
------Original Message------
From: Patrik vanOdijk <patrik.van.odijk at gbg.frontec.se>
To: SAP-WUG at MITVMA.MIT.EDU
Sent: September 29, 2000 6:03:11 AM GMT
Subject: Re: AW: AW: Workflow condition step returns wrong value
 
 
 
 
Thorsten,
 
In our case it was parking of an invoice and we used object FIPP. I agree t=
hat
it would be nice if this really was an error, but as I remember it the data=
base
update was made before the triggering of the event as an asynchronous updat=
e. 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
 
 
 
--------------------------------
 
 
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 solutio=
n
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
 
______________________________________________
FREE Personalized Email at Mail.com
Sign up at http://www.mail.com/?sr=3Dsignup