Substiution and possible agents

Thu Mar 2 14:36:55 EST 2006

Greg,

Interesting! (SRM is on our radar. Not using yet. 4.6c)

So, the issue would not be auth for t-code. And, does what 
when someone does not have the dollar amount authorization?

If it is covered in this sap-wug I will search when we get to that
bridge. Otherwise, 
a link to the info on this subject? OSS note(s)?

Thanks!

Rick Sample
SAP Workflow Analyst/Developer
Graybar, Inc.

>>> Gregory.Utley at citrix.com 3/2/2006 13:03:09 >>>
Re #2, one of the interesting dilemmas that we have is that our SRM
workflow snakes up through the reports-to chain of the goods-recipient
until an approving agent is found with adequate approval authority for
the dollar amount of the shopping cart.  So authorization is
determined
before the task is executed, not during execution.  This has caused
some
lively discussions re substitutions.  The originally identified
approving agent retains responsibility for selecting an appropriate
substitute.

Greg Utley
Citrix Systems, Inc.
SAP Development Team

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On
Behalf
Of Rick Sample
Sent: Thursday, March 02, 2006 11:58 AM
To: sap-wug at mit.edu 
Subject: RE: Subsitution and possible agents

Baskaran,
Just to expand on this topic...

1. You can sub to anyone. 

2. No authorization checks are made until task is executed. 

3. The substitute may or may not have authorization for all tasks.
Here, you have 
a few options that you implement to ensure WF does not error out
and/or
user does not see 
certain tasks. Like HR WFs. 
You can add "classifications" to the tasks and users can substitute
ALL
tasks or just these 
specific classified tasks. 

If you do not use classifications, you will need to ensure that all
sub'd WFs have auth 
checks (should be done anyway) and do something like display a message
that user 
does not have auth for task. 

Also, two different types of substitutions exists. 
1. Personal substitution. This is via UID and stored in HRUS_D2.
2. Position substitution. HRP1001

Dig around a bit and let me know if you have any more questions. 
There are reasons (which may not be readily apparent) why we have 
different types. 

rick

>>> jocelyn.dart at sap.com 3/1/2006 23:57:02 >>>
Hi Baskaran, 
Yes that is correct functionality.  If you were expecting something
different then you haven't understood the substitution process
correctly.
The point of substitution is to allow someone to receive a work item
on
behalf of the original recipient - so effectively they are an
"implicit"
possible agent by their relationship to the original recipient.  

Forwarding is of course a completely separate issue - as then the
recipient receives the work item on their own behalf, not on behalf of

someone else. 

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 Baskaran Aluru
Sent: Thursday, 02 March 2006 2:07 PM
To: SAP Workflow Users' Group
Subject: Subsitution and possible agents

Hi Everyone,
We have an issue in 4.7 with substitution.  A substitute agent is able
to execute the workitem even though they do not belong to the possible
agents list.  No errors or warnings.  Task has "Forwarding not
allowed"
set, possible agents come from a Role, and the substitute is not
assigned to that Role.

Is this an authorization issue?  Any clues would be appreciated.

TIA,
Baskaran.

_______________________________________________
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 