Substitution and possible agents
Nat 4 Govender
ngovender4 at toyota.co.za
Fri Mar 3 02:08:06 EST 2006
Hi All,
Just to add to the subject.
Our substitution process operates in the following manner
1. Substitution workflow is triggered on creation of an absence
record.
2. If absence is in the past the workflow or person that will be
absence (Appointee) does not have an active SAP login the workflow will
end.
3. Workflow goes the Appointee with the following options
3.1 Select A Substitute
3.2 No Substitute Required
4. The workflow is then routed to the Appointee's superior to will
the following options
4.1 Approve Substitute Selected
4.2 Choose Another substitute
4.3 No Substitute Required
5. If option 4.3 is selected the workflow will end.
6. if 4.1 or 4.2 is selected the workflow will then perform the
following
6.1 Compare the profiles of the Appointee and the Substitute
and create composite profile consisting only difference
This composite profile has the conforms to the naming
convention of Z:"USER LOGIN", e.g. Z:DNAT
6.2 This profile is then linked to the Substitute for the
period on absence.
7. Profile is remove on the following conditions
7.1 Substitution period ends
7.2 Deletion of Absence
7.3 Substitute is changed.
Regards
Nat Govender
Toyota South Africa
IT - SAP Workflow Specialist
Internal Ext. : 32645
Direct Line : +27 031 910 2645
Fax : +27 031 902 9633
E-mail : ngovender4 at toyota.co.za
==================================================================
Forgiveness is when one relinquishes the option to hurt the person that
hurt you.
Remember not to forget that which you do not need to know.
==================================================================
"Rick Sample"
<Rick.Sample at gbe.
com> To
Sent by: sap-wug at mit.edu
sap-wug-bounces at m cc
it.edu
Subject
RE: Subsitution and possible agents
2006/03/02 06:57
PM
Please respond to
"SAP Workflow
Users' Group"
<sap-wug at mit.edu>
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
This message is a privileged and private communication and may be read, copied and used only by
the intended recipient(s). If you are not an intended recipient, please let us know by return email.
Please then delete the message and do not disclose its contents to any person. Neither the sender nor
Toyota South Africa Motors accepts any liability whatsoever as a result of the further dissemination
of this message. Whilst all reasonable steps are taken to avoid corruption of data or information,
we do not accept any liability should such corruption occur.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20060303/2b890508/attachment.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20060303/2b890508/attachment.gif
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pic01339.gif
Type: image/gif
Size: 1255 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20060303/2b890508/attachment-0001.gif
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ecblank.gif
Type: image/gif
Size: 45 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20060303/2b890508/attachment-0002.gif
More information about the SAP-WUG
mailing list