<HTML><HEAD>
<META content="text/html; charset=UTF-8" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 10.00.9200.17116"></HEAD>
<BODY style="FONT: 10pt Segoe UI; MARGIN: 4px 4px 1px">
<DIV>Thanks Dan,</DIV>
<DIV> </DIV>
<DIV>I should have mentioned that, they often don't have a consistent position description. But maybe, I'll revisit that.</DIV>
<DIV> </DIV>
<DIV>Cheers</DIV>
<DIV> </DIV>
<DIV>Claude<BR><BR>>>> Dan Stoicof <dan_stoicof@yahoo.com> 2014/10/29 1:59 PM >>><BR></DIV>
<DIV style="FONT-SIZE: 16px; FONT-FAMILY: HelveticaNeue-Light, Helvetica Neue Light, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; COLOR: #000; BACKGROUND-COLOR: #fff">
<DIV id=yui_3_16_0_1_1414586595779_189982 dir=ltr><SPAN>Claude,</SPAN></DIV>
<DIV id=yui_3_16_0_1_1414586595779_189983 dir=ltr><SPAN></SPAN> </DIV>
<DIV id=yui_3_16_0_1_1414586595779_189976 dir=ltr><SPAN id=yui_3_16_0_1_1414586595779_189977>Evaluate position description, that should be the same in all systems and it generally has the CFO/CEO letters in it. Once you find it, stop.</SPAN></DIV>
<DIV id=yui_3_16_0_1_1414586595779_189978 dir=ltr><SPAN></SPAN> </DIV>
<DIV id=yui_3_16_0_1_1414586595779_189979 dir=ltr><SPAN>Regards,</SPAN></DIV>
<DIV id=yui_3_16_0_1_1414586595779_189980 dir=ltr><SPAN></SPAN> </DIV>
<DIV id=yui_3_16_0_1_1414586595779_189981 dir=ltr><SPAN>Dan Stoicof</SPAN></DIV><BR>
<DIV id=yui_3_16_0_1_1414586595779_189974 style="FONT-SIZE: 16px; FONT-FAMILY: HelveticaNeue-Light, Helvetica Neue Light, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif">
<DIV id=yui_3_16_0_1_1414586595779_189973 style="FONT-SIZE: 16px; FONT-FAMILY: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif">
<DIV id=yui_3_16_0_1_1414586595779_189972 dir=ltr>
<HR SIZE=1>
<FONT id=yui_3_16_0_1_1414586595779_189975 size=2 face=Arial><B><SPAN style="FONT-WEIGHT: bold">From:</SPAN></B> Claude Bourque <claude.bourque@rcmp-grc.gc.ca><BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B> sap-wug@mit.edu <BR><B><SPAN style="FONT-WEIGHT: bold">Sent:</SPAN></B> Wednesday, October 29, 2014 1:44 PM<BR><B><SPAN style="FONT-WEIGHT: bold">Subject:</SPAN></B> Stopping Escalation<BR></FONT></DIV>
<DIV class=y_msg_container><BR>
<DIV id=yiv2893738312>
<DIV>
<DIV>Greetings WUGgers</DIV>
<DIV> </DIV>
<DIV>The following is more to start a discussion that to get an answer to a specific technical problem. So, here it goes.</DIV>
<DIV> </DIV>
<DIV>I've been dealing with this for about 10 years and I'm wondering if there's a better way.</DIV>
<DIV> </DIV>
<DIV>In a lot of workflows that I've built, the business wants escalation to stop once it reaches a certain position in the hierarchy. For example, don't go higher than the CFAO or the Director of HR. Or, if the user requestion leave, travel, training, etc is the CFO/CFAO then the approval is different than for other users.</DIV>
<DIV> </DIV>
<DIV>I've used a variety of ways to do this including the following</DIV>
<DIV> </DIV>
<DIV>1. Hard-code the position(s) within the workflow (bad, very bad)</DIV>
<DIV>2. Hard-code the position(s) within an ABAP method (still very bad)</DIV>
<DIV>2. Use a Z-table to store the position(s) in question and read that table from WF</DIV>
<DIV>3. Use table TVARVC (or TVARV)</DIV>
<DIV>4. I saw a customer once use table T77S0 to save the position(s).</DIV>
<DIV> </DIV>
<DIV>Are there other significantly different options out there?</DIV>
<DIV> </DIV>
<DIV>The main dilemma is that the CFO/CFAO position is most likely NOT the same in DEV, QA and Prod.</DIV>
<DIV> </DIV>
<DIV>Thanks.</DIV>
<DIV> </DIV>
<DIV>Cheers</DIV>
<DIV> </DIV>
<DIV>Claude</DIV>
<DIV>Workflow Consultant RCMP</DIV></DIV></DIV><BR>_______________________________________________<BR>SAP-WUG mailing list<BR><A href="mailto:SAP-WUG@mit.edu" ymailto="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><BR><BR><BR></DIV></DIV></DIV></DIV></BODY></HTML>