<!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=591501323-18122005><FONT face=Arial
color=#0000ff size=2>Hi Ryan,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=591501323-18122005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=591501323-18122005><FONT face=Arial
color=#0000ff size=2>Sounds like you need to read a couple more SAP notes and
read the fine print a little more carefully. </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=591501323-18122005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=591501323-18122005><FONT face=Arial
color=#0000ff size=2>ITEM_APPROVAL_OBJ can use any criteria you care to
use - its up to you to keep the relationship going which</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=591501323-18122005><FONT face=Arial
color=#0000ff size=2>you can always do via your own custom
table, e.g. you set a "key id", "key value" of your own choosing -
that key value </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=591501323-18122005><FONT face=Arial
color=#0000ff size=2>could be a look up key to your own custom table,
rather than an SAP field value. Item_approval_obj is just
using the key ids/values </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=591501323-18122005><FONT face=Arial
color=#0000ff size=2>to reliably hold which items belong to which approval
object - it doesn't care whether the id or values are real SAP fields or not.
</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=591501323-18122005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=591501323-18122005><FONT face=Arial
color=#0000ff size=2>The absolutely no gaps requirement is obsolete. If
you read some of the other notes in the same area the gap situation is now
handled. </FONT></SPAN></DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </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>
Saturday, 17 December 2005 5:49 AM<BR><B>To:</B> SAP Workflow Users'
Group<BR><B>Subject:</B> SRM 4.0 Item-Based Approval Levels Limited to
3?<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV><SPAN class=228240618-16122005><FONT face=Arial size=2>I've been reviewing
the functionality of the item-based approval for shopping carts and
a couple of things aren't clear to me:</FONT></SPAN></DIV>
<DIV><SPAN class=228240618-16122005><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=228240618-16122005><FONT face=Arial size=2>1. I noticed
that the ITEM_APPROVAL_OBJ parameter (Assignment of Approval Objects to Approval
Criteria) for badi BBP_WFL_APPROV_BADI only allows for 3 criteria. So
unlike the n-level workflow, is the item-based workflow limited to only 3 levels
or am I missing something?</FONT></SPAN></DIV>
<DIV><SPAN class=228240618-16122005><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=228240618-16122005><FONT face=Arial size=2>2. At the end
of the IMG documentation for the badi it states, "Note that there must be
<B>absolutely no gaps</B> in the approval steps and that approvers must be
defined for every step." This seems contradictory to some of the
other documentation I've been reading. In my scenario, all items would
require an approval at the first level, but for the second and third levels only
some or possibly none of the items may require an approval. So in a case
where only a first level and third level approval is required, the
item-based workflow won't work?</FONT></SPAN></DIV>
<DIV><SPAN class=228240618-16122005><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=228240618-16122005><FONT face=Arial size=2>Thanks for your
help,</FONT></SPAN></DIV>
<DIV><SPAN class=228240618-16122005><FONT face=Arial
size=2>Ryan</FONT></SPAN></DIV></BODY></HTML>