<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<STYLE>P {
        PADDING-RIGHT: 0px; PADDING-LEFT: 0px; PADDING-BOTTOM: 0px; MARGIN: 0px; PADDING-TOP: 0px
}
BODY {
        FONT-SIZE: 10pt; FONT-FAMILY: Tahoma
}
</STYLE>

<META content="MSHTML 6.00.2800.1555" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=460401904-28062006><FONT face=Arial 
color=#0000ff>Stephane, </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=460401904-28062006><FONT face=Arial 
color=#0000ff></FONT></SPAN>&nbsp;</DIV>
<DIV dir=ltr align=left><SPAN class=460401904-28062006><FONT face=Arial 
color=#0000ff>Go to the workflow builder (transaction SWDD), bring up the 
workflows, go to the basic data area (hat icon), check the properties of the 
workflow - check ad hoc agent assignment is possible. <SPAN 
class=460401904-28062006><FONT face=Arial color=#0000ff>Sounds like someone may 
have accidentally turned it off.&nbsp;<SPAN class=460401904-28062006><FONT 
face=Arial color=#0000ff>If that's the case try retransporting your workflow. 
</FONT></SPAN></FONT></SPAN></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=460401904-28062006><FONT face=Arial 
color=#0000ff><SPAN class=460401904-28062006><FONT face=Arial 
color=#0000ff><SPAN 
class=460401904-28062006></SPAN></FONT></SPAN></FONT></SPAN>&nbsp;</DIV>
<DIV dir=ltr align=left><SPAN class=460401904-28062006><FONT face=Arial 
color=#0000ff>Also check that the agent assignment to the workflow level itself 
(not to the approval step) is the same in DEV and QA. </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=460401904-28062006><FONT face=Arial 
color=#0000ff>In which case you can use program RHMOVE30 to transport the 
assignments to the WS object.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=460401904-28062006></SPAN><SPAN 
class=460401904-28062006></SPAN><SPAN class=460401904-28062006><FONT face=Arial 
color=#0000ff></FONT></SPAN>&nbsp;</DIV>
<DIV>&nbsp;</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&nbsp;&nbsp; +61 412 390 
267</FONT></SPAN> <BR><SPAN lang=en-us><FONT face=Arial color=#808080 
size=1>M&nbsp;&nbsp; + 61 412 390 267</FONT></SPAN> <BR><SPAN lang=en-us><FONT 
face=Arial color=#808080 size=1>E&nbsp;&nbsp; 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>&nbsp;</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>Stéphane 
Bailleul<BR><B>Sent:</B> Wednesday, 28 June 2006 1:48 PM<BR><B>To:</B> 
sap-wug@mit.edu<BR><B>Subject:</B> SRM Shopping Cart preview 
error<BR></FONT><BR></DIV>
<DIV></DIV>
<TABLE cellSpacing=0 cellPadding=2 width=930 border=0>
  <TBODY>
  <TR>
    <TD><FONT face="Tms Rmn">
      <P>Hi All, <BR>&nbsp;<BR>&nbsp;<BR>We are using the standard Badi workflow 
      WS14000134 &amp; WS14000133 with<BR>the standard decision task TS10008126 
      ( general task)<BR>&nbsp;<BR>The preview is working on our Development 
      system and not on the quality<BR>system. I have checked the task, Business 
      object, rule to determine<BR>the agent and the BADI all are set up in the 
      same way<BR>&nbsp;<BR>The message that we have on the preview is the 
      following:<BR>"Approval step without ad-hoc capability. No preview 
      possible"<BR>&nbsp;<BR>The agent determination is <FONT class="">done in 
      the business object&nbsp;. <FONT class="">When the shopping cart is on 
      hold&nbsp;or saved I can&nbsp;see that the approvers are calculated 
      correctly. </FONT>&nbsp;</FONT><BR>The <FONT class="">workflow runs 
      perfectly well, but only the preview is causing us problem</FONT><BR>Can 
      you help me if you have any idea of the possible origin of this problem 
      ?<BR>Technical information:<BR>SAPKA64016 Cross-Application 
      Component<BR>SAPKB64016 SAP Basis Component<BR>SAPKIPYJ64 Basis Plug-In 
      (PI_BASIS) 2005_1_640<BR>SAPKITLPS1 SAP Solution Tools Plug-In (ST-PI 
      003C_6<BR>SAPKW35014 Business Information Warehouse<BR>SAPKIBKS08 
      SRM_SERVER<BR>SAPK-26404INCCM CCM 200_640 : Add-On Delta 
      Upgrade<BR></FONT></P></TD></TR></TBODY></TABLE><FONT face="Tms Rmn">
<P></P>&nbsp;<BR></FONT><BR><FONT class="">Many Thanks</FONT> 
<BR>Stephane<BR><BR><BR><BR>
<HR id=stopSpelling>
<BR>&gt; From: sap-wug-request@mit.edu<BR>&gt; Subject: SAP-WUG Digest, Vol 19, 
Issue 70<BR>&gt; To: sap-wug@mit.edu<BR>&gt; Date: Tue, 27 Jun 2006 22:43:25 
-0400<BR>&gt; <BR>&gt; 
Send&nbsp;SAP-WUG&nbsp;mailing&nbsp;list&nbsp;submissions&nbsp;to<BR>&gt; 
sap-wug@mit.edu<BR>&gt; <BR>&gt; 
To&nbsp;subscribe&nbsp;or&nbsp;unsubscribe&nbsp;via&nbsp;the&nbsp;World&nbsp;Wide&nbsp;Web,&nbsp;visit<BR>&gt; 
http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>&gt; 
or,&nbsp;via&nbsp;email,&nbsp;send&nbsp;a&nbsp;message&nbsp;with&nbsp;subject&nbsp;or&nbsp;body&nbsp;'help'&nbsp;to<BR>&gt; 
sap-wug-request@mit.edu<BR>&gt; <BR>&gt; 
You&nbsp;can&nbsp;reach&nbsp;the&nbsp;person&nbsp;managing&nbsp;the&nbsp;list&nbsp;at<BR>&gt; 
sap-wug-owner@mit.edu<BR>&gt; <BR>&gt; 
When&nbsp;replying,&nbsp;please&nbsp;edit&nbsp;your&nbsp;Subject&nbsp;line&nbsp;so&nbsp;it&nbsp;is&nbsp;more&nbsp;specific<BR>&gt; 
than&nbsp;"Re:&nbsp;Contents&nbsp;of&nbsp;SAP-WUG&nbsp;digest..."<BR>&gt; 
<BR>&gt; <BR>&gt; Today's&nbsp;Topics:<BR>&gt; <BR>&gt; 
&nbsp;&nbsp;&nbsp;1.&nbsp;RE:&nbsp;EP&nbsp;7.0&nbsp;UWL&nbsp;Inquiry&nbsp;(Dart,&nbsp;Jocelyn)<BR>&gt; 
&nbsp;&nbsp;&nbsp;2.&nbsp;RE:&nbsp;Validation&nbsp;of&nbsp;selected&nbsp;substitutes&nbsp;?&nbsp;(Dart,&nbsp;Jocelyn)<BR>&gt; 
&nbsp;&nbsp;&nbsp;3.&nbsp;EBP&nbsp;Worflow&nbsp;Trigger&nbsp;issue&nbsp;with&nbsp;multiple&nbsp;lines&nbsp;in&nbsp;SC&nbsp;(D&nbsp;Duchon)<BR>&gt; 
&nbsp;&nbsp;&nbsp;4.&nbsp;RE:&nbsp;EP&nbsp;7.0&nbsp;UWL&nbsp;Inquiry&nbsp;(jerry.martinek)<BR>&gt; 
<BR>&gt; <BR>&gt; 
----------------------------------------------------------------------<BR>&gt; 
<BR>&gt; Message:&nbsp;1<BR>&gt; 
Date:&nbsp;Wed,&nbsp;28&nbsp;Jun&nbsp;2006&nbsp;07:30:12&nbsp;+0800<BR>&gt; 
From:&nbsp;"Dart,&nbsp;Jocelyn"&nbsp;&lt;jocelyn.dart@sap.com&gt;<BR>&gt; 
Subject:&nbsp;RE:&nbsp;EP&nbsp;7.0&nbsp;UWL&nbsp;Inquiry<BR>&gt; 
To:&nbsp;"SAP&nbsp;Workflow&nbsp;Users'&nbsp;Group"&nbsp;&lt;sap-wug@mit.edu&gt;<BR>&gt; 
Message-ID:<BR>&gt; 
&lt;F843AF000027394A9F3D3194109269F45E15A7@sgsine11.sin.sap.corp&gt;<BR>&gt; 
Content-Type:&nbsp;text/plain;&nbsp;charset="us-ascii"<BR>&gt; <BR>&gt; 
Jerry,&nbsp;<BR>&gt; 
Again&nbsp;this&nbsp;is&nbsp;possible&nbsp;and&nbsp;relatively&nbsp;uncomplicated&nbsp;to&nbsp;do&nbsp;from&nbsp;Extended<BR>&gt; 
Notifications.&nbsp;<BR>&gt; &nbsp;<BR>&gt; <BR>&gt; Regards,&nbsp;<BR>&gt; 
Jocelyn&nbsp;Dart&nbsp;<BR>&gt; Senior&nbsp;Consultant&nbsp;<BR>&gt; 
SAP&nbsp;Australia&nbsp;Pty&nbsp;Ltd.&nbsp;<BR>&gt; 
Level&nbsp;1/168&nbsp;Walker&nbsp;St.&nbsp;<BR>&gt; 
North&nbsp;Sydney&nbsp;<BR>&gt; NSW,&nbsp;2060&nbsp;<BR>&gt; 
Australia&nbsp;<BR>&gt; 
T&nbsp;&nbsp;&nbsp;+61&nbsp;412&nbsp;390&nbsp;267&nbsp;<BR>&gt; 
M&nbsp;&nbsp;&nbsp;+&nbsp;61&nbsp;412&nbsp;390&nbsp;267&nbsp;<BR>&gt; 
E&nbsp;&nbsp;&nbsp;jocelyn.dart@sap.com&nbsp;<BR>&gt; 
http://www.sap.com&nbsp;&lt;http://www.sap.com/&gt;&nbsp;&nbsp;<BR>&gt; <BR>&gt; 
The&nbsp;information&nbsp;contained&nbsp;in&nbsp;or&nbsp;attached&nbsp;to&nbsp;this&nbsp;electronic&nbsp;transmission<BR>&gt; 
is&nbsp;confidential&nbsp;and&nbsp;may&nbsp;be&nbsp;legally&nbsp;privileged.&nbsp;It&nbsp;is&nbsp;intended&nbsp;only&nbsp;for<BR>&gt; 
the&nbsp;person&nbsp;or&nbsp;entity&nbsp;to&nbsp;which&nbsp;it&nbsp;is&nbsp;addressed.&nbsp;If&nbsp;you&nbsp;are&nbsp;not&nbsp;the<BR>&gt; 
intended&nbsp;recipient,&nbsp;you&nbsp;are&nbsp;hereby&nbsp;notified&nbsp;that&nbsp;any&nbsp;distribution,<BR>&gt; 
copying,&nbsp;review,&nbsp;retransmission,&nbsp;dissemination&nbsp;or&nbsp;other&nbsp;use&nbsp;of&nbsp;this<BR>&gt; 
electronic&nbsp;transmission&nbsp;or&nbsp;the&nbsp;information&nbsp;contained&nbsp;in&nbsp;it&nbsp;is&nbsp;strictly<BR>&gt; 
prohibited.&nbsp;If&nbsp;you&nbsp;have&nbsp;received&nbsp;this&nbsp;electronic&nbsp;transmission&nbsp;in&nbsp;error,<BR>&gt; 
please&nbsp;immediately&nbsp;contact&nbsp;the&nbsp;sender&nbsp;to&nbsp;arrange&nbsp;for&nbsp;the&nbsp;return&nbsp;of&nbsp;the<BR>&gt; 
original&nbsp;documents.&nbsp;<BR>&gt; <BR>&gt; 
Electronic&nbsp;transmission&nbsp;cannot&nbsp;be&nbsp;guaranteed&nbsp;to&nbsp;be&nbsp;secure&nbsp;and<BR>&gt; 
accordingly,&nbsp;the&nbsp;sender&nbsp;does&nbsp;not&nbsp;accept&nbsp;liability&nbsp;for&nbsp;any&nbsp;such&nbsp;data<BR>&gt; 
corruption,&nbsp;interception,&nbsp;unauthorized&nbsp;amendment,&nbsp;viruses,&nbsp;delays&nbsp;or&nbsp;the<BR>&gt; 
consequences&nbsp;thereof.<BR>&gt; <BR>&gt; 
Any&nbsp;views&nbsp;expressed&nbsp;in&nbsp;this&nbsp;electronic&nbsp;transmission&nbsp;are&nbsp;those&nbsp;of&nbsp;the<BR>&gt; 
individual&nbsp;sender,&nbsp;except&nbsp;where&nbsp;the&nbsp;message&nbsp;states&nbsp;otherwise&nbsp;and&nbsp;the<BR>&gt; 
sender&nbsp;is&nbsp;authorized&nbsp;to&nbsp;state&nbsp;them&nbsp;to&nbsp;be&nbsp;the&nbsp;views&nbsp;of&nbsp;SAP&nbsp;AG&nbsp;or&nbsp;any&nbsp;of<BR>&gt; 
its&nbsp;subsidiaries.&nbsp;SAP&nbsp;AG,&nbsp;its&nbsp;subsidiaries,&nbsp;and&nbsp;their&nbsp;directors,<BR>&gt; 
officers&nbsp;and&nbsp;employees&nbsp;make&nbsp;no&nbsp;representation&nbsp;nor&nbsp;accept&nbsp;any&nbsp;liability<BR>&gt; 
for&nbsp;the&nbsp;accuracy&nbsp;or&nbsp;completeness&nbsp;of&nbsp;the&nbsp;views&nbsp;or&nbsp;information&nbsp;contained<BR>&gt; 
herein.&nbsp;Please&nbsp;be&nbsp;aware&nbsp;that&nbsp;the&nbsp;furnishing&nbsp;of&nbsp;any&nbsp;pricing&nbsp;information/<BR>&gt; 
business&nbsp;proposal&nbsp;herein&nbsp;is&nbsp;indicative&nbsp;only,&nbsp;is&nbsp;subject&nbsp;to&nbsp;change&nbsp;and<BR>&gt; 
shall&nbsp;not&nbsp;be&nbsp;construed&nbsp;as&nbsp;an&nbsp;offer&nbsp;or&nbsp;as&nbsp;constituting&nbsp;a&nbsp;binding<BR>&gt; 
agreement&nbsp;on&nbsp;the&nbsp;part&nbsp;of&nbsp;SAP&nbsp;AG&nbsp;or&nbsp;any&nbsp;of&nbsp;its&nbsp;subsidiaries&nbsp;to&nbsp;enter&nbsp;into<BR>&gt; 
any&nbsp;relationship,&nbsp;unless&nbsp;otherwise&nbsp;expressly&nbsp;stated.&nbsp;<BR>&gt; 
<BR>&gt; &nbsp;<BR>&gt; <BR>&gt; ________________________________<BR>&gt; 
<BR>&gt; 
From:&nbsp;sap-wug-bounces@mit.edu&nbsp;[mailto:sap-wug-bounces@mit.edu]&nbsp;On&nbsp;Behalf<BR>&gt; 
Of&nbsp;jerry.martinek<BR>&gt; 
Sent:&nbsp;Monday,&nbsp;26&nbsp;June&nbsp;2006&nbsp;4:09&nbsp;AM<BR>&gt; 
To:&nbsp;'SAP&nbsp;Workflow&nbsp;Users'&nbsp;Group'<BR>&gt; 
Subject:&nbsp;RE:&nbsp;EP&nbsp;7.0&nbsp;UWL&nbsp;Inquiry<BR>&gt; <BR>&gt; 
<BR>&gt; <BR>&gt; Hi&nbsp;Mark,<BR>&gt; <BR>&gt; &nbsp;<BR>&gt; <BR>&gt; 
That's&nbsp;what&nbsp;I&nbsp;was&nbsp;afraid&nbsp;of.&nbsp;What&nbsp;I&nbsp;want&nbsp;is&nbsp;a&nbsp;generic,&nbsp;common&nbsp;notice&nbsp;and<BR>&gt; 
not&nbsp;a&nbsp;task&nbsp;description&nbsp;informing&nbsp;the&nbsp;approver&nbsp;that&nbsp;they&nbsp;have&nbsp;a<BR>&gt; 
pending/waiting&nbsp;request&nbsp;in&nbsp;their&nbsp;UWL.&nbsp;&nbsp;Sort&nbsp;of&nbsp;similar&nbsp;to&nbsp;the&nbsp;UWL&nbsp;based<BR>&gt; 
substitutions.&nbsp;I&nbsp;don't&nbsp;want&nbsp;to&nbsp;have&nbsp;multiple&nbsp;instance&nbsp;of&nbsp;this&nbsp;job,&nbsp;one<BR>&gt; 
per&nbsp;SAP&nbsp;system.&nbsp;Furthermore&nbsp;what&nbsp;I&nbsp;need&nbsp;is&nbsp;an&nbsp;URL&nbsp;in&nbsp;the&nbsp;email&nbsp;that<BR>&gt; 
takes&nbsp;them&nbsp;to&nbsp;the&nbsp;UWL&nbsp;folder&nbsp;directly&nbsp;from&nbsp;Outlook.<BR>&gt; 
<BR>&gt; &nbsp;<BR>&gt; <BR>&gt; 
Thanks&nbsp;for&nbsp;the&nbsp;confirmation.<BR>&gt; <BR>&gt; &nbsp;<BR>&gt; 
<BR>&gt; Regards,<BR>&gt; <BR>&gt; Jerry<BR>&gt; <BR>&gt; 
________________________________<BR>&gt; <BR>&gt; 
From:&nbsp;sap-wug-bounces@mit.edu&nbsp;[mailto:sap-wug-bounces@mit.edu]&nbsp;On&nbsp;Behalf<BR>&gt; 
Of&nbsp;Mark&nbsp;Pyc<BR>&gt; 
Sent:&nbsp;June&nbsp;25,&nbsp;2006&nbsp;12:47&nbsp;AM<BR>&gt; 
To:&nbsp;SAP&nbsp;Workflow&nbsp;Users'&nbsp;Group<BR>&gt; 
Subject:&nbsp;Re:&nbsp;EP&nbsp;7.0&nbsp;UWL&nbsp;Inquiry<BR>&gt; <BR>&gt; 
&nbsp;<BR>&gt; <BR>&gt; G'day&nbsp;Jerry,<BR>&gt; <BR>&gt; 
I&nbsp;can&nbsp;appreciate&nbsp;that&nbsp;what&nbsp;you're&nbsp;after&nbsp;is&nbsp;an&nbsp;UWL&nbsp;equivalent&nbsp;of<BR>&gt; 
RSWUWFML2.&nbsp;i.e.&nbsp;like&nbsp;the&nbsp;UWL&nbsp;it&nbsp;would&nbsp;be&nbsp;central&nbsp;and&nbsp;only&nbsp;configured<BR>&gt; 
once&nbsp;rather&nbsp;than&nbsp;in&nbsp;each&nbsp;backend&nbsp;system,&nbsp;but&nbsp;I&nbsp;don't&nbsp;think&nbsp;such<BR>&gt; 
functionality&nbsp;exists.&nbsp;I&nbsp;think&nbsp;you&nbsp;just&nbsp;have&nbsp;to&nbsp;set&nbsp;up&nbsp;RSWUWFML2&nbsp;in&nbsp;each<BR>&gt; 
system.&nbsp;<BR>&gt; <BR>&gt; Have&nbsp;fun,<BR>&gt; Mark<BR>&gt; <BR>&gt; 
On&nbsp;6/25/06,&nbsp;jerry.martinek&nbsp;&lt;jerry.martinek@shawbiz.ca&gt;&nbsp;wrote:<BR>&gt; 
<BR>&gt; Hi&nbsp;All,<BR>&gt; <BR>&gt; &nbsp;<BR>&gt; <BR>&gt; 
Is&nbsp;it&nbsp;possible&nbsp;to&nbsp;setup&nbsp;an&nbsp;UWL&nbsp;triggered&nbsp;email&nbsp;notification&nbsp;process&nbsp;if<BR>&gt; 
the&nbsp;owner&nbsp;receives&nbsp;a&nbsp;workitem&nbsp;in&nbsp;their&nbsp;UWL?&nbsp;It's&nbsp;sort&nbsp;of&nbsp;the&nbsp;opposite<BR>&gt; 
functionality&nbsp;of&nbsp;the&nbsp;UWL&nbsp;Alerts.&nbsp;The&nbsp;goal&nbsp;is&nbsp;to&nbsp;let&nbsp;the&nbsp;selected&nbsp;person<BR>&gt; 
know&nbsp;that&nbsp;they&nbsp;have&nbsp;a&nbsp;waiting&nbsp;approval&nbsp;request&nbsp;in&nbsp;their&nbsp;UWL&nbsp;inbox.<BR>&gt; 
<BR>&gt; &nbsp;<BR>&gt; <BR>&gt; 
I've&nbsp;read&nbsp;through&nbsp;the&nbsp;documentation&nbsp;on&nbsp;the&nbsp;UWL&nbsp;but&nbsp;I&nbsp;couldn't&nbsp;find<BR>&gt; 
anything&nbsp;on&nbsp;this&nbsp;subject.<BR>&gt; <BR>&gt; &nbsp;<BR>&gt; 
<BR>&gt; Thanks,<BR>&gt; <BR>&gt; Jerry<BR>&gt; <BR>&gt; &nbsp;&nbsp;<BR>&gt; 
<BR>&gt; <BR>&gt; _______________________________________________<BR>&gt; 
SAP-WUG&nbsp;mailing&nbsp;list<BR>&gt; SAP-WUG@mit.edu<BR>&gt; 
http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>&gt; <BR>&gt; <BR>&gt; 
<BR>&gt; &nbsp;<BR>&gt; <BR>&gt; 
--------------&nbsp;next&nbsp;part&nbsp;--------------<BR>&gt; 
An&nbsp;HTML&nbsp;attachment&nbsp;was&nbsp;scrubbed...<BR>&gt; 
URL:&nbsp;http://mailman.mit.edu/pipermail/sap-wug/attachments/20060628/b783a462/attachment-0001.htm<BR>&gt; 
<BR>&gt; ------------------------------<BR>&gt; <BR>&gt; Message:&nbsp;2<BR>&gt; 
Date:&nbsp;Wed,&nbsp;28&nbsp;Jun&nbsp;2006&nbsp;07:34:25&nbsp;+0800<BR>&gt; 
From:&nbsp;"Dart,&nbsp;Jocelyn"&nbsp;&lt;jocelyn.dart@sap.com&gt;<BR>&gt; 
Subject:&nbsp;RE:&nbsp;Validation&nbsp;of&nbsp;selected&nbsp;substitutes&nbsp;?<BR>&gt; 
To:&nbsp;"SAP&nbsp;Workflow&nbsp;Users'&nbsp;Group"&nbsp;&lt;sap-wug@MIT.EDU&gt;<BR>&gt; 
Message-ID:<BR>&gt; 
&lt;F843AF000027394A9F3D3194109269F45E15A9@sgsine11.sin.sap.corp&gt;<BR>&gt; 
Content-Type:&nbsp;text/plain; charset="us-ascii"<BR>&gt; <BR>&gt; 
Sue,&nbsp;<BR>&gt; <BR>&gt; 
Yes&nbsp;we&nbsp;have&nbsp;asked&nbsp;for&nbsp;BADIs&nbsp;but&nbsp;no&nbsp;official&nbsp;word&nbsp;yet&nbsp;on&nbsp;when&nbsp;or&nbsp;whether<BR>&gt; 
they&nbsp;will&nbsp;be&nbsp;introduced.&nbsp;&nbsp;&nbsp;However&nbsp;if&nbsp;you&nbsp;are&nbsp;using&nbsp;the&nbsp;UWL&nbsp;with&nbsp;SRM<BR>&gt; 
(which&nbsp;you&nbsp;are&nbsp;I&nbsp;seem&nbsp;to&nbsp;remember?)<BR>&gt; 
-&nbsp;a&nbsp;mod&nbsp;in&nbsp;the&nbsp;relevant&nbsp;SAP_WAPI_SUBSTITUTE_CREATE&nbsp;function&nbsp;module&nbsp;will<BR>&gt; 
do&nbsp;it.&nbsp;&nbsp;I've&nbsp;done&nbsp;this&nbsp;before&nbsp;at&nbsp;another&nbsp;project&nbsp;...&nbsp;this&nbsp;is&nbsp;where&nbsp;we've<BR>&gt; 
asked&nbsp;for&nbsp;the&nbsp;user-exit&nbsp;to&nbsp;be&nbsp;placed.&nbsp;&nbsp;&nbsp;You'll&nbsp;still&nbsp;have&nbsp;to&nbsp;put<BR>&gt; 
together&nbsp;your&nbsp;own&nbsp;logic&nbsp;for&nbsp;deciding&nbsp;what&nbsp;is&nbsp;an&nbsp;attribute&nbsp;match.&nbsp;<BR>&gt; 
<BR>&gt; <BR>&gt; Regards,<BR>&gt; Jocelyn&nbsp;Dart<BR>&gt; 
Senior&nbsp;Consultant<BR>&gt; SAP&nbsp;Australia&nbsp;Pty&nbsp;Ltd.<BR>&gt; 
Level&nbsp;1/168&nbsp;Walker&nbsp;St.<BR>&gt; North&nbsp;Sydney&nbsp;<BR>&gt; 
NSW,&nbsp;2060<BR>&gt; Australia<BR>&gt; 
T&nbsp;&nbsp;&nbsp;+61&nbsp;412&nbsp;390&nbsp;267<BR>&gt; 
M&nbsp;&nbsp;&nbsp;+&nbsp;61&nbsp;412&nbsp;390&nbsp;267<BR>&gt; 
E&nbsp;&nbsp;&nbsp;jocelyn.dart@sap.com<BR>&gt; http://www.sap.com<BR>&gt; 
<BR>&gt; 
The&nbsp;information&nbsp;contained&nbsp;in&nbsp;or&nbsp;attached&nbsp;to&nbsp;this&nbsp;electronic&nbsp;transmission<BR>&gt; 
is&nbsp;confidential&nbsp;and&nbsp;may&nbsp;be&nbsp;legally&nbsp;privileged.&nbsp;It&nbsp;is&nbsp;intended&nbsp;only&nbsp;for<BR>&gt; 
the&nbsp;person&nbsp;or&nbsp;entity&nbsp;to&nbsp;which&nbsp;it&nbsp;is&nbsp;addressed.&nbsp;If&nbsp;you&nbsp;are&nbsp;not&nbsp;the<BR>&gt; 
intended&nbsp;recipient,&nbsp;you&nbsp;are&nbsp;hereby&nbsp;notified&nbsp;that&nbsp;any&nbsp;distribution,<BR>&gt; 
copying,&nbsp;review,&nbsp;retransmission,&nbsp;dissemination&nbsp;or&nbsp;other&nbsp;use&nbsp;of&nbsp;this<BR>&gt; 
electronic&nbsp;transmission&nbsp;or&nbsp;the&nbsp;information&nbsp;contained&nbsp;in&nbsp;it&nbsp;is&nbsp;strictly<BR>&gt; 
prohibited.&nbsp;If&nbsp;you&nbsp;have&nbsp;received&nbsp;this&nbsp;electronic&nbsp;transmission&nbsp;in&nbsp;error,<BR>&gt; 
please&nbsp;immediately&nbsp;contact&nbsp;the&nbsp;sender&nbsp;to&nbsp;arrange&nbsp;for&nbsp;the&nbsp;return&nbsp;of&nbsp;the<BR>&gt; 
original&nbsp;documents.&nbsp;<BR>&gt; 
Electronic&nbsp;transmission&nbsp;cannot&nbsp;be&nbsp;guaranteed&nbsp;to&nbsp;be&nbsp;secure&nbsp;and<BR>&gt; 
accordingly,&nbsp;the&nbsp;sender&nbsp;does&nbsp;not&nbsp;accept&nbsp;liability&nbsp;for&nbsp;any&nbsp;such&nbsp;data<BR>&gt; 
corruption,&nbsp;interception,&nbsp;unauthorized&nbsp;amendment,&nbsp;viruses,&nbsp;delays&nbsp;or&nbsp;the<BR>&gt; 
consequences&nbsp;thereof.<BR>&gt; 
Any&nbsp;views&nbsp;expressed&nbsp;in&nbsp;this&nbsp;electronic&nbsp;transmission&nbsp;are&nbsp;those&nbsp;of&nbsp;the<BR>&gt; 
individual&nbsp;sender,&nbsp;except&nbsp;where&nbsp;the&nbsp;message&nbsp;states&nbsp;otherwise&nbsp;and&nbsp;the<BR>&gt; 
sender&nbsp;is&nbsp;authorized&nbsp;to&nbsp;state&nbsp;them&nbsp;to&nbsp;be&nbsp;the&nbsp;views&nbsp;of&nbsp;SAP&nbsp;AG&nbsp;or&nbsp;any&nbsp;of<BR>&gt; 
its&nbsp;subsidiaries.&nbsp;SAP&nbsp;AG,&nbsp;its&nbsp;subsidiaries,&nbsp;and&nbsp;their&nbsp;directors,<BR>&gt; 
officers&nbsp;and&nbsp;employees&nbsp;make&nbsp;no&nbsp;representation&nbsp;nor&nbsp;accept&nbsp;any&nbsp;liability<BR>&gt; 
for&nbsp;the&nbsp;accuracy&nbsp;or&nbsp;completeness&nbsp;of&nbsp;the&nbsp;views&nbsp;or&nbsp;information&nbsp;contained<BR>&gt; 
herein.&nbsp;Please&nbsp;be&nbsp;aware&nbsp;that&nbsp;the&nbsp;furnishing&nbsp;of&nbsp;any&nbsp;pricing&nbsp;information/<BR>&gt; 
business&nbsp;proposal&nbsp;herein&nbsp;is&nbsp;indicative&nbsp;only,&nbsp;is&nbsp;subject&nbsp;to&nbsp;change&nbsp;and<BR>&gt; 
shall&nbsp;not&nbsp;be&nbsp;construed&nbsp;as&nbsp;an&nbsp;offer&nbsp;or&nbsp;as&nbsp;constituting&nbsp;a&nbsp;binding<BR>&gt; 
agreement&nbsp;on&nbsp;the&nbsp;part&nbsp;of&nbsp;SAP&nbsp;AG&nbsp;or&nbsp;any&nbsp;of&nbsp;its&nbsp;subsidiaries&nbsp;to&nbsp;enter&nbsp;into<BR>&gt; 
any&nbsp;relationship,&nbsp;unless&nbsp;otherwise&nbsp;expressly&nbsp;stated.&nbsp;<BR>&gt; 
<BR>&gt; <BR>&gt; -----Original&nbsp;Message-----<BR>&gt; 
From:&nbsp;sap-wug-bounces@MIT.EDU&nbsp;[mailto:sap-wug-bounces@MIT.EDU]&nbsp;On&nbsp;Behalf<BR>&gt; 
Of&nbsp;Susan&nbsp;R.&nbsp;Keohan<BR>&gt; 
Sent:&nbsp;Wednesday,&nbsp;28&nbsp;June&nbsp;2006&nbsp;5:23&nbsp;AM<BR>&gt; 
To:&nbsp;SAP&nbsp;Workflow&nbsp;Users'&nbsp;Group<BR>&gt; 
Subject:&nbsp;Validation&nbsp;of&nbsp;selected&nbsp;substitutes&nbsp;?<BR>&gt; 
<BR>&gt; SRM&nbsp;5.0,<BR>&gt; 
Here's&nbsp;a&nbsp;weird&nbsp;one&nbsp;(what&nbsp;else&nbsp;do&nbsp;I&nbsp;ever&nbsp;send?)<BR>&gt; 
<BR>&gt; 
Certain&nbsp;approvers&nbsp;have&nbsp;strange&nbsp;and&nbsp;amazing&nbsp;powers,&nbsp;and&nbsp;it's&nbsp;important<BR>&gt; 
that&nbsp;they&nbsp;not&nbsp;select&nbsp;<BR>&gt; 
substitutes&nbsp;who&nbsp;do&nbsp;not&nbsp;also&nbsp;possess&nbsp;these&nbsp;same&nbsp;powers.&nbsp;&nbsp;Let's&nbsp;say&nbsp;these<BR>&gt; 
strange&nbsp;and&nbsp;amazing&nbsp;powers&nbsp;<BR>&gt; 
are&nbsp;manifest&nbsp;in&nbsp;SAP&nbsp;Authorizations,&nbsp;and&nbsp;SAP&nbsp;Org&nbsp;Objects,&nbsp;and&nbsp;SAP<BR>&gt; 
Qualifications&nbsp;(HR).<BR>&gt; 
We&nbsp;are&nbsp;resolving&nbsp;all&nbsp;our&nbsp;workflow&nbsp;tasks&nbsp;to&nbsp;the&nbsp;person&nbsp;level&nbsp;(positional<BR>&gt; 
substitution&nbsp;does&nbsp;not&nbsp;apply).<BR>&gt; <BR>&gt; 
Is&nbsp;there&nbsp;anyway&nbsp;to&nbsp;check&nbsp;when&nbsp;a&nbsp;user&nbsp;picks&nbsp;a&nbsp;substitute,&nbsp;that&nbsp;the<BR>&gt; 
substitute&nbsp;has&nbsp;the&nbsp;same&nbsp;attributes&nbsp;<BR>&gt; 
as&nbsp;the&nbsp;picker&nbsp;?&nbsp;&nbsp;(no&nbsp;really,&nbsp;please,&nbsp;don't&nbsp;laugh)<BR>&gt; 
<BR>&gt; Thanks!<BR>&gt; <BR>&gt; --&nbsp;<BR>&gt; 
Susan&nbsp;R.&nbsp;Keohan<BR>&gt; SAP&nbsp;Workflow&nbsp;Developer<BR>&gt; 
MIT&nbsp;Lincoln&nbsp;Laboratory<BR>&gt; 244&nbsp;Wood&nbsp;Street<BR>&gt; 
LI-200<BR>&gt; Lexington,&nbsp;MA.&nbsp;02420<BR>&gt; 781-981-3561<BR>&gt; 
keohan@ll.mit.edu<BR>&gt; <BR>&gt; 
_______________________________________________<BR>&gt; 
SAP-WUG&nbsp;mailing&nbsp;list<BR>&gt; SAP-WUG@mit.edu<BR>&gt; 
http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>&gt; <BR>&gt; <BR>&gt; 
<BR>&gt; ------------------------------<BR>&gt; <BR>&gt; Message:&nbsp;3<BR>&gt; 
Date:&nbsp;Tue,&nbsp;27&nbsp;Jun&nbsp;2006&nbsp;20:37:03&nbsp;-0500<BR>&gt; 
From:&nbsp;"D&nbsp;Duchon"&nbsp;&lt;duchond@comcast.net&gt;<BR>&gt; 
Subject:&nbsp;EBP&nbsp;Worflow&nbsp;Trigger&nbsp;issue&nbsp;with&nbsp;multiple&nbsp;lines&nbsp;in&nbsp;SC<BR>&gt; 
To:&nbsp;&lt;sap-wug@mit.edu&gt;<BR>&gt; Message-ID:<BR>&gt; 
&lt;200606280137.k5S1bAWr009677@pacific-carrier-annex.mit.edu&gt;<BR>&gt; 
Content-Type:&nbsp;text/plain;&nbsp;charset="us-ascii"<BR>&gt; <BR>&gt; 
Hello,&nbsp;&nbsp;&nbsp;I&nbsp;have&nbsp;an&nbsp;issue&nbsp;with&nbsp;EBP&nbsp;start&nbsp;conditions&nbsp;based&nbsp;on&nbsp;the&nbsp;material<BR>&gt; 
group&nbsp;(prod&nbsp;category&nbsp;in&nbsp;EBP),&nbsp;&nbsp;my&nbsp;workflow&nbsp;is&nbsp;being&nbsp;triggered&nbsp;correctly&nbsp;for<BR>&gt; 
shopping&nbsp;carts&nbsp;with&nbsp;one&nbsp;line&nbsp;item,&nbsp;But&nbsp;if&nbsp;I&nbsp;have&nbsp;a&nbsp;SC&nbsp;with&nbsp;multiple&nbsp;lines<BR>&gt; 
the&nbsp;workflow&nbsp;is&nbsp;not&nbsp;trigged.&nbsp;&nbsp;Any&nbsp;suggestions?&nbsp;&nbsp;Should&nbsp;I&nbsp;be&nbsp;using<BR>&gt; 
MaterialGroupList?&nbsp;If&nbsp;yes,&nbsp;how&nbsp;do&nbsp;you&nbsp;maintain&nbsp;a&nbsp;list.&nbsp;&nbsp;&nbsp;Using&nbsp;EBP&nbsp;v5.0<BR>&gt; 
<BR>&gt; &nbsp;<BR>&gt; <BR>&gt; Many&nbsp;thanks-<BR>&gt; <BR>&gt; 
--------------&nbsp;next&nbsp;part&nbsp;--------------<BR>&gt; 
An&nbsp;HTML&nbsp;attachment&nbsp;was&nbsp;scrubbed...<BR>&gt; 
URL:&nbsp;http://mailman.mit.edu/pipermail/sap-wug/attachments/20060627/bbdb4c6f/attachment-0001.htm<BR>&gt; 
<BR>&gt; ------------------------------<BR>&gt; <BR>&gt; Message:&nbsp;4<BR>&gt; 
Date:&nbsp;Tue,&nbsp;27&nbsp;Jun&nbsp;2006&nbsp;19:43:20&nbsp;-0700<BR>&gt; 
From:&nbsp;"jerry.martinek"&nbsp;&lt;jerry.martinek@shawbiz.ca&gt;<BR>&gt; 
Subject:&nbsp;RE:&nbsp;EP&nbsp;7.0&nbsp;UWL&nbsp;Inquiry<BR>&gt; 
To:&nbsp;"'SAP&nbsp;Workflow&nbsp;Users'&nbsp;Group'"&nbsp;&lt;sap-wug@mit.edu&gt;<BR>&gt; 
Message-ID:&nbsp;&lt;0J1J0006EU889D20@bpd2mi5no.prod.shawcable.com&gt;<BR>&gt; 
Content-Type:&nbsp;text/plain;&nbsp;charset="us-ascii"<BR>&gt; <BR>&gt; 
Hi&nbsp;Jocelyn,<BR>&gt; <BR>&gt; &nbsp;<BR>&gt; <BR>&gt; 
Thank&nbsp;for&nbsp;the&nbsp;feedback,&nbsp;I'll&nbsp;read&nbsp;up&nbsp;on&nbsp;this&nbsp;topic.<BR>&gt; 
<BR>&gt; &nbsp;<BR>&gt; <BR>&gt; Thanks,<BR>&gt; <BR>&gt; Jerry<BR>&gt; <BR>&gt; 
&nbsp;<BR>&gt; <BR>&gt; &nbsp;&nbsp;_____&nbsp;&nbsp;<BR>&gt; <BR>&gt; 
From:&nbsp;sap-wug-bounces@mit.edu&nbsp;[mailto:sap-wug-bounces@mit.edu]&nbsp;On&nbsp;Behalf&nbsp;Of<BR>&gt; 
Dart,&nbsp;Jocelyn<BR>&gt; 
Sent:&nbsp;June&nbsp;27,&nbsp;2006&nbsp;4:29&nbsp;PM<BR>&gt; 
To:&nbsp;SAP&nbsp;Workflow&nbsp;Users'&nbsp;Group<BR>&gt; 
Subject:&nbsp;RE:&nbsp;EP&nbsp;7.0&nbsp;UWL&nbsp;Inquiry<BR>&gt; <BR>&gt; 
&nbsp;<BR>&gt; <BR>&gt; Jerry,&nbsp;<BR>&gt; <BR>&gt; 
If&nbsp;you&nbsp;have&nbsp;a&nbsp;6.40&nbsp;system&nbsp;or&nbsp;above&nbsp;in&nbsp;your&nbsp;landscape&nbsp;then&nbsp;use&nbsp;Extended<BR>&gt; 
Notifications&nbsp;not&nbsp;RSWUWFML2&nbsp;-&nbsp;from&nbsp;Extended&nbsp;Notifications&nbsp;you&nbsp;could&nbsp;tailor<BR>&gt; 
the&nbsp;notifications&nbsp;to&nbsp;be&nbsp;read&nbsp;from&nbsp;all&nbsp;affected&nbsp;systems.&nbsp;<BR>&gt; 
<BR>&gt; &nbsp;<BR>&gt; <BR>&gt; 
I'm&nbsp;hoping&nbsp;to&nbsp;do&nbsp;some&nbsp;blogs&nbsp;some&nbsp;time&nbsp;on&nbsp;this&nbsp;topic&nbsp;but&nbsp;I&nbsp;want&nbsp;to&nbsp;finish&nbsp;the<BR>&gt; 
OO&nbsp;series&nbsp;first.&nbsp;<BR>&gt; <BR>&gt; &nbsp;<BR>&gt; <BR>&gt; 
&nbsp;<BR>&gt; <BR>&gt; Regards,&nbsp;<BR>&gt; Jocelyn&nbsp;Dart&nbsp;<BR>&gt; 
Senior&nbsp;Consultant&nbsp;<BR>&gt; 
SAP&nbsp;Australia&nbsp;Pty&nbsp;Ltd.&nbsp;<BR>&gt; 
Level&nbsp;1/168&nbsp;Walker&nbsp;St.&nbsp;<BR>&gt; 
North&nbsp;Sydney&nbsp;<BR>&gt; NSW,&nbsp;2060&nbsp;<BR>&gt; 
Australia&nbsp;<BR>&gt; 
T&nbsp;&nbsp;&nbsp;+61&nbsp;412&nbsp;390&nbsp;267&nbsp;<BR>&gt; 
M&nbsp;&nbsp;&nbsp;+&nbsp;61&nbsp;412&nbsp;390&nbsp;267&nbsp;<BR>&gt; 
E&nbsp;&nbsp;&nbsp;jocelyn.dart@sap.com&nbsp;<BR>&gt; 
http://www.sap.com&nbsp;&lt;http://www.sap.com/&gt;&nbsp;&nbsp;<BR>&gt; <BR>&gt; 
The&nbsp;information&nbsp;contained&nbsp;in&nbsp;or&nbsp;attached&nbsp;to&nbsp;this&nbsp;electronic&nbsp;transmission&nbsp;is<BR>&gt; 
confidential&nbsp;and&nbsp;may&nbsp;be&nbsp;legally&nbsp;privileged.&nbsp;It&nbsp;is&nbsp;intended&nbsp;only&nbsp;for&nbsp;the<BR>&gt; 
person&nbsp;or&nbsp;entity&nbsp;to&nbsp;which&nbsp;it&nbsp;is&nbsp;addressed.&nbsp;If&nbsp;you&nbsp;are&nbsp;not&nbsp;the&nbsp;intended<BR>&gt; 
recipient,&nbsp;you&nbsp;are&nbsp;hereby&nbsp;notified&nbsp;that&nbsp;any&nbsp;distribution,&nbsp;copying,&nbsp;review,<BR>&gt; 
retransmission,&nbsp;dissemination&nbsp;or&nbsp;other&nbsp;use&nbsp;of&nbsp;this&nbsp;electronic&nbsp;transmission<BR>&gt; 
or&nbsp;the&nbsp;information&nbsp;contained&nbsp;in&nbsp;it&nbsp;is&nbsp;strictly&nbsp;prohibited.&nbsp;If&nbsp;you&nbsp;have<BR>&gt; 
received&nbsp;this&nbsp;electronic&nbsp;transmission&nbsp;in&nbsp;error,&nbsp;please&nbsp;immediately&nbsp;contact<BR>&gt; 
the&nbsp;sender&nbsp;to&nbsp;arrange&nbsp;for&nbsp;the&nbsp;return&nbsp;of&nbsp;the&nbsp;original&nbsp;documents.&nbsp;<BR>&gt; 
<BR>&gt; 
Electronic&nbsp;transmission&nbsp;cannot&nbsp;be&nbsp;guaranteed&nbsp;to&nbsp;be&nbsp;secure&nbsp;and&nbsp;accordingly,<BR>&gt; 
the&nbsp;sender&nbsp;does&nbsp;not&nbsp;accept&nbsp;liability&nbsp;for&nbsp;any&nbsp;such&nbsp;data&nbsp;corruption,<BR>&gt; 
interception,&nbsp;unauthorized&nbsp;amendment,&nbsp;viruses,&nbsp;delays&nbsp;or&nbsp;the&nbsp;consequences<BR>&gt; 
thereof.<BR>&gt; <BR>&gt; 
Any&nbsp;views&nbsp;expressed&nbsp;in&nbsp;this&nbsp;electronic&nbsp;transmission&nbsp;are&nbsp;those&nbsp;of&nbsp;the<BR>&gt; 
individual&nbsp;sender,&nbsp;except&nbsp;where&nbsp;the&nbsp;message&nbsp;states&nbsp;otherwise&nbsp;and&nbsp;the&nbsp;sender<BR>&gt; 
is&nbsp;authorized&nbsp;to&nbsp;state&nbsp;them&nbsp;to&nbsp;be&nbsp;the&nbsp;views&nbsp;of&nbsp;SAP&nbsp;AG&nbsp;or&nbsp;any&nbsp;of&nbsp;its<BR>&gt; 
subsidiaries.&nbsp;SAP&nbsp;AG,&nbsp;its&nbsp;subsidiaries,&nbsp;and&nbsp;their&nbsp;directors,&nbsp;officers&nbsp;and<BR>&gt; 
employees&nbsp;make&nbsp;no&nbsp;representation&nbsp;nor&nbsp;accept&nbsp;any&nbsp;liability&nbsp;for&nbsp;the&nbsp;accuracy<BR>&gt; 
or&nbsp;completeness&nbsp;of&nbsp;the&nbsp;views&nbsp;or&nbsp;information&nbsp;contained&nbsp;herein.&nbsp;Please&nbsp;be<BR>&gt; 
aware&nbsp;that&nbsp;the&nbsp;furnishing&nbsp;of&nbsp;any&nbsp;pricing&nbsp;information/&nbsp;business&nbsp;proposal<BR>&gt; 
herein&nbsp;is&nbsp;indicative&nbsp;only,&nbsp;is&nbsp;subject&nbsp;to&nbsp;change&nbsp;and&nbsp;shall&nbsp;not&nbsp;be&nbsp;construed<BR>&gt; 
as&nbsp;an&nbsp;offer&nbsp;or&nbsp;as&nbsp;constituting&nbsp;a&nbsp;binding&nbsp;agreement&nbsp;on&nbsp;the&nbsp;part&nbsp;of&nbsp;SAP&nbsp;AG&nbsp;or<BR>&gt; 
any&nbsp;of&nbsp;its&nbsp;subsidiaries&nbsp;to&nbsp;enter&nbsp;into&nbsp;any&nbsp;relationship,&nbsp;unless&nbsp;otherwise<BR>&gt; 
expressly&nbsp;stated.&nbsp;<BR>&gt; <BR>&gt; &nbsp;<BR>&gt; <BR>&gt; 
&nbsp;<BR>&gt; <BR>&gt; &nbsp;&nbsp;_____&nbsp;&nbsp;<BR>&gt; <BR>&gt; 
From:&nbsp;sap-wug-bounces@mit.edu&nbsp;[mailto:sap-wug-bounces@mit.edu]&nbsp;On&nbsp;Behalf&nbsp;Of<BR>&gt; 
Mark&nbsp;Pyc<BR>&gt; 
Sent:&nbsp;Sunday,&nbsp;25&nbsp;June&nbsp;2006&nbsp;5:47&nbsp;PM<BR>&gt; 
To:&nbsp;SAP&nbsp;Workflow&nbsp;Users'&nbsp;Group<BR>&gt; 
Subject:&nbsp;Re:&nbsp;EP&nbsp;7.0&nbsp;UWL&nbsp;Inquiry<BR>&gt; <BR>&gt; 
G'day&nbsp;Jerry,<BR>&gt; <BR>&gt; 
I&nbsp;can&nbsp;appreciate&nbsp;that&nbsp;what&nbsp;you're&nbsp;after&nbsp;is&nbsp;an&nbsp;UWL&nbsp;equivalent&nbsp;of&nbsp;RSWUWFML2.<BR>&gt; 
i.e.&nbsp;like&nbsp;the&nbsp;UWL&nbsp;it&nbsp;would&nbsp;be&nbsp;central&nbsp;and&nbsp;only&nbsp;configured&nbsp;once&nbsp;rather&nbsp;than<BR>&gt; 
in&nbsp;each&nbsp;backend&nbsp;system,&nbsp;but&nbsp;I&nbsp;don't&nbsp;think&nbsp;such&nbsp;functionality&nbsp;exists.&nbsp;I&nbsp;think<BR>&gt; 
you&nbsp;just&nbsp;have&nbsp;to&nbsp;set&nbsp;up&nbsp;RSWUWFML2&nbsp;in&nbsp;each&nbsp;system.&nbsp;<BR>&gt; 
<BR>&gt; Have&nbsp;fun,<BR>&gt; Mark<BR>&gt; <BR>&gt; 
On&nbsp;6/25/06,&nbsp;jerry.martinek&nbsp;&lt;jerry.martinek@shawbiz.ca&gt;&nbsp;wrote:&nbsp;<BR>&gt; 
<BR>&gt; Hi&nbsp;All,<BR>&gt; <BR>&gt; &nbsp;<BR>&gt; <BR>&gt; 
Is&nbsp;it&nbsp;possible&nbsp;to&nbsp;setup&nbsp;an&nbsp;UWL&nbsp;triggered&nbsp;email&nbsp;notification&nbsp;process&nbsp;if&nbsp;the<BR>&gt; 
owner&nbsp;receives&nbsp;a&nbsp;workitem&nbsp;in&nbsp;their&nbsp;UWL?&nbsp;It's&nbsp;sort&nbsp;of&nbsp;the&nbsp;opposite<BR>&gt; 
functionality&nbsp;of&nbsp;the&nbsp;UWL&nbsp;Alerts.&nbsp;The&nbsp;goal&nbsp;is&nbsp;to&nbsp;let&nbsp;the&nbsp;selected&nbsp;person&nbsp;know<BR>&gt; 
that&nbsp;they&nbsp;have&nbsp;a&nbsp;waiting&nbsp;approval&nbsp;request&nbsp;in&nbsp;their&nbsp;UWL&nbsp;inbox.<BR>&gt; 
<BR>&gt; &nbsp;<BR>&gt; <BR>&gt; 
I've&nbsp;read&nbsp;through&nbsp;the&nbsp;documentation&nbsp;on&nbsp;the&nbsp;UWL&nbsp;but&nbsp;I&nbsp;couldn't&nbsp;find&nbsp;anything<BR>&gt; 
on&nbsp;this&nbsp;subject.<BR>&gt; <BR>&gt; &nbsp;<BR>&gt; <BR>&gt; 
Thanks,<BR>&gt; <BR>&gt; Jerry<BR>&gt; <BR>&gt; &nbsp;&nbsp;<BR>&gt; <BR>&gt; 
<BR>&gt; _______________________________________________<BR>&gt; 
SAP-WUG&nbsp;mailing&nbsp;list<BR>&gt; SAP-WUG@mit.edu<BR>&gt; 
http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>&gt; <BR>&gt; <BR>&gt; 
<BR>&gt; &nbsp;<BR>&gt; <BR>&gt; 
--------------&nbsp;next&nbsp;part&nbsp;--------------<BR>&gt; 
An&nbsp;HTML&nbsp;attachment&nbsp;was&nbsp;scrubbed...<BR>&gt; 
URL:&nbsp;http://mailman.mit.edu/pipermail/sap-wug/attachments/20060627/c008dcc8/attachment.htm<BR>&gt; 
<BR>&gt; ------------------------------<BR>&gt; <BR>&gt; 
_______________________________________________<BR>&gt; 
SAP-WUG&nbsp;mailing&nbsp;list<BR>&gt; SAP-WUG@mit.edu<BR>&gt; 
http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>&gt; <BR>&gt; <BR>&gt; 
End&nbsp;of&nbsp;SAP-WUG&nbsp;Digest,&nbsp;Vol&nbsp;19,&nbsp;Issue&nbsp;70<BR>&gt; 
***************************************<BR><BR><BR>
<HR>
La future messagerie instantanée : <A 
href="http://ideas.live.com/programpage.aspx?versionId=0eccd94b-eb48-497c-8e60-c6313f7ebb73" 
target=_new>Essayez gratuitement Windows Live Messenger Beta</A> </BODY></HTML>