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