<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:x="urn:schemas-microsoft-com:office:excel" 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=us-ascii"><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;}
@font-face
        {font-family:"Comic Sans MS";
        panose-1:3 15 7 2 3 3 2 2 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.EmailStyle17
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.BalloonTextChar
        {mso-style-name:"Balloon Text Char";
        mso-style-priority:99;
        mso-style-link:"Balloon Text";
        font-family:"Tahoma","sans-serif";}
span.l0s521
        {mso-style-name:l0s521;
        font-family:"Courier New";
        color:blue;
        background:white;}
span.l0s331
        {mso-style-name:l0s331;
        font-family:"Courier New";
        color:#4DA619;
        background:white;}
span.l0s551
        {mso-style-name:l0s551;
        font-family:"Courier New";
        color:purple;
        background:white;}
span.l0s701
        {mso-style-name:l0s701;
        font-family:"Courier New";
        color:gray;
        background:white;}
span.l0s321
        {mso-style-name:l0s321;
        font-family:"Courier New";
        color:#3399FF;
        background:white;}
.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='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Mark,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Thank you for pointing this out. I changed my message number to 001 and I am now getting my warning messages!<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><img width=785 height=301 id="Picture_x0020_1" src="cid:image005.png@01CEF691.F62713D0"></span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>And to Rick’s point about debugging the method: I did that and I noticed some odd behavior in our Purchase Order workflow (BUS2012). The BAPI that is used to release the PO has a parameter that basically tells the BAPI if any exceptions are going to be raised:<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span class=l0s521><span style='font-size:10.0pt'>CALL FUNCTION </span></span><span class=l0s331><span style='font-size:10.0pt'>'BAPI_PO_RELEASE'</span></span><span style='font-size:10.0pt;font-family:"Courier New";color:black;background:white'><br> </span><span class=l0s521><span style='font-size:10.0pt'>EXPORTING</span></span><span style='font-size:10.0pt;font-family:"Courier New";color:black;background:white'><br> <span style='background:yellow;mso-highlight:yellow'>use_exceptions </span></span><span class=l0s551><span style='font-size:10.0pt;background:yellow;mso-highlight:yellow'>= </span></span><span style='font-size:10.0pt;font-family:"Courier New";color:black;background:yellow;mso-highlight:yellow'>useexceptions</span><span style='font-size:10.0pt;font-family:"Courier New";color:black;background:white'><br> po_rel_code </span><span class=l0s551><span style='font-size:10.0pt'>= </span></span><span style='font-size:10.0pt;font-family:"Courier New";color:black;background:white'>relcode<br> no_commit </span><span class=l0s551><span style='font-size:10.0pt'>= </span></span><span style='font-size:10.0pt;font-family:"Courier New";color:black;background:white'>nocommit<br> purchaseorder </span><span class=l0s551><span style='font-size:10.0pt'>= </span></span><span style='font-size:10.0pt;font-family:"Courier New";color:black;background:white'>object</span><span class=l0s701><span style='font-size:10.0pt'>-</span></span><span class=l0s521><span style='font-size:10.0pt'>key</span></span><span class=l0s701><span style='font-size:10.0pt'>-</span></span><span style='font-size:10.0pt;font-family:"Courier New";color:black;background:white'>purchaseorder<br> </span><span class=l0s521><span style='font-size:10.0pt'>IMPORTING...<o:p></o:p></span></span></p><p class=MsoNormal><span class=l0s521><span style='font-size:10.0pt'><o:p> </o:p></span></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>If this parameter is not populated with an “X”, the BAPI will not raise any exceptions at all.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I then saw this code at the beginning of the PO Release method:<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New";color:black;background:white'>swc_get_element container </span><span class=l0s331><span style='font-size:10.0pt'>'RelCode' </span></span><span style='font-size:10.0pt;font-family:"Courier New";color:black;background:white'>relcode</span><span class=l0s551><span style='font-size:10.0pt'>.</span></span><span style='font-size:10.0pt;font-family:"Courier New";color:black;background:white'><br>swc_get_element container </span><span class=l0s331><span style='font-size:10.0pt'>'UseExceptions' </span></span><span style='font-size:10.0pt;font-family:"Courier New";color:black;background:white'>useexceptions</span><span class=l0s551><span style='font-size:10.0pt'>.</span></span><span style='font-size:10.0pt;font-family:"Courier New";color:black;background:white'><br>swc_get_element container </span><span class=l0s331><span style='font-size:10.0pt'>'NoCommit' </span></span><span style='font-size:10.0pt;font-family:"Courier New";color:black;background:white'>nocommit</span><span class=l0s551><span style='font-size:10.0pt'>.</span></span><span style='font-size:10.0pt;font-family:"Courier New";color:black;background:white'><br></span><span class=l0s521><span style='font-size:10.0pt'>IF </span></span><span style='font-size:10.0pt;font-family:"Courier New";color:black;background:white'>sy</span><span class=l0s701><span style='font-size:10.0pt'>-</span></span><span style='font-size:10.0pt;font-family:"Courier New";color:black;background:white'>subrc <> </span><span class=l0s321><span style='font-size:10.0pt'>0</span></span><span class=l0s551><span style='font-size:10.0pt'>.</span></span><span style='font-size:10.0pt;font-family:"Courier New";color:black;background:white'><br> </span><span class=l0s521><span style='font-size:10.0pt'>MOVE </span></span><span class=l0s331><span style='font-size:10.0pt'>'X' </span></span><span class=l0s521><span style='font-size:10.0pt'>TO </span></span><span style='font-size:10.0pt;font-family:"Courier New";color:black;background:white'>useexceptions</span><span class=l0s551><span style='font-size:10.0pt'>.</span></span><span style='font-size:10.0pt;font-family:"Courier New";color:black;background:white'><br></span><span class=l0s521><span style='font-size:10.0pt'>ENDIF</span></span><span class=l0s551><span style='font-size:10.0pt'>.</span></span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>During debugging, I noticed that the first GET_ELEMENT command got a return-code of zero. But the next two both got return-codes of 0008. Looking at the bindings, I could see that we were passing the workflow container elements to the task container, but the workflow container elements were never populated anywhere in the workflow. </span><b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:red'>What is the criteria for when a GET_ELEMENT command will return a SY-SUBRC of 0008?</span></b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:red'> </span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>What I found interesting was that if I tested the BOR method stand-alone through SWO1, these GET_ELEMENT commands always got return codes of zero, even though I did not key anything into the importing fields on the test screen. They only got return-codes of 0008 when running in the workflow itself. So is it possible that the SWO1 test screen was populating these fields with spaces which was accepted? And then when running in the workflow they were INITIAL which caused the return-code 0008?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>The other thing I notice here is that the check of SY-SUBRC is after the GET of the NoCommit parameter but it is populating the UseExceptions parameter if sy-subr is not zero. That looks to me like an error in the code and this code came from the standard RELEASE method of BUS2012. I think the only reason we have been getting any exceptions at all from this process is because we just happened to not populate the NoCommit parameter which caused SY-SUBRC to be 0008 which then caused us to move the “X” to the UseExceptions variable.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Comic Sans MS";color:blue'>Loren </span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:gray'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:gray'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><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>Mark Pyc<br><b>Sent:</b> Tuesday, December 10, 2013 5:38 PM<br><b>To:</b> SAP Workflow Users' Group<br><b>Subject:</b> Re: Temporary Exception Message Not Showing Up in Workflow Log<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>G'day Loren,<o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal>An oldie, but a goldie!! <o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal>SAP has some wonderful code that says if the message number is initial, don't include it in the log. Oh but wait, message 000 is a valid message number.... Too bad. Pick a different number.<o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal>If you change to message ZWF_MSG 001 it'll work a treat.<o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal>Have fun,<o:p></o:p></p></div><div><p class=MsoNormal>Mark<o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div></div><div><p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p><div><p class=MsoNormal>On 11 December 2013 05:41, Bratzler, Loren <<a href="mailto:loren.bratzler@nscorp.com" target="_blank">loren.bratzler@nscorp.com</a>> wrote:<o:p></o:p></p><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'>I feel like I’m asking an awful lot of questions here lately! But here is another issue I am facing. I spoke with Sue about this at TechEd and I have scoured SCN and the internet trying to find an answer but no luck so far.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'>I have added a temporary exception to a BOR method when a user has the object locked. On other workflows where we have a temporary exception, the workflow log shows a yellow warning indicator on the execution of the step that you can click on and get the temporary exception message:</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'><img border=0 width=678 height=115 id="_x0000_i1025" src="cid:image001.png@01CEF691.7B7ACFA0"></span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'>If you click on the warning, you get a pop-up window that displays the message:</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'><img border=0 width=432 height=140 id="_x0000_i1026" src="cid:image002.png@01CEF691.7B7ACFA0"></span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'>However, on the workflow where I just added the temporary exception, I do not get the warning message. You can see in this example below, that the background task was executed twice by the retry program (RSWWERRE) before it finally completed but I did not get the warning messages:</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><img border=0 width=680 height=149 id="_x0000_i1027" src="cid:image003.png@01CEF691.7B7ACFA0"><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'>I have compared the two BOR methods (the one that works and the one that doesn’t work) and I believe I am doing everything correct. They both have the exception defined as temporary:</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><img border=0 width=656 height=205 id="_x0000_i1028" src="cid:image004.png@01CEF691.7B7ACFA0"><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'>And the logic in the method is doing an EXIT_RETURN raising the temporary exception number:</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt'>* If there is only one error message and it is a user lock</span><span style='font-size:10.0pt;font-family:"Courier New";background:white'><br></span><span style='font-size:10.0pt'>* error (CJ-806), raise temporary exception 9001.</span><span style='font-size:10.0pt;font-family:"Courier New";background:white'><br> </span><span style='font-size:10.0pt'>IF </span><span style='font-size:10.0pt;font-family:"Courier New";background:white'>lv_lines </span><span style='font-size:10.0pt'>= 1.</span><span style='font-size:10.0pt;font-family:"Courier New";background:white'><br> </span><span style='font-size:10.0pt'>READ TABLE </span><span style='font-size:10.0pt;font-family:"Courier New";background:white'>lt_result </span><span style='font-size:10.0pt'>INDEX 1</span><span style='font-size:10.0pt;font-family:"Courier New";background:white'><br> </span><span style='font-size:10.0pt'>INTO </span><span style='font-size:10.0pt;font-family:"Courier New";background:white'>ls_result</span><span style='font-size:10.0pt'>.</span><span style='font-size:10.0pt;font-family:"Courier New";background:white'><br> </span><span style='font-size:10.0pt'>IF </span><span style='font-size:10.0pt;font-family:"Courier New";background:white'>ls_result</span><span style='font-size:10.0pt'>-</span><span style='font-size:10.0pt;font-family:"Courier New";background:white'>message_id </span><span style='font-size:10.0pt'>= 'CJ' AND</span><span style='font-size:10.0pt;font-family:"Courier New";background:white'><br> ls_result</span><span style='font-size:10.0pt'>-</span><span style='font-size:10.0pt;font-family:"Courier New";background:white'>message_number </span><span style='font-size:10.0pt'>= '806'.</span><span style='font-size:10.0pt;font-family:"Courier New";background:white'><br> lv_msg1 </span><span style='font-size:10.0pt'>= </span><span style='font-size:10.0pt;font-family:"Courier New";background:white'>ls_result</span><span style='font-size:10.0pt'>-</span><span style='font-size:10.0pt;font-family:"Courier New";background:white'>message_text</span><span style='font-size:10.0pt'>.</span><span style='font-size:10.0pt;font-family:"Courier New";background:white'><br> exit_return </span><span style='font-size:10.0pt'>9001 </span><span style='font-size:10.0pt;font-family:"Courier New";background:white'>lv_msg1 space space space</span><span style='font-size:10.0pt'>.</span><span style='font-size:10.0pt;font-family:"Courier New";background:white'><br> </span><span style='font-size:10.0pt'>ENDIF.</span><span style='font-size:10.0pt;font-family:"Courier New";background:white'><br> </span><span style='font-size:10.0pt'>ENDIF.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'>Even though these changes were made strictly to the BOR Object, I also generated a new version of the workflow to see if that would make the messages start appearing in the log, but that did not work either.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'>Anyone have any ideas on what I might be missing here?</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'> </span><o:p></o:p></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Comic Sans MS";color:blue'>Loren Bratzler</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:gray'>Norfolk Southern Corporation</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:gray'>110 Franklin Road SE</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:gray'>Roanoke, VA 24042-0060</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:gray'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:gray'>Phone: <a href="tel:540-524-3072" target="_blank">540-524-3072</a></span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:gray'>Email: <a href="mailto:loren.bratzler@nscorp.com" target="_blank">loren.bratzler@nscorp.com</a></span><o:p></o:p></p></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'> </span><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></body></html>