<!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=362232021-14092005><FONT face=Arial
color=#0000ff size=2>Hi Matt,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=362232021-14092005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=362232021-14092005><FONT face=Arial
color=#0000ff size=2>Can you check if note 764521 has been applied to your
system. This enters function module FRE_ORD_EVENT_PO_DB into the Cange
Document entry in SWEC. I</FONT></SPAN><SPAN class=362232021-14092005><FONT
face=Arial color=#0000ff size=2>f you do NOT use Forecasting & Replenishment
the the entry in SWEC can be removed. ie. remove the entire entry from SWEC and
you should not experience the problem of deactivation. Note 797775 gives more
detail about this.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=362232021-14092005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=362232021-14092005><FONT face=Arial
color=#0000ff size=2>If this is not the issue then a problem with the data being
passed from the event container to the workflow container is most likely. e.g.
Maybe a mandatory element in the workflow container is not being
filled.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=362232021-14092005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=362232021-14092005><FONT face=Arial
color=#0000ff size=2>In order to analyse the event container you could do the
following:<BR>Define a new entry in SWE2. Enter the Event, for the receiver type
enter a user name (your user name), and for the receiver function module
enter SWE_EVENT_MAIL. You will then get the event container in an email for
every event and can see if some data is missing or corrupt.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=362232021-14092005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=362232021-14092005><FONT face=Arial
color=#0000ff size=2>Regards,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=362232021-14092005><FONT face=Arial
color=#0000ff size=2>Eddie</FONT></SPAN></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>Matt D.
Krebs<BR><B>Sent:</B> 14 September 14, 2005 21:22<BR><B>To:</B>
sap-wug@mit.edu<BR><B>Subject:</B> PO Release Strategy keeps getting
deactivated<BR></FONT><BR></DIV>
<DIV></DIV><BR><FONT face=sans-serif size=2>We are on 4.6C and are looking at
using the Standard SAP workflow for Purchase Order Release Strategy.
Everything looks like it is set up correctly, however, every time someone
posts a Purchase Order, the workflow becomes deactive. I go into
configuration transaction OOCU and activate the Workflow for release of purchase
order, but once a new PO is posted, it becomes deactive again. I tried to
troubleshoot the workflow, but it doesn't appear to kick off any tasks.
Has anyone encountered this issue before? Any advice?</FONT>
<BR><BR><FONT face=sans-serif size=2>Thanks in advance.</FONT> <BR><BR><FONT
face=sans-serif size=2>Matt Krebs<BR>NACD e-Business<BR>100 N.E. Adams
Street<BR>Peoria, IL 61629-2320<BR>309-675-1351</FONT> <BR><BR><BR>
<TABLE width="100%">
<TBODY>
<TR vAlign=top>
<TD width="40%"><FONT face=sans-serif
size=1><B>sap-wug-request@mit.edu</B> </FONT><BR><FONT face=sans-serif
size=1>Sent by: sap-wug-bounces@mit.edu</FONT>
<P><FONT face=sans-serif size=1>09/14/2005 11:10 AM</FONT>
<TABLE border=1>
<TBODY>
<TR vAlign=top>
<TD bgColor=white>
<DIV align=center><FONT face=sans-serif size=1>Please respond
to<BR>sap-wug@mit.edu</FONT></DIV></TR></TBODY></TABLE><BR></P>
<TD width="59%"><BR>
<TABLE width="100%">
<TBODY>
<TR>
<TD>
<DIV align=right><FONT face=sans-serif size=1>To</FONT> <BR><FONT
face=sans-serif size=1><U>To</U></FONT></DIV>
<TD vAlign=top><FONT face=sans-serif size=1>sap-wug@mit.edu</FONT>
<TR>
<TD>
<DIV align=right><FONT face=sans-serif size=1>cc</FONT></DIV>
<TD vAlign=top><BR><BR></TR></TBODY></TABLE><BR>
<TABLE width="100%">
<TBODY>
<TR>
<TD>
<DIV align=right><FONT face=sans-serif size=1>Subject</FONT></DIV>
<TD vAlign=top><FONT face=sans-serif size=1>SAP-WUG Digest, Vol 10,
Issue 86</FONT></TR></TBODY></TABLE><BR>
<TABLE>
<TBODY>
<TR vAlign=top>
<TD>
<TD></TR></TBODY></TABLE><BR></TR></TBODY></TABLE>
<P><FONT face=sans-serif size=1>Caterpillar: Confidential Green
Retain Until: 10/14/2005 Retention
Category: G90 - General Matters/Administration</FONT> <BR><BR><BR><FONT
size=2><TT>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: SRM approval work
item in UWL 6.0 (Bijay
Shrestha)<BR><BR><BR>----------------------------------------------------------------------<BR><BR>Date:
Wed, 14 Sep 2005 11:01:09 -0500<BR>From: "Bijay Shrestha"
<Bijay.Shrestha@genmills.com><BR>To: "SAP Workflow Users' Group"
<sap-wug@mit.edu><BR>Subject: RE: SRM approval work item in UWL
6.0<BR>Message-ID:
<2ABE45836DB5D04389DD7FE12B5E3AFD23C698@mgoex21.genmills.com><BR>Content-Type:
multipart/alternative;<BR>
boundary="----_=_NextPart_001_01C5B945.8552C16D"<BR>MIME-Version:
1.0<BR>Precedence: list<BR>Reply-To: SAP Workflow Users' Group
<sap-wug@mit.edu><BR>Message: 1<BR><BR>This is a multi-part message in
MIME format.<BR><BR>------_=_NextPart_001_01C5B945.8552C16D<BR>Content-Type:
text/plain;<BR>
charset="us-ascii"<BR>Content-Transfer-Encoding: quoted-printable<BR><BR>Hi
Monique,<BR>=20<BR>Thanks for the info. I'm now able to disable the Back
button.<BR>=20<BR>I have still not found why I don't get the "Back To Approval"
link<BR>doesn't show up in UWL. I'm still working on
it.<BR>=20<BR>Thanks.<BR><BR>Bijay
Shrestha<BR><BR><BR><BR>=20<BR><BR>________________________________<BR><BR>From:
sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On Behalf<BR>Of
Stephens, Monique S L<BR>Sent: Wednesday, September 14, 2005 10:09 AM<BR>To: SAP
Workflow Users' Group<BR>Subject: RE: SRM approval work item in UWL
6.0<BR><BR><BR>Comments from our technical person in regards to the back
button<BR>removal:<BR>=20<BR>In our portal, we use the Default Framework Page.
One of the objects<BR>provided there is the Page Title Bar. The Page
Title Bar contains<BR>History, Back, Forward, and options links for portal
navigation. In the<BR>case of the Back button, it goes back to the last
top level navigation<BR>that was selected by the user. For instance,
assume the user selected<BR>Content Administration from the top level navigation
and then clicked on<BR>Go Shopping. Then, assume they went into several
screens under the<BR>Shopping. If they then clicked the Back button on the
Page Title Bar,<BR>they would be sent back to Content Administration, not the
previous<BR>Shopping screen. In our case, we made the entire Page Title
Bar<BR>invisible to remove this Back
button.<BR>=20<BR>=20<BR><BR>________________________________<BR><BR>From:
sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On Behalf<BR>Of Bijay
Shrestha<BR>Sent: Wednesday, September 14, 2005 9:39 AM<BR>To: SAP Workflow
Users' Group<BR>Subject: RE: SRM approval work item in UWL 6.0<BR><BR><BR>Hi
Monique,<BR>=20<BR>Thanks for your quick response. I'm still struggling why
"Back to<BR>approval" link doesn't show up when I go through UWL.=20<BR>You
mentioned that you have disabled/removed Back button from the page<BR>or portal
itself. How did you do that? I didn't see any property for<BR>"Back" in UWL
iView.<BR>=20<BR>Thanks.<BR>=20<BR><BR>Bijay
Shrestha<BR><BR><BR><BR>=20<BR><BR>________________________________<BR><BR>From:
sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On Behalf<BR>Of
Stephens, Monique S L<BR>Sent: Tuesday, September 13, 2005 9:35 PM<BR>To: SAP
Workflow Users' Group; SAP Workflow Users' Group<BR>Subject: RE: SRM approval
work item in UWL 6.0<BR><BR><BR><BR>I can speak from experience that any back
button other than "back to<BR>approval" locks the users. We are struggling with
this problem right<BR>now. We just warn the users to not click any other
back button. We<BR>have even gone so far as to physically remove the back
button from the<BR>portal itself. Now, the users only have "back to
approval" and the<BR>internet back button (which they tend to click on as
well).<BR><BR>I don't believe we did anything special to make "back to
approval"<BR>appear.<BR><BR>Monique Stephens<BR><BR><BR>-----Original
Message-----<BR>From: sap-wug-bounces@mit.edu on behalf of Athur
Krishna<BR>Sent: Tue 9/13/2005 9:11 PM<BR>To: SAP Workflow Users'
Group<BR>Subject: Re: SRM approval work item in UWL 6.0<BR><BR>Hi Bijay,<BR>1)
Can you see the "Back to Inbox" link.<BR>2) Regarding Locking of users : Ideally
Portal Creates new session<BR>every<BR>time you visit the approval page, hence
even if you use back button from<BR>portal , it should ideall not get
locked.<BR>which version of EBP and Portal you are using.<BR>-Krishna<BR><BR>On
9/13/05, Bijay Shrestha <Bijay.Shrestha@genmills.com>
wrote:<BR>><BR>> Hi,<BR>><BR>> Lately I am seeing lots of SRM
related discussions in this group.<BR>><BR>> We are implementing SRM 4.0
and EBP5.0. The approval workitems are<BR>coming<BR>> to UWL fine. When we
execute the work item from UWL we get the detail<BR>of<BR>> that item where
you can approve or reject and save it. That works fine<BR>too.<BR>> The issue
is we are missing a link "Back to Approval" on top of the<BR>page.<BR>> This
is link is there if we go through SRM logon page/Approval page.<BR>><BR>>
Because this link is not there in UWL, if user decide not to
approve<BR>or<BR>> reject at that moment he can not back out. His only choice
is to use<BR>Back<BR>> button of UWL iView. That takes user back to the
screen but his work<BR>item<BR>> gets locked and can't do anything
anymore.<BR>><BR>> Have anyone seen this issue?<BR>><BR>> *Bijay
Shrestha***<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><BR><BR>------_=_NextPart_001_01C5B945.8552C16D<BR>Content-Type:
text/html;<BR>
charset="us-ascii"<BR>Content-Transfer-Encoding:
quoted-printable<BR><BR><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0
Transitional//EN"><BR><HTML><HEAD><TITLE>RE: SRM approval
work item in UWL 6.0</TITLE><BR><META http-equiv=3DContent-Type
content=3D"text/html; =<BR>charset=3Dus-ascii"><BR><META content=3D"MSHTML
6.00.2800.1515" name=3DGENERATOR></HEAD><BR><BODY><BR><DIV
dir=3Dltr align=3Dleft><SPAN class=3D443215915-14092005><FONT
=<BR>face=3DArial=20<BR>color=3D#0000ff size=3D2>Hi
Monique,</FONT></SPAN></DIV><BR><DIV dir=3Dltr
align=3Dleft><SPAN class=3D443215915-14092005><FONT
=<BR>face=3DArial=20<BR>color=3D#0000ff
size=3D2></FONT></SPAN>&nbsp;</DIV><BR><DIV
dir=3Dltr align=3Dleft><SPAN class=3D443215915-14092005><FONT
=<BR>face=3DArial=20<BR>color=3D#0000ff size=3D2>Thanks for the info. I'm now
able to disable =<BR>the
Back=20<BR>button.</FONT></SPAN></DIV><BR><DIV dir=3Dltr
align=3Dleft><SPAN class=3D443215915-14092005><FONT
=<BR>face=3DArial=20<BR>color=3D#0000ff
size=3D2></FONT></SPAN>&nbsp;</DIV><BR><DIV
dir=3Dltr align=3Dleft><SPAN class=3D443215915-14092005><FONT
=<BR>face=3DArial=20<BR>color=3D#0000ff size=3D2>I have still not found why I
don't get the =<BR>"Back To=20<BR>Approval" link doesn't show up in UWL. I'm
still working on=20<BR>it.</FONT></SPAN></DIV><BR><DIV
dir=3Dltr align=3Dleft><SPAN class=3D443215915-14092005><FONT
=<BR>face=3DArial=20<BR>color=3D#0000ff
size=3D2></FONT></SPAN>&nbsp;</DIV><BR><DIV
dir=3Dltr align=3Dleft><SPAN class=3D443215915-14092005><FONT
=<BR>face=3DArial=20<BR>color=3D#0000ff
size=3D2>Thanks.</FONT></SPAN></DIV><!-- Converted from
= text/rtf format --><BR><P><SPAN
lang=3Den-us><B><I><FONT face=3DScript color=3D#008080
=<BR>size=3D5>Bijay=20<BR>Shrestha</FONT></I></B><I></I><FONT
face=3D"Times New
Roman"=20<BR>size=3D5></FONT><BR></SPAN></P><BR><BR><DIV>&nbsp;</DIV><BR><BR><DIV
class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft><BR><HR
tabIndex=3D-1><BR><FONT face=3DTahoma size=3D2><B>From:</B>
sap-wug-bounces@mit.edu=20<BR>[mailto:sap-wug-bounces@mit.edu] <B>On
Behalf Of </B>Stephens, Monique S
=<BR><BR>L<BR><B>Sent:</B> Wednesday, September 14, 2005 10:09
AM<BR><B>To:</B> =<BR>SAP=20<BR>Workflow Users'
Group<BR><B>Subject:</B> RE: SRM approval work item in
=<BR>UWL=20<BR>6.0<BR></FONT><BR></DIV><BR><DIV></DIV><BR><DIV
dir=3Dltr align=3Dleft><SPAN class=3D285320715-14092005><FONT
=<BR>face=3DArial=20<BR>color=3D#0000ff size=3D2>Comments from our technical
person in regards =<BR>to the back=20<BR>button
removal:</FONT></SPAN></DIV><BR><DIV dir=3Dltr
align=3Dleft><SPAN class=3D285320715-14092005><FONT
=<BR>face=3DArial=20<BR>color=3D#0000ff
size=3D2></FONT></SPAN>&nbsp;</DIV><BR><DIV
dir=3Dltr align=3Dleft><SPAN class=3D285320715-14092005><BR><DIV
dir=3Dltr align=3Dleft><SPAN class=3D738340515-14092005><FONT
=<BR>face=3DArial=20<BR>color=3D#0000ff size=3D2>In our portal, we use the
Default Framework =<BR>Page.&nbsp; One=20<BR>of the objects provided there
is the Page Title Bar.&nbsp; The Page =<BR>Title Bar=20<BR>contains
</FONT></SPAN><SPAN class=3D738340515-14092005><FONT
=<BR>face=3DArial=20<BR>color=3D#0000ff size=3D2>History,
Back,&nbsp;Forward, and options links =<BR>for
portal=20<BR>navigation.&nbsp; In the case of the Back button,&nbsp;it
goes =<BR>back&nbsp;to the=20<BR>last top level navigation that was selected
by the user.&nbsp; For=20<BR>instance,&nbsp;assume the user selected
Content Administration from the =<BR>top=20<BR>level navigation and then clicked
on Go Shopping.&nbsp; Then, assume=20<BR>they&nbsp;went into several
screens under the Shopping.&nbsp; If they =<BR>then=20<BR>clicked the Back
button on the Page Title Bar, they would be sent back =<BR>to=20<BR>Content
Administration, not the previous Shopping
screen.&nbsp;=20<BR></FONT></SPAN><SPAN
class=3D738340515-14092005><FONT face=3DArial
=<BR>color=3D#0000ff=20<BR>size=3D2>In our case, we made the entire Page
Title Bar invisible to =<BR>remove this=20<BR>Back
button.</FONT></SPAN></DIV><BR><DIV>&nbsp;</DIV><BR><DIV><FONT
face=3DArial><FONT color=3D#0000ff><FONT
size=3D2><SPAN=20<BR>class=3D738340515-14092005></SPAN></FONT></FONT></FONT>&nbsp;</DIV></SPAN=<BR>></DIV><BR><BR><DIV
class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft><BR><HR
tabIndex=3D-1><BR><FONT face=3DTahoma size=3D2><B>From:</B>
sap-wug-bounces@mit.edu=20<BR>[mailto:sap-wug-bounces@mit.edu] <B>On
Behalf Of </B>Bijay=20<BR>Shrestha<BR><B>Sent:</B>
Wednesday, September 14, 2005 9:39 =<BR>AM<BR><B>To:</B>
SAP=20<BR>Workflow Users' Group<BR><B>Subject:</B> RE: SRM
approval work item in
=<BR>UWL=20<BR>6.0<BR></FONT><BR></DIV><BR><DIV></DIV><BR><DIV
dir=3Dltr align=3Dleft><SPAN class=3D001563514-14092005><FONT
=<BR>face=3DArial=20<BR>color=3D#0000ff size=3D2>Hi
Monique,</FONT></SPAN></DIV><BR><DIV dir=3Dltr
align=3Dleft><SPAN class=3D001563514-14092005><FONT
=<BR>face=3DArial=20<BR>color=3D#0000ff
size=3D2></FONT></SPAN>&nbsp;</DIV><BR><DIV
dir=3Dltr align=3Dleft><SPAN class=3D001563514-14092005><FONT
=<BR>face=3DArial=20<BR>color=3D#0000ff size=3D2>Thanks for your quick
response. I'm still =<BR>struggling why=20<BR>"Back to approval" link doesn't
show up when I go through
UWL.=20<BR></FONT></SPAN></DIV><BR><DIV dir=3Dltr
align=3Dleft><SPAN class=3D001563514-14092005><FONT
=<BR>face=3DArial=20<BR>color=3D#0000ff size=3D2>You mentioned that you have
disabled/removed =<BR>Back button=20<BR>from the page or portal itself. How did
you do that? I didn't see any =<BR>property=20<BR>for "Back"&nbsp;in UWL
iView.</FONT></SPAN></DIV><BR><DIV dir=3Dltr
align=3Dleft><SPAN class=3D001563514-14092005><FONT
=<BR>face=3DArial=20<BR>color=3D#0000ff
size=3D2></FONT></SPAN>&nbsp;</DIV><BR><DIV
dir=3Dltr align=3Dleft><SPAN class=3D001563514-14092005><FONT
=<BR>face=3DArial=20<BR>color=3D#0000ff
size=3D2>Thanks.</FONT></SPAN></DIV><BR><DIV>&nbsp;</DIV><!--
Converted from text/rtf format --><BR><P><SPAN
lang=3Den-us><B><I><FONT face=3DScript color=3D#008080
=<BR>size=3D5>Bijay=20<BR>Shrestha</FONT></I></B><I></I><FONT
face=3D"Times New
Roman"=20<BR>size=3D5></FONT><BR></SPAN></P><BR><BR><DIV>&nbsp;</DIV><BR><BR><DIV
class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft><BR><HR
tabIndex=3D-1><BR><FONT face=3DTahoma size=3D2><B>From:</B>
sap-wug-bounces@mit.edu=20<BR>[mailto:sap-wug-bounces@mit.edu] <B>On
Behalf Of </B>Stephens, Monique S
=<BR><BR>L<BR><B>Sent:</B> Tuesday, September 13, 2005 9:35
PM<BR><B>To:</B> SAP =<BR>Workflow=20<BR>Users' Group; SAP
Workflow Users' Group<BR><B>Subject:</B> RE: SRM =<BR>approval
work=20<BR>item in UWL
6.0<BR></FONT><BR></DIV><BR><DIV></DIV><!--
Converted from text/plain format --><BR><P><FONT size=3D2>I can
speak from experience that any back button other =<BR>than=20<BR>"back to
approval" locks the users. We are struggling with this problem
=<BR>right=20<BR>now.&nbsp; We just warn the users to not click any other
back =<BR>button.&nbsp; We=20<BR>have even gone so far as to physically
remove the back button from the =<BR>portal=20<BR>itself.&nbsp; Now, the
users only have "back to approval" and the =<BR>internet back=20<BR>button
(which they tend to click on as well).<BR><BR>I don't believe we
=<BR>did=20<BR>anything special to make "back to approval"
appear.<BR><BR>Monique=20<BR>Stephens<BR><BR><BR>-----Original
Message-----<BR>From: =<BR>sap-wug-bounces@mit.edu=20<BR>on behalf of
Athur Krishna<BR>Sent: Tue 9/13/2005 9:11 PM<BR>To: SAP
=<BR>Workflow=20<BR>Users' Group<BR>Subject: Re: SRM approval work item in
UWL 6.0<BR><BR>Hi =<BR><BR>Bijay,<BR>&nbsp;1) Can you see
the "Back to Inbox" link.<BR>&nbsp;2) =<BR>Regarding=20<BR>Locking of
users : Ideally Portal Creates new session every<BR>time you
=<BR>visit=20<BR>the approval page, hence even if you use back button
from<BR>portal , it =<BR>should=20<BR>ideall not get
locked.<BR>&nbsp;which version of EBP and Portal you
are=20<BR>using.<BR>&nbsp;-Krishna<BR><BR>&nbsp;On
9/13/05, Bijay Shrestha=20<BR>&lt;Bijay.Shrestha@genmills.com&gt;
wrote:<BR>&gt;<BR>&gt;
=<BR>Hi,<BR>&gt;<BR>&gt;=20<BR>Lately I am seeing lots of
SRM related discussions in this=20<BR>group.<BR>&gt;<BR>&gt;
We are implementing SRM 4.0 and EBP5.0. The =<BR>approval=20<BR>workitems are
coming<BR>&gt; to UWL fine. When we execute the work item =<BR>from
UWL=20<BR>we get the detail of<BR>&gt; that item where you can approve
or reject =<BR>and save=20<BR>it. That works fine too.<BR>&gt; The
issue is we are missing a link =<BR>"Back to=20<BR>Approval" on top of the
page.<BR>&gt; This is link is there if we go =<BR>through
SRM=20<BR>logon page/Approval page.<BR>&gt;<BR>&gt; Because
this link is not there =<BR>in UWL,=20<BR>if user decide not to approve
or<BR>&gt; reject at that moment he can =<BR>not back=20<BR>out. His
only choice is to use Back<BR>&gt; button of UWL iView. That
=<BR>takes user=20<BR>back to the screen but his work item<BR>&gt;
gets locked and can't do
=<BR>anything=20<BR>anymore.<BR>&gt;<BR>&gt; Have anyone
seen this issue?<BR>&gt;<BR>&gt;
=<BR>*Bijay=20<BR>Shrestha***<BR>&gt;<BR>&gt;<BR>&gt;=20<BR>_______________________________________________<BR>&gt;
SAP-WUG mailing=20<BR>list<BR>&gt; SAP-WUG@mit.edu<BR>&gt;
<A=20<BR>href=3D"http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.m=<BR>it.edu/mailman/listinfo/sap-wug</A><BR>&gt;<BR>&gt;<BR>&gt;<BR><BR></FONT=<BR>></P></BODY></HTML><BR><BR>------_=_NextPart_001_01C5B945.8552C16D--<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 10, Issue
86<BR>***************************************<BR></TT></FONT><BR></P></BODY></HTML>