<!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.1515" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=183204006-12092005><FONT face=Arial
color=#0000ff size=2>Cyrus, </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=183204006-12092005><FONT face=Arial
color=#0000ff size=2>Please ALWAYS ask questions via the WUG - it is not
appropriate to contact me directly with consulting questions as I am a paid
consultant just like you - you should always use a forum where information is
exchanged freely. </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=183204006-12092005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=183204006-12092005><FONT face=Arial
color=#0000ff size=2>No you absolutely cannot use your existing R/3 PR/PO
workflow for SRM. </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=183204006-12092005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=183204006-12092005><FONT face=Arial
color=#0000ff size=2>What you can do is use RH_GET_ACTORS via RFC to determine
your agents from R/3. </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=183204006-12092005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=183204006-12092005><FONT face=Arial
color=#0000ff size=2>But you will still need to use the SRM workflows for SRM.
</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=183204006-12092005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=183204006-12092005><FONT face=Arial
color=#0000ff size=2>There are a number orf reasons for this including but not
limited to:</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=183204006-12092005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=183204006-12092005><FONT face=Arial
color=#0000ff size=2>1. A shopping cart is NOT a purchase requistion - it is
before or instead of a purchase requisition. But a shopping cart can also be
used to create a PO, a PR a Reservation, or a Bid
Invitation.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=183204006-12092005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=183204006-12092005><FONT face=Arial
color=#0000ff size=2>2. SRM provides much more flexibility and visibility to the
user on what is happening before, during and after the workflow - this
functionality depends to a great extent on the very specific patterns of
behaviour used in SRM. SRM has *a lot* of special workflow processing
around these. </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=183204006-12092005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=183204006-12092005><FONT face=Arial
color=#0000ff size=2>If you want to put similar functionality in SRM as compared
to R/3 use the BADI approval workflow. </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> John Cyrus [mailto:cyrus.john@gmail.com]
<BR><B>Sent:</B> Saturday, 10 September 2005 5:33 AM<BR><B>To:</B> Dart,
Jocelyn<BR><B>Subject:</B> R3 Workflow in SRM<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV>Hi Jocelyn,</DIV>
<DIV> </DIV>
<DIV>I saw your posting on SAP-WUG. I have a question regarding a situation I
have wherein I am trying to re-use an R3 Workflow setup in my SRM installation,
is this doable ? The client has created a very rich Workflow setup on R3 which
we want to use in the SRM implementation on a dynamic basis rather than
downloading anything onto EBP. I know that the program RSWUWFML2 is supposed to
do this. Also the RFC RH_GET_ACTORS is useful. </DIV>
<DIV> </DIV>
<DIV>I am at a design phase and trying to make a recommendation on what is
doable. Is it right to say that the R3 Workflow can be used as is on a Dynamic
basis by just having the same business objects (PR, PO ...) defined on the R3
side. As far as the ABAP development involved, is there goods hooks into SRM
(like BADI's) to make this happen. </DIV>
<DIV> </DIV>
<DIV>I will greatly appreciate your help.</DIV>
<DIV> </DIV>
<DIV>Greetings</DIV>
<DIV> </DIV>
<DIV>Cyrus<BR clear=all></DIV></BODY></HTML>