<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.6000.16640" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#fafafa>
<DIV><FONT face=Arial size=2>welcome...</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>I would use of copy of the standard template
anyway, but it seems that the one having the higher number, is the newer one,
even though they look just the same to me.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Best wishes,</FONT></DIV>
<DIV><FONT face=Arial size=2>Florin</FONT></DIV>
<BLOCKQUOTE
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=jhoworth@csc.com href="mailto:jhoworth@csc.com">John A Haworth</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=sap-wug@mit.edu
href="mailto:sap-wug@mit.edu">SAP Workflow Users' Group</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Wednesday, April 23, 2008 12:31
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: Pur req-release wrkflw</DIV>
<DIV><BR></DIV><BR><FONT face=sans-serif size=2>Thanks again for your fast
response & info.</FONT> <BR><BR><FONT face=sans-serif size=2>Should I be
using 00000038 or 20000077?</FONT> <BR><BR><FONT face=sans-serif
size=2>John<BR><BR>CSC Computer Sciences Limited<BR>Registered Office: Royal
Pavilion, Wellesley Road, Aldershot, Hampshire, GU11 1PZ, UK<BR>Registered in
England No:
0963578<BR><BR>-------------------------------------------------------------------------------------------------------------------------------------------------------------------------<BR>This
is a PRIVATE message. If you are not the intended recipient, please delete
without copying and kindly advise us by e-mail of the mistake in delivery.
<BR>NOTE: Regardless of content, this e-mail shall not operate to bind CSC to
any order or other contract unless pursuant to explicit written agreement or
government initiative expressly permitting the use of e-mail for such
purpose.<BR>-------------------------------------------------------------------------------------------------------------------------------------------------------------------------<BR></FONT><BR><BR><BR>
<TABLE width="100%">
<TBODY>
<TR vAlign=top>
<TD width="40%"><FONT face=sans-serif size=1><B>"Florin Wach"
<florin.wach@gmx.net></B> </FONT><BR><FONT face=sans-serif
size=1>Sent by: sap-wug-bounces@mit.edu</FONT>
<P><FONT face=sans-serif size=1>23/04/2008 10:43</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 Workflow Users' Group"
<sap-wug@mit.edu></FONT></DIV></TR></TBODY></TABLE><BR></P>
<TD width="59%">
<TABLE width="100%">
<TBODY>
<TR vAlign=top>
<TD>
<DIV align=right><FONT face=sans-serif size=1>To</FONT></DIV>
<TD><FONT face=sans-serif size=1>"SAP Workflow Users' Group"
<sap-wug@mit.edu></FONT>
<TR vAlign=top>
<TD>
<DIV align=right><FONT face=sans-serif size=1>cc</FONT></DIV>
<TD>
<TR vAlign=top>
<TD>
<DIV align=right><FONT face=sans-serif size=1>Subject</FONT></DIV>
<TD><FONT face=sans-serif size=1>Re: Pur req-release
wrkflw</FONT></TR></TBODY></TABLE><BR>
<TABLE>
<TBODY>
<TR vAlign=top>
<TD>
<TD></TR></TBODY></TABLE><BR></TR></TBODY></TABLE><BR><BR><BR><FONT
size=2><TT>Jup,<BR><BR>this seems to be not working a 100% as
designed.<BR><BR>I usually deselect the SignificantlyChanged event as the
terminating event in the workflow pattern (as a copy from the SAP's original),
as that event is always accompanied by the .Rejection_start.<BR><BR>Also the
(newer?) template WS20000077 has the same thing.<BR><BR>If you'd like to avoid
that, you could also use a check-function module in the instance coupling of
the task TS20000159 that avoids the event .SignificantlyChanged of beeing
processed. Or you'd add a info-rejection as the first step in the rejection
flow.<BR><BR>Best wishes,<BR>Florin<BR><BR><BR>-------- Original-Nachricht
--------<BR>> Datum: Wed, 23 Apr 2008 10:22:54 +0100<BR>> Von: John A
Haworth <jhoworth@csc.com><BR>> An: "SAP Workflow Users\' Group"
<sap-wug@mit.edu><BR>> Betreff: Pur req-release wrkflw<BR><BR>>
Thanks for that info.<BR>> <BR>> Continuing on the same workflow. I have
an issue with the way this seems <BR>> to be working, could someone please
comment?<BR>> <BR>> It seems that when the Pur Req is created and saved,
WS0000038 is <BR>> triggered ok, and the approve request is sent to the
correct Responsible <BR>> Agent. If that agent then Approves the PReq, the
workflow works correctly <BR>> and the initiator is informed via a wflw
task from WS0000038. But if the <BR>> agents rejects the Preq, then event
'SIGNIFICANTLYCHANGED' is raised which<BR>> cancels down the initial
workflow (WS0000038), together with a second <BR>> event
REJECTION_START which then triggers a new single step workflow
<BR>> (WS65400027)<BR>> <BR>> This doesnt look correct, as cancelling
down the initial workflow, means <BR>> that the task 'Negative
Confirmation' in WS0000038 doesnt get touched and <BR>> therefore isnt sent
to the initiator (whereas the positive confirmation <BR>> task is run when
the Agent approves)<BR>> <BR>> WS65400027 then waits for the event
REJECTION_STOP as a terminating event,<BR>> but the initiator is never
informed.<BR>> <BR>> Many Thanks<BR>> <BR>> John<BR>> <BR>>
<BR>> <BR>> CSC Computer Sciences Limited<BR>> Registered Office:
Royal Pavilion, Wellesley Road, Aldershot, Hampshire, <BR>> GU11 1PZ,
UK<BR>> Registered in England No: 0963578<BR>> <BR>>
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------<BR>>
This is a PRIVATE message. If you are not the intended recipient, please
<BR>> delete without copying and kindly advise us by e-mail of the mistake
in <BR>> delivery. <BR>> NOTE: Regardless of content, this e-mail shall
not operate to bind CSC to <BR>> any order or other contract unless
pursuant to explicit written agreement <BR>> or government initiative
expressly permitting the use of e-mail for such <BR>> purpose.<BR>>
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------<BR>>
<BR>> <BR>> <BR>> <BR>> "Florin Wach (gmx)"
<florin.wach@gmx.net> <BR>> Sent by: sap-wug-bounces@mit.edu<BR>>
21/04/2008 17:39<BR>> Please respond to<BR>> "SAP Workflow Users' Group"
<sap-wug@mit.edu><BR>> <BR>> <BR>> To<BR>> "SAP Workflow
Users' Group" <sap-wug@mit.edu><BR>> cc<BR>> <BR>>
Subject<BR>> Re: user exit on Pur req-release wrkflw<BR>> <BR>>
<BR>> <BR>> <BR>> <BR>> <BR>> Hi John,<BR>> <BR>>
if the box "Assigned agent" is left blank, der Task's standard role <BR>>
resolution is used, which is, what's exactly happening there.<BR>>
<BR>> Look at the Task definition of TS... under "Rules".<BR>>
<BR>> Best wishes,<BR>> Florin<BR>> ----- Original Message
----- <BR>> From: John A Haworth <BR>> To: SAP Workflow Users' Group
<BR>> Sent: Monday, April 21, 2008 4:49 PM<BR>> Subject: user exit on
Pur req-release wrkflw<BR>> <BR>> <BR>> Hi <BR>> <BR>> I am
looking at a clients already created workflows. One is the purchase <BR>>
requisition release standard workflow WS00000038. They have the purchase
<BR>> reqs configured to use the LXM06U12 Customer enhancement to look in a
<BR>> customer table for the approver name, that all looks ok. <BR>> But
the first step in the workflow that sends the approval request to the <BR>>
approver, has no entry in the 'Responsible Agents' entry box. Yet the <BR>>
workflow seems to be sending to the right person?? Surely this is not <BR>>
right, and my mental block thats happening more frequently is not
helping!<BR>> Any advice? <BR>> <BR>> John<BR>> <BR>> CSC
Computer Sciences Limited<BR>> Registered Office: Royal Pavilion, Wellesley
Road, Aldershot, Hampshire, <BR>> GU11 1PZ, UK<BR>> Registered in
England No: 0963578<BR>> <BR>>
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------<BR>>
This is a PRIVATE message. If you are not the intended recipient, please
<BR>> delete without copying and kindly advise us by e-mail of the mistake
in <BR>> delivery. <BR>> NOTE: Regardless of content, this e-mail shall
not operate to bind CSC to <BR>> any order or other contract unless
pursuant to explicit written agreement <BR>> or government initiative
expressly permitting the use of e-mail for such <BR>> purpose.<BR>>
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------<BR>>
<BR>> _______________________________________________<BR>> SAP-WUG
mailing list<BR>> SAP-WUG@mit.edu<BR>>
http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>>
_______________________________________________<BR>> SAP-WUG mailing
list<BR>> SAP-WUG@mit.edu<BR>>
http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>>
<BR>_______________________________________________<BR>SAP-WUG mailing
list<BR>SAP-WUG@mit.edu<BR>http://mailman.mit.edu/mailman/listinfo/sap-wug<BR></TT></FONT><BR>
<P>
<HR>
<P></P>_______________________________________________<BR>SAP-WUG mailing
list<BR>SAP-WUG@mit.edu<BR>http://mailman.mit.edu/mailman/listinfo/sap-wug<BR></BLOCKQUOTE></BODY></HTML>