<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'><font style="font-size:16pt;" size="4" color="#000000" face="Garamond,sans-serif">Hi Claude,<br>This, ultimately, might not be much different than the z-table approach, but I just finished ( a while ago) reading through the SAP-PRESS publication for BRF+. It is different from BRF as the + version is in the ABAP stack. <br><br>If you're not looking for a quick solution, you might want to take a look at it. I don't know what release you're on, but I think it is generally available by now. <br><br>It supports several different rule structures and the resulting tables are available to the business process owners. The tables are read by function calls.<br><br>Would love to get a chance to use this myself. <br id="FontBreak"></font><br><br><font style="font-size:12pt;"><strong><font color="#000000"><font style="font-size:16pt;"><font face="Tahoma"><font style="font-size:10pt;" size="2">Ed Diehl</font><br></font></font></font></strong></font><font style="font-size: 12pt;" size="3"><font face="Tahoma"><span style="color:rgb(0, 0, 0);"><em>"Success consists of going from failure to failure without loss of enthusiasm."</em> </span><br><br></font></font><br><br><div><hr id="stopSpelling">Date: Wed, 29 Oct 2014 13:44:32 -0400<br>From: claude.bourque@rcmp-grc.gc.ca<br>To: sap-wug@mit.edu<br>Subject: Stopping Escalation<br><br>
<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>
<br>_______________________________________________
SAP-WUG mailing list
SAP-WUG@mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug</div> </div></body>
</html>