<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2800.1515" name=GENERATOR></HEAD>
<BODY text=#000000 bgColor=#ffffff>
<DIV dir=ltr align=left><SPAN class=770465214-26092005><FONT face=Arial
color=#0000ff size=2>Yes Sue - you should make sure only one workflow starts for
a particular contract and the event SAVED or CHANGEVERSIONSAVED. Your conditions
should be mutually exclusive. </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=770465214-26092005><FONT face=Arial
color=#0000ff size=2>You can have the same contract go to different workflows
for SAVED versus CHANGEVERSIONSAVED - that's fine. </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=770465214-26092005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=770465214-26092005><FONT face=Arial
color=#0000ff size=2>This is not just a technical restriction - it's
logically what must happen - i.e. only one contract approval workflow must be
active for a particular contract at any one time.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=770465214-26092005></SPAN><SPAN
class=770465214-26092005></SPAN><SPAN class=770465214-26092005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV>
<DIV dir=ltr align=left><SPAN class=770465214-26092005><FONT face=Arial
color=#0000ff size=2>Woah - just looked at the workflows - you should not be
turning on the WS14000084 Update Contract after Approval workflow anyway -
that's a subworkflow! That doesn't even have the SAVED or CHANGEVERSIONSAVED
events in standard! Someone's been modifying.... get them to fix it before
it causes more problems. </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=770465214-26092005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=770465214-26092005><FONT face=Arial
color=#0000ff size=2><SPAN class=770465214-26092005><FONT face=Arial
color=#0000ff size=2>Please re-educate your SRM consultant.
</FONT></SPAN></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=770465214-26092005><FONT face=Arial
color=#0000ff size=2><SPAN
class=770465214-26092005></SPAN></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=770465214-26092005><FONT face=Arial
color=#0000ff size=2>You only turn on the main workflows - WS14000086,
WS14000088, WS14000148, etc. </FONT></SPAN></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>Susan R.
Keohan<BR><B>Sent:</B> Tuesday, 27 September 2005 12:30 AM<BR><B>To:</B> SAP
Workflow Users' Group<BR><B>Subject:</B> Re: WS14000084 for contracts on SRM 4.0
not starting<BR></FONT><BR></DIV>
<DIV></DIV>Hi All,<BR><BR>The IMG for SRM 4.0 says <BR><BR>'Make sure that only
<B>one</B> workflow is started for each requirement coverage request, that means
you must formulate the conditions in such a way that a requirement coverage
request cannot fulfill more than one condition.'. <BR><BR>Even though this
is regarding requirement coverage requests, would this same rule hold true for
Contracts ?<BR><BR>Has anyone turned on the standard WFs for contracts in SRM
? If so, did you turn on WS14000086, or WS14000084 ? Our SRM
consultant has the start conditions for *both* workflows turned on.<BR><BR>Still
fishing, hoping for a nibble...<BR>Sue<BR><BR>Susan R. Keohan wrote:<BR>
<BLOCKQUOTE cite=mid43342537.7020104@ll.mit.edu type="cite">Hello all,
<BR><BR>This question is being posed from an old R/3 Workflow-er, so please
excuse my lack of knowledge about SRM. <BR><BR>We have upgraded from EBP 3.5
to SRM 4.0 in our sandbox environment. This our landscape:
<BR>SAP_BASIS
640 SAPKB64011
<BR>SAP_ABA
640 SAPKA64011
<BR>SRM_SERVER 500
SAPKIBKS06 <BR><BR>Our SRM consultant has enabled (via SPRO and SWB_COND) the
standard SAP workflow WS14000084 and WS14000086 for BUS2000113, events
CHANGEVERSIONSAVED and SAVED. <BR>Example of Start Conditions is
attached. All the 'normal' workflow customizing has been carried out via
SWU3. Event log is turned on. Event linkage is activated, and the
check functions are <BR>SWB_2_CHECK_FB_START_COND_EVAL (WS14000084) and
SWB_CHECK_FB_START_COND_EVAL (WS14000086). <BR><BR>The contract is created,
but of course, no workflow starts. Why else would I be annoying you with
this on a Friday. <BR><BR>SWUD for WS14000084 gives yellow lights on the
binding between task and event. Simulate Event gives red light for
WS14000084, green light for WS14000086. The information on WS14000084 is
that there is an error in the binding definition. <BR><BR>OSS Note 879528
refers to this workflow (WS14000084) in a different context, but suggests
changing the binding. Okay, I know how to do that, but step 7 of this
note says to change the binding to.... <BR><BR>then there is nothing. No
information on what the binding should be changed *to*. <BR><BR>Can anyone
shed some light on: <BR>What the correct binding for this task should be ?
<BR>How to tell if the event is raised. I know in SRM that the standard
event log will not help. <BR>What is the difference (in a nutshell) between
the two check functions ? Why use one over the other ? <BR>Any other tips and
tricks to teach this old dog would be helpful. <BR><BR>Thanks! <BR>Sue
<BR><BR><BR>
<HR width="90%" SIZE=4>
<BR>
<CENTER><IMG src="cid:770465214@26092005-238C"></CENTER><PRE wrap=""><HR width="90%" SIZE=4>
_______________________________________________
SAP-WUG mailing list
<A class=moz-txt-link-abbreviated href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</A>
<A class=moz-txt-link-freetext href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</A>
</PRE></BLOCKQUOTE><BR><PRE class=moz-signature cols="100">--
Susan R. Keohan
SAP Workflow Developer
MIT Lincoln Laboratory
244 Wood Street
LI-200
Lexington, MA. 02420
781-981-3561
<A class=moz-txt-link-abbreviated href="mailto:keohan@ll.mit.edu">keohan@ll.mit.edu</A>
</PRE></BODY></HTML>