<!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=806280213-07092005><FONT face=Arial
color=#0000ff size=2>Ok - you missed a step. If you want your approver to
see the form in its web format you can do it in two ways.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=806280213-07092005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=806280213-07092005><FONT face=Arial
color=#0000ff size=2>1. Send them a web form - i.e. they execute in the portal
as well - the workflows do show this option - its simply a matter of using a
task with the correct object type/method</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=806280213-07092005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=806280213-07092005><FONT face=Arial
color=#0000ff size=2>2. If they *really* want to approve via R/3, then you are
supposed to configure an "action" against the notification type so that from
QISR they can click on a link and see the form in its web format, rather than
use the configurable tab which shows the data in its raw format.
Some of the ESS forms show how this is done. Its a good idea to configure
the action in any case so you can equally see the form from both the web and
R/3. </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>Andy Curtis<BR><B>Sent:</B>
Wednesday, 07 September 2005 10:50 PM<BR><B>To:</B> SAP Workflow Users'
Group<BR><B>Subject:</B> Re: Help needed with this scenario<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV>The following was my experience of ISR's</DIV>
<DIV> </DIV>
<DIV>The issue with ISR's and Wf templates WS50000040/41/42 is that the
user sees and enters data into a nice webform and SAP sends the QISR1
transaction as a task to change the status (ie approve). So one
person sees a webform and understands it, the approver sees QISR1, has
to flip to the extended QISR transaction to get a configurable tab that displays
the webform before setting the status. When I showed this to my client
they did not like it. In the end I still used the ISR framework,
as Jocelyn says if offers lots of configuration options and is standard
technology for ESS/MSS, but modified the Wf template to use a webflow task to
display the webform via the browser. I additionally had to have
buttons on the webform for Approve/Reject and fed this back to the Wf
container via the ISR BAPI's </DIV>
<DIV> </DIV>
<DIV>I also got trapped by the QISR BAPI's not feeding back any changed
characteristics when called in display mode, they are only fed back in input and
change mode.</DIV>
<DIV> </DIV>
<DIV>At the end of the piece of work I was not convinced about ISR's and would
choose BSP's in future.</DIV>
<DIV> </DIV>
<DIV>Andy Curtis</DIV></BODY></HTML>