<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>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></BODY></HTML>