<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2800.1522" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=050382023-10112005><FONT face=Arial
color=#0000ff size=2>Re assigning approvers at the split account assignment
level - its not intended for this and SAP AG don't guarantee it will work.
</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=050382023-10112005><FONT face=Arial
color=#0000ff size=2>However I have played around with it and it did seem to be
possible - certainly the "everyone approves" scenario worked fine -
but we were not able to complete testing of this functionality and did not go
live with it. </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=050382023-10112005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=050382023-10112005><FONT face=Arial
color=#0000ff size=2>You can copy and modify the item-based workflows - but you
have to know what you are doing. Go very gently. </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=050382023-10112005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=050382023-10112005><FONT face=Arial color=#0000ff size=2>You
are absolutely required to use an ad hoc agent object based on AAGENT *unless*
you are using the BADI workflows - if you don't you will lose some significant
parts of the approval preview/approval tab displays. You can call
your function module or an object attribute from the Create method of your ad
hoc agent object. </FONT></SPAN></DIV><!-- Converted from text/rtf format -->
<P><SPAN lang=en-us><FONT face=Arial size=1>Regards,</FONT></SPAN> <BR><SPAN
lang=en-us><B><FONT face=Arial color=#000080 size=1>Jocelyn
Dart</FONT></B></SPAN> <BR><SPAN lang=en-us><FONT face=Arial color=#808080
size=1>Senior Consultant</FONT></SPAN> <BR><SPAN lang=en-us><B><FONT face=Arial
color=#808080 size=1>SAP Australia Pty Ltd.</FONT></B></SPAN> <BR><SPAN
lang=en-us><FONT face=Arial color=#808080 size=1>Level 1/168 Walker
St.</FONT></SPAN> <BR><SPAN lang=en-us><FONT face=Arial color=#808080
size=1>North Sydney </FONT></SPAN><BR><SPAN lang=en-us><FONT face=Arial
color=#808080 size=1>NSW, 2060</FONT></SPAN> <BR><SPAN lang=en-us><FONT
face=Arial color=#808080 size=1>Australia</FONT></SPAN> <BR><SPAN
lang=en-us><FONT face=Arial color=#808080 size=1>T +61 412 390
267</FONT></SPAN> <BR><SPAN lang=en-us><FONT face=Arial color=#808080
size=1>M + 61 412 390 267</FONT></SPAN> <BR><SPAN lang=en-us><FONT
face=Arial color=#808080 size=1>E jocelyn.dart@sap.com</FONT></SPAN>
<BR><SPAN lang=en-us><FONT face=Arial color=#808080 size=1><A
href="http://www.sap.com/">http://www.sap.com</A></FONT></SPAN> </P>
<P><SPAN lang=en-au><FONT face="Times New Roman" color=#ff0000 size=1>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. </FONT></SPAN></P>
<P><SPAN lang=en-au><FONT face="Times New Roman" color=#ff0000 size=1>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.</FONT></SPAN></P>
<P><SPAN lang=en-au><FONT face="Times New Roman" color=#ff0000 size=1>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. </FONT></SPAN></P>
<DIV> </DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> sap-wug-bounces@mit.edu
[mailto:sap-wug-bounces@mit.edu] <B>On Behalf Of </B>Seko, Ryan<BR><B>Sent:</B>
Friday, 11 November 2005 6:18 AM<BR><B>To:</B> SAP Workflow Users'
Group<BR><B>Subject:</B> SRM 4.0 Item-Based Approval
Question<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV><FONT face=Arial size=2><SPAN class=941374522-09112005>Hi
All,</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=941374522-09112005></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=941374522-09112005>My company will soon
be upgrading from SRM 2.0 (EBP 3.5) to SRM 4.0 and I'm planning to redesign our
custom shopping cart approval process at the same time. Our main approval
is based on cost center with the possibility of up to three more
approvals after that. Currently, we use dynamic parallel
processing to send the entire shopping cart to all cost center approvers
(including items with multiple account assigments). It looks like SAP's
Item-Based Approval might work for us, but one concern I have is if it
can handle items with multiple account assignments. Does anyone know
if the Badi can be programmed to have a single item sent
to multiple approvers? From everything I've read, it
appears everything has to be done through the Badi since
the item-based and n-level workflows can't be copied then modified
like past standard workflows. Is that correct?</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=941374522-09112005></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=941374522-09112005>While I'm at it,
I'll throw this one out too (in case I don't use the item-based
approval). I have a function to look up the cost center approver(s)
from a custom table. Is it more efficient to call this function from a
object attribute or from a rule within the workflow? From reading the
"Practical Workflow" book it appears I would have to add the attribute to a
subtype of AAGENT to maintain ad-hoc approver functionality. Would I
lose that functionality if my function is called from a workflow
rule?</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=941374522-09112005></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=941374522-09112005>Thanks for your
help,</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=941374522-09112005>Ryan</SPAN></FONT></DIV></BODY></HTML>