<!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.1528" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=767112210-17022006><FONT face=Arial
color=#0000ff size=2>Monique, </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=767112210-17022006><FONT face=Arial
color=#0000ff size=2>Yes its possible but not standard.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=767112210-17022006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=767112210-17022006><FONT face=Arial color=#0000ff size=2>I've
done this before - </FONT></SPAN></DIV>
<DIV><SPAN class=767112210-17022006><FONT face=Arial color=#0000ff size=2>1. All
POs needed to be created with a release strategy - even if that effectively
states they are automatically approved on first creation</FONT></SPAN></DIV>
<DIV><SPAN class=767112210-17022006><FONT face=Arial color=#0000ff size=2>2.
</FONT></SPAN><SPAN class=767112210-17022006><FONT face=Arial color=#0000ff
size=2>we used a workflow (I think started by the significantly changed event)
to explicitly reset the release code</FONT></SPAN></DIV>
<DIV><SPAN class=767112210-17022006><FONT face=Arial color=#0000ff size=2>3.
Resetting the release code in turn started the standard
workflow</FONT></SPAN></DIV>
<DIV><SPAN class=767112210-17022006><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=767112210-17022006><FONT face=Arial color=#0000ff size=2>It was
a while ago but the process should still work.</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>Stephens, Monique S
L<BR><B>Sent:</B> Friday, 17 February 2006 6:54 AM<BR><B>To:</B>
SAP-WUG@MITVMA.MIT.EDU<BR><B>Subject:</B> PO Workflow<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV><FONT face=Arial size=2><SPAN class=491024319-16022006>I need some
assistance with PO workflow. Prior to SRM, our users were creating PO's
that were then routed through the system for approvals. We had particular
release indicators set up. Therefore, if a PO is blocked at a particular
release level, a pre-determined percentage change would need to be made for the
PO to go back through workflow. The release indicators identify this
percentage.</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=491024319-16022006></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=491024319-16022006>Now, with SRM, our
users create shopping carts that route through approvals. But, when the
cart transfers over to SAP and turns into a PO, no workflow is initiated.
Our users are not allowed to change these PO's. We would like to look at
our pre-SRM workflow, enhance it, and use it for the newer PO's. In order
to do this, we need to tell the system that either a percentage change (already
identified in the release indicators) or value change will reset the
releases. We only want workflow to be initiated after a PO has already
been generated and changed after the fact. Is there a way to set up
workflow to look at value and percentage like it can for invoice
tolerances? </SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=491024319-16022006></SPAN></FONT> </DIV>
<DIV> </DIV>
<DIV align=left><FONT face="Lucida Handwriting"
color=#ff0000><STRONG><EM>Monique Stephens</EM></STRONG></FONT></DIV>
<DIV align=left><FONT face=Arial size=2>SAP Analyst</FONT></DIV>
<DIV align=left><FONT face=Arial size=2>Baylor College of Medicine</FONT></DIV>
<DIV align=left><FONT face=Arial size=2>713-798-1349</FONT></DIV>
<DIV align=left><FONT face=Arial size=2>713-798-1326 (FAX)</FONT></DIV>
<DIV> </DIV></BODY></HTML>