<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Times New Roman","serif";
color:black;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='color:black'>Hi Andy,<o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>We *<b>never</b>* take SAP’s advice ;-)<o:p></o:p></span></p><p class=MsoNormal><span style='color:black'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:black'>We are using the same custom workflow templates that we used in SRM5. But the Check FM ‘works’ – it just gives the end user that nasty-gram.<o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>The old WFs were too complex to have been converted to PC during this particular upgrade. (Looking forward to THAT effort too!).<o:p></o:p></span></p><p class=MsoNormal><span style='color:black'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:black'>Thanks for your feedback!<o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>Sue<o:p></o:p></span></p><p class=MsoNormal><span style='color:black'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] <b>On Behalf Of </b>Andy Curtis<br><b>Sent:</b> Tuesday, September 30, 2014 11:15 AM<br><b>To:</b> SAP Workflow Users' Group<br><b>Subject:</b> Check FM in SRM7 (Keohan, Susan - 1140 - MITLL)<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>Sue<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Why do you have a custom check FM? If your taking the SAP advice and 'not modified' the SAP templates then you shouldn't ever get duplicate Wf's. We don't and we have gone from SRM5 to SRM7 AC Wf. <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Thinking, SAP actually start a Waiting status Wf when you make a change to a PO/SC and SAVE it. They use it to record the Approval chain and display it in the Approval Preview.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Andy <o:p></o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p><div><p class=MsoNormal>On Tue, Sep 30, 2014 at 3:43 PM, <<a href="mailto:sap-wug-request@mit.edu" target="_blank">sap-wug-request@mit.edu</a>> wrote:<o:p></o:p></p><p class=MsoNormal>Send SAP-WUG mailing list submissions to<br> <a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a><br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> <a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>or, via email, send a message with subject or body 'help' to<br> <a href="mailto:sap-wug-request@mit.edu">sap-wug-request@mit.edu</a><br><br>You can reach the person managing the list at<br> <a href="mailto:sap-wug-owner@mit.edu">sap-wug-owner@mit.edu</a><br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of SAP-WUG digest..."<br><br>Today's Topics:<br><br> 1. Check FM in SRM7 (Keohan, Susan - 1140 - MITLL)<br><br><br>---------- Forwarded message ----------<br>From: "Keohan, Susan - 1140 - MITLL" <<a href="mailto:keohan@ll.mit.edu">keohan@ll.mit.edu</a>><br>To: "SAP Workflow Users' Group (<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>)" <<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>><br>Cc: <br>Date: Tue, 30 Sep 2014 14:42:07 +0000<br>Subject: Check FM in SRM7<o:p></o:p></p><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:black'>Hi all,</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:black'>We’re upgrading to SRM7 (technical only) from SRM5 and using our old Application Controlled Workflows.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:black'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:black'>We’ve always used a Check Function Module in the Event Linkage table to prevent multiple workflows from kicking off for Purchase Order Change Versions if the same GUID is already involved in an active workflow process. </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:black'>So if the Check Function module (referenced in SWETYPV) finds an active workflow using that PO GUID, it exits gracefully with our friendly exception NO_WORKFLOW.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:black'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:black'>In SRM7, however, this is interpreted as something completely different in the PDO layer…</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:black'>A very nasty error is displayed to the user:</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><img border=0 width=736 height=192 id="_x0000_i1025" src="cid:image001.png@01CFDCA4.9D516C20"><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:black'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:black'>Has anyone else had to change their methodology of using Check FMs in SRM7? I know I can put a task in the workflow to check for other flows on the same GUID, but Check FMs seemed to work so nicely before.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:black'><br>Thanks in advance,<br>Sue</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:black'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:black'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:black'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:black'>Susan R. Keohan</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:black'>SAP Workflow Specialist</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:black'>MIT Lincoln Laboratory</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:black'>244 Wood Street, LI-200</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:black'>Lexington, MA. 02420</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:black'><a href="tel:781-981-3561" target="_blank">781-981-3561</a></span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:black'>@skeohan</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div></div><p class=MsoNormal style='margin-bottom:12.0pt'><br>_______________________________________________<br>SAP-WUG mailing list<br><a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p></div></div></div></body></html>