Stopping Escalation

[Claude Bourque]

Thanks Dan,
 
I should have mentioned that, they often don't have a consistent position description. But maybe, I'll revisit that.
 
Cheers
 
Claude

>>> Dan Stoicof <dan_stoicof at yahoo.com> 2014/10/29 1:59 PM >>>
Claude,
 
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.
 
Regards,
 
Dan Stoicof

From: Claude Bourque <claude.bourque at rcmp-grc.gc.ca>
To: sap-wug at mit.edu 
Sent: Wednesday, October 29, 2014 1:44 PM
Subject: Stopping Escalation


Greetings WUGgers
 
The following is more to start a discussion that to get an answer to a specific technical problem. So, here it goes.
 
I've been dealing with this for about 10 years and I'm wondering if there's a better way.
 
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.
 
I've used a variety of ways to do this including the following
 
1. Hard-code the position(s) within the workflow (bad, very bad)
2. Hard-code the position(s) within an ABAP method (still very bad)
2. Use a Z-table to store the position(s) in question and read that table from WF
3. Use table TVARVC (or TVARV)
4. I saw a customer once use table T77S0 to save the position(s).
 
Are there other significantly different options out there?
 
The main dilemma is that the CFO/CFAO position is most likely NOT the same in DEV, QA and Prod.
 
Thanks.
 
Cheers
 
Claude
Workflow Consultant RCMP

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20141029/074209cd/attachment.htm