AW: Workflow condition step returns wrong value

[Stephan Becker]

Sorry, wrong, events are and should be (but not always are) created in the =
update task because they logically belong to the database update they are t=
riggered from. Have a look at SWE_EVENT_CREATE_IN_UPD_TASK or SWE_EVENT_CRE=
ATE_FOR_UPD_TASK.
Stephan
=20
 
------Original Message------
From: Gregory Kowalik <gkowalik at ashland.com>
To: SAP-WUG at MITVMA.MIT.EDU
Sent: September 28, 2000 6:30:17 PM GMT
Subject: Re: AW: Workflow condition step returns wrong value
 
 
 
 
Thornsten,
 
My 2 cents:
I think you are wrong in your statement,
The update task does only database operations. That what it is responsible =
for.
The event cannot be triggered from within an update task.
So it is physically possible that the event will be raised before the value=
s are
actually written to the disk.
 
Greg
 
 
 
 
 
 
"Quenzer, Kenneth" <QuenzeKD at oge.com> on 09/28/2000 02:13:26 PM
 
Please respond to "SAP Workflow Users' Group" <SAP-WUG at MITVMA.MIT.EDU>
 
To:   SAP-WUG at MITVMA.MIT.EDU
cc:    (bcc: Gregory Kowalik)
Subject:  Re: AW: Workflow condition step returns wrong value
 
 
 
--------------------------------
 
 
Hi Thorsten,
 
I was mistaken in my previous answer.  The problem that I ran into was in a
workflow that executed a task which created a business object and then the
subsequent step attempted to access an attribute of the newly created
business object.  In some cases the step was executed before the database
tables were updated which caused the step to fail.  This sounds like a
different problem than what you are referring to.
 
Kenny Quenzer
 
-----Original Message-----
From: Dr. Thorsten Wewers [mailto:thorsten.wewers at bmt-consulting.de]
Sent: Thursday, September 28, 2000 12:59 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: AW: AW: Workflow condition step returns wrong value
 
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, the
event is "committed" (raised) after the database contents have been
"physically" updated (in update task, right before the event). If it's not
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 b=
e
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 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 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