User Substitutions within EBP

Dart, Jocelyn jocelyn.dart at sap.com
Tue Aug 27 03:44:51 EDT 2002


Yes Michael,
You are correct - as EBP always retrieves users within the ad hoc objects
then agent determination is always to the user and hence substitution must
always be to the user. Position based substitution won't work here.
 
Don't forget that the "change approver" function can also be used for
proactive substitution.  However if you want to set up substitution in
advance then you will need to use workflow substitution.
 
By the way, the workflow substitution buttons in the BBP web inbox are
strictly for HRUS_D2 substitutions anyway.
 
Regards,
        Jocelyn Dart
Consultant (SRM, EBP, Workflow)
and co-author of the book
"Practical Workflow for SAP"
SAP Australia
email: jocelyn.dart at sap.com
phone: +61 412 390 267
fax:   +61 2 9935 4880
 
 
 
 
-----Original Message-----
From: Michael Arter [mailto:Michael_Arter at national.com.au]
Sent: Monday, 26 August 2002 5:42 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: User Substitutions within EBP
 
 
Hi,
We are planning to use substitution logic within our EBP system.  We have
come to a consensus that we need to do this
via the personal substitution relationship that utilises the table HRUS_D2
which creates a user to user substitution.
 
The main reason for this is that the adhoc agent object needs to be a
userid as opposed to say a position for the contact
details to display correctly in the java applet.  Given that the agent is a
userid I don't believe position based substitutions
are going to work - eg. the A210 relationship.
 
I would be interested to know how others have addressed this issue within
EBP.
 
NB:  We are also using substitution functionality within our backend system
but this will be position based substitutions where the
role resolution object will be a postion as opposed to a userid.
 
 
Regards,
Michael Arter
 
IBM GSA.
__________________________________________________________________________
The information contained in this email communication may be confidential.
You
should only read, disclose, re-transmit, copy, distribute, act in reliance
on or
commercialise the information if you are authorised to do so. If you are
not the
intended recipient of this email communication, please notify us
immediately by
email to NABpost at national.com.au or reply by email direct to the sender
and then destroy any electronic or paper copy of this message.  Any views
expressed in this email communication are those of the individual sender,
except
where the sender specifically states them to be the views of a member of
the
National Australia Bank Group of companies.  The National Australia Bank
Group
of companies does not represent, warrant or guarantee that the integrity of
this
communication has been maintained nor that the communication is free of
errors,
virus or interference.
 


More information about the SAP-WUG mailing list