Workflow Substitution Report

Mon Sep 12 18:12:24 EDT 2005

First of all, I just wanted to thank everyone for the replies.  The
information was extremely helpful.

- Given 90% of our user base, if something isn't workflow enabled it
doesn't get done.  Users venturing out to the application to do it
without workflow is not an issue.  But, I understand the concerns
voiced.

- DBTABLOG was mentioned as a table to view.  This is great information
that I was not aware of and will help us is in resolving issues.
However, our main issue is that we have an administrator performing
transactions for4-5 managers and there is really no accurate record of
whom the original recipient for a workitem was.  

- Jocelyn Dart's email about the _RULE_RESULT container element was
exactly what I was looking for.  The fact that is available 6.20 and
above helps further as I continue to beat the drum about need for an
upgrade (still on 4.5b).

Thanks again...

Bob

  _____  

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Trant, David
Sent: Friday, September 09, 2005 9:05 AM
To: SAP Workflow Users' Group
Subject: RE: Workflow Substitution Report

Thanks, Jocelyn.  I missed the BW announcement - that's good news.
Though it will unfortunately be quite a while before we upgrade from
4.6C, it helps to know the direction SAP is taking so we can try to
design today's new workflows now based on it.  It's good to know that
more detailed information will be available in future logs, and just as
important that we'll be able to offload that information onto BW.  That
should help the performance issues we have today due to huge table
sizes, and make my Basis colleagues much happier in the process.

Thanks again,
David

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]On Behalf
Of Dart, Jocelyn
Sent: Friday, September 09, 2005 1:52 AM
To: SAP Workflow Users' Group
Subject: RE: Workflow Substitution Report

Bob, 
I think the comments from everybody are spot on and very useful.  

Of course we do have BW capability coming for Workflow as Alan Rickayzen
announced a few weeks ago.   

The workflow log does give a process history of who did what / who made
the decisions along the way to getting the update and this can be
valuable data in addition to the change history of the application
itself.   There may be several people involved in the decision process
regardless of who made the final update to the application.  And of
course whether workflow was used or not to affect the update is useful
information in itself. As we move up the releases the workflow log is
showing increasingly more specific information - e.g. current logs show
whether an item was forwarded by a user or by the workflow
administrator. 

Regarding the ability to see if someone has acted as a substitute - a
lot depends on your release.  If you are in a system running on a basis
6.20 or above (such as R/3 Enterprise), then you may be able to use the
_RULE_RESULT container element to compare the actual agent with who was
originally sent the work item. 

If you are in a lower release things the _RULE_RESULT element is not
available, and yes you will need to rely heavily on table HRUS_D2
providing you make sure no-one deletes the old entries (i.e. they should
just set an end date, not delete the substitution). 

Regards, 
Jocelyn Dart 
Senior Consultant 
SAP Australia Pty Ltd. 
Level 1/168 Walker St. 
North Sydney 
NSW, 2060 
Australia 
T   +61 412 390 267 
M   + 61 412 390 267 
E   jocelyn.dart at sap.com 
http://www.sap.com <http://www.sap.com/>  
The information contained in or attached to this electronic transmission
is confidential and may be legally privileged. It is intended only for
the person or entity to which it is addressed. If you are not the
intended recipient, you are hereby notified that any distribution,
copying, review, retransmission, dissemination or other use of this
electronic transmission or the information contained in it is strictly
prohibited. If you have received this electronic transmission in error,
please immediately contact the sender to arrange for the return of the
original documents. 
Electronic transmission cannot be guaranteed to be secure and
accordingly, the sender does not accept liability for any such data
corruption, interception, unauthorized amendment, viruses, delays or the
consequences thereof.
Any views expressed in this electronic transmission are those of the
individual sender, except where the message states otherwise and the
sender is authorized to state them to be the views of SAP AG or any of
its subsidiaries. SAP AG, its subsidiaries, and their directors,
officers and employees make no representation nor accept any liability
for the accuracy or completeness of the views or information contained
herein. Please be aware that the furnishing of any pricing information/
business proposal herein is indicative only, is subject to change and
shall not be construed as an offer or as constituting a binding
agreement on the part of SAP AG or any of its subsidiaries to enter into
any relationship, unless otherwise expressly stated. 

  _____  

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Schmidt, Bob
Sent: Friday, 09 September 2005 3:00 AM
To: sap-wug at mit.edu
Subject: Workflow Substitution Report
We are allowing users to create substitution rules in their workflow
inboxes usually a manager delegating to their admin. The issue we are
having is that auditors are requesting a report of workitems processed
by each user and additionally if a substitution rule was involved and
whom it was performed on behalf of.

Has anyone encountered similar requirements and how was it satisfied?

Regards,
Bob Schmidt 

------------------------------------------------------------------------
------------------------
This message is for the designated recipient only and may
contain privileged, proprietary, or otherwise private information. 
If you have received it in error, please notify the sender
immediately and delete the original. Any unauthorized use of
this email is prohibited.
------------------------------------------------------------------------
------------------------
[mf2] 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20050912/e7fe5c55/attachment.htm