Re : SAP-WUG Digest, Vol 119, Issue 15

Wed Oct 29 15:28:08 EDT 2014

Hi I would use BRF+
No hard coding and could add some logic
Also another could be to create customs attribute or rôle allocated to the user.
I would explore those...
Cheers

sap-wug-request at mit.edu a écrit :
Send SAP-WUG mailing list submissions to
	sap-wug at mit.edu

To subscribe or unsubscribe via the World Wide Web, visit
	http://mailman.mit.edu/mailman/listinfo/sap-wug
or, via email, send a message with subject or body 'help' to
	sap-wug-request at mit.edu

You can reach the person managing the list at
	sap-wug-owner at mit.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of SAP-WUG digest..."

Today's Topics:

   1. Stopping Escalation (Claude Bourque)
   2. Re: Stopping Escalation (Dan Stoicof)
   3. Re: Stopping Escalation (Claude Bourque)
   4. RE: Stopping Escalation (Desai, Suvarna)

----------------------------------------------------------------------

Message: 1
Date: Wed, 29 Oct 2014 13:44:32 -0400
From: "Claude Bourque" <claude.bourque at rcmp-grc.gc.ca>
Subject: Stopping Escalation
To: <sap-wug at mit.edu>
Message-ID: <5450EF4002000064000C4D98 at mail.rcmp-grc.gc.ca>
Content-Type: text/plain; charset="us-ascii"

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20141029/5d2a66f2/attachment-0001.htm

------------------------------

Message: 2
Date: Wed, 29 Oct 2014 17:59:25 +0000 (UTC)
From: Dan Stoicof <dan_stoicof at yahoo.com>
Subject: Re: Stopping Escalation
To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
Message-ID:
	<1256237644.112783.1414605565523.JavaMail.yahoo at jws10706.mail.gq1.yahoo.com>

Content-Type: text/plain; charset="utf-8"

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 WF3. 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 dil!
 emma is that the CFO/CFAO position is most likely NOT the same in DEV, QA and Prod.?Thanks.?Cheers?ClaudeWorkflow 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/93e97d18/attachment-0001.htm

------------------------------

Message: 3
Date: Wed, 29 Oct 2014 14:10:26 -0400
From: "Claude Bourque" <claude.bourque at rcmp-grc.gc.ca>
Subject: Re: Stopping Escalation
To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
Message-ID: <5450F55202000064000C4DA8 at mail.rcmp-grc.gc.ca>
Content-Type: text/plain; charset="us-ascii"

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-0001.htm

------------------------------

Message: 4
Date: Wed, 29 Oct 2014 19:20:46 +0000
From: "Desai, Suvarna" <SDesai at atb.com>
Subject: RE: Stopping Escalation
To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
Message-ID:
	<3F2298AD62A9434BA825CDB73B0030FB3B9C162B at APP-P-EXCH02.atb.ab.com>
Content-Type: text/plain; charset="utf-8"

Hello,
I think we can use the function module 'RH_STRUC_GET' for this one .This FM will get the org. unit tied directly to each of the position the user holds and restricts in reading the level above

Thanks.
Suvarna
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Dan Stoicof
Sent: Wednesday, October 29, 2014 11:59 AM
To: SAP Workflow Users' Group
Subject: Re: Stopping Escalation

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<mailto:claude.bourque at rcmp-grc.gc.ca>>
To: sap-wug at mit.edu<mailto: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<mailto:SAP-WUG at mit.edu>
http://mailman.mit.edu/mailman/listinfo/sap-wug

If you have received this email in error, please let me know by return email so I can make sure it doesn't happen again. Because emails can contain confidential and privileged material, I'd ask for your help by deleting it and any attachments. Thanks!

We like to keep people up to date with information about new products and services at ATB or changes that could affect you. You can check out more about ATB and CASL at http://www.atb.com/important-information/privacy-security/Pages/ATB-and-CASL.aspx 

If you would like to unsubscribe from our updates, please use this URL - http://www.atb.com/important-information/privacy-security/Pages/unsubscribe.aspx 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20141029/74dac31e/attachment.htm

------------------------------

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

End of SAP-WUG Digest, Vol 119, Issue 15
****************************************