Statistics on wait times? - Loops and New Tasks

Thu Aug 2 09:30:15 EDT 2007

John White,

Clear as mud? 

Keep monitoring this list. Many helpful folks here. 
I just learned some new stuff (for me anyway) per Mike Pokraka yesterday
on deadline monitoring. 
I don't use them much, so a nudge in the right direction was very
helpful.

If you need more, just ask...

Rick Sample
SAP Business Workflow Developer
Graybar, Inc.

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Yulianto
Sent: Wednesday, August 01, 2007 7:52 PM
To: 'SAP Workflow Users' Group'
Subject: RE: Statistics on wait times? - Loops and New Tasks

To make sure that the user actually did what he/she had to do (for
example, editing something), then a better way to do it is to create an
asynchronous task (to execute an asynchronous method) wherein you have
to put the terminating event to that asynchronous task. This terminating
event will tell the workflow system to complete the current work item.
So, unless the terminating event is received, the work item will remain
in the user's inbox forever, until he/she actually does what he has to
do.
But the problem is (as always), how to trigger that terminating event
when the user has done his job (for example, changing or approving
something).
Then you might be interested in examining whether your document has a
status management, or change document, or final solution is to utilize
user exit to explicitly call function module to trigger event.

Regards,

Yulianto Abu Muhammad

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of John White
Sent: Thursday, 2 August, 2007 3:07 AM
To: SAP Workflow Users' Group
Subject: RE: Statistics on wait times? - Loops and New Tasks

Rick,

You mentioned that when you were a workflow 'newbie', you created loops
that created a new task every loop.

I'm definitely a workflow newbie, and have created edit loops to verify
that the user actually did what they were suppose to. Is there a better
way? 

I would appreciate further any further enlightenment. 

Thanks,

John White
Sauder Woodworking, Inc.

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Sample, Rick
Sent: Wednesday, August 01, 2007 11:31 AM
To: SAP Workflow Users' Group
Subject: RE: Statistics on wait times?

Alan,

We had basically same request. A sort of Manager's report on their
subordinates work.
One issues that will effect WF duration reports:

Duration. Duration of what? 
Some of my older WFs (when I was a newbie) have loops that create a
"new" task every loop. 
I clean up as needed when I revisit these older WFs, but none the less,
they could skew your reports.
i.e. user opens a task, closes, and the loop creates a new task. So,
duration of this task would be meaningless.
I know no one has never done this before. Right? 

Our solution was to add a struct to all WFs with the tasks we want to
report on. Pull that info into BW and slice and dice any way business
wants. 

Worked for us. 
But I would be really interested in your findings since you have
defected to Duet group vs. WF world!  :-)

Rick Sample
SAP Business Workflow Developer
Graybar, Inc.

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Rickayzen, Alan
Sent: Wednesday, August 01, 2007 9:19 AM
To: SAP Workflow Users' Group
Subject: Statistics on wait times?

Dear workflow experts,

I'm hoping to gather some statistics on workflow performance - in
particular wait times (i.e. wasted time - time a work item spends before
someone works on it).
In particular - I'm looking to see how e-mail notifications affect
things.

Why? Duet supports SAP Business Workflow and I'm confident we'll
eventually be able to show how much advantage there is in, say, doing
offline approvals compared with simple notifications compared with no
e-mail support at all.

Here's the request to workflow administrators - if you're not one,
sorry, you won't have the authorization or expertise and can stop
reading here :-)

IMPORTANT: Don't do this today. Wait until next week to give anyone a
chance to raises concerns about risks involved just in case there are
any that my colleagues and I have overlooked.

------------------------------

To create the statistics, you simply call transaction SWI2_DURA in a
production system and select the last-365-days interval.
The task ID is TS00008267 (or equivalent) and press F8. This does not
make changes in the system - it simply reads the data.

Irrespective of what mail system you use, I'm hoping to receive

1. Threshold values shown by the report (10%, 50%, 90%) and the average
values (wait, process, total). Just cut and paste these from the report
results.

2. Whether or not you send e-mail notifications, or even e-mail-based
approvals as in SRM.

3. What mail client you use.

4. Whether you have enhanced the standard SAP notification capabilities
(Kjetil did with great success). 

5. Process name  if possible (e.g. shopping cart approval). I guess this
is only possible if you copied TS8267 to your own custom task for one
particular process to configure a useful task description and do proper
reporting (Massive kudos for doing this - triple-kudos for anyone doing
this sort of reporting in BI).

Address to return results to: 
       alan.rickayzen at sap.com

------------------

I'll circulate the statistical results (without the company or personal
names) to Sue (our workflow Goddess) and those of you generous enough
with your time to participate. Maybe we can improve the questions later
for a proper web survey for ASUG or some other event.

Best regards,

Alan  Rickayzen
SAP AG 

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

This e-mail and any files transmitted with it may contain privileged,
confidential, or proprietary information which may be protected from
disclosure under law, and is intended solely for the use of the
individual, group, or entity to whom this e-mail is addressed.  If you
are not one of the named recipients, please notify the sender by e-mail
and delete this message immediately from your computer.  Any other use,
retention, dissemination, forwarding, printing, or copying of this
e-mail is strictly prohibited.  Thank you for your assistance.

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug