Manager should not approve his own leave request in MSS

[Former Member]

Hello All

1) Manager should be able to add himself as approver of leave requests in ESS: How to control this through authorization or any other way?

2) Manager should not be allowed to approve his leave request. How to control this through authorization or any other way?

Await quick reply.

regards

Subramanyam

[Former Member]

Subra:

If Security is using P_PERNR object you can easily achieve # 2 requirement.  Of course this is dependent on Security also maintaining, IT0105, subtype 0001 with the User Id.

In P_PERNR, one specifies in a role, whether a particular infotype is READ or READ/WRITE.

Cheers, Al

[Former Member]

Hi Subra,

As mentioned our friends, there are 2 ways.

1. You filter the Approver when user choose manually (using ABAPer help).

2. If your authorization role contains P_PERNR object, you can control using authorization object.

Regards,

Kumar.

[Former Member]

Hello Albert and Kumar

The role used to approve the leave request is  Z_TIME_MGR_XX_ESS_WDA_1. The P_Pernr object is maintained in the role as shown below.

Request further inputs on what should be the settings so that manager cannot approve his own leave request.

warm regards

Subramanyam

[Former Member]

The second line of the P_PERNR above reads that the User has complete access to Read/Write for the time infotypes.  It's been some time since I built roles, but generally I think what is needed is another line where an Exclusion (E) is setup and the Authorization is simply READ.  (and Matchcode) for IT2001.

Al

[Former Member]

Hi,

Generally leave request will move to the supervisor mapping (standard 012- cheif) or 002 -Reports to relationship in OM Infotype 1001.

you manager will have the relationship 012- / A002 i mean who is the manager/ cheif  or to whom he/she reporting to.A002.

based on this , approval will happen.

Regards,

Dinesh

[Former Member]

Hi Dinesh

The usual process of manager getting defaulted through OM structure etc.. works fine. We have enabled the '' Requestor may change next agent'' option so that i can enter any other manager.

Therefore the manager is able to remove the default approver, put his name as approver and also approve the same.

This is what we want to avoid. Hope it is more clear.

regards

Subramanyam

[Former Member]

so you want manager to apply leave by default approves by himself only, then why don't you use auto approval process by taking 'not necessary to enter next agent',

Hope that I am clear to your requirement.

[Former Member]

hi Kedhar

I think you got confused. The scenario you described is what i want to avoid. How do i do it?

regards

Subramanyam

[Former Member]

Then remove the option 'Requestor may change next agent' for Manager rule groups,

There will be no authorization object for this & everything is as per config

check this doc  http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/108c31e7-b6a7-2d10-3692-c1a9f7a5c...

And also tell me that Manager leave should approve by whom ?

[Former Member]

Hi Kedhar

Thanks for highlighting this. The option 'Requestor may change next agent' is a business reqt and therefore cannot change it.

It is just that; i do not want to allow manager to add himself as approver and also he should not be able to approve his own request.

Can this be done using authorization or any config in spro. Development (ABAP/WF) is to be looked at as a last option due to budget constraints.

Hope it is more clear now.

regards

Subramanyam

[clwalker]

Hi Subramanyman

DId you achieve a solution for this?

[Former Member]

Hello Claire

No response so far and i found no solution w.r.t. SPRO config or authorization.

From the ABAPer I know this can be achieved using Badi PT_GEN_REQ: Client does not have development budget.

So, i am still awaiting for any sort of solution which does not involve ABAP/WF.

regards

Subramanyam

[Former Member]

Hi Subramanyam,

As far as i can understand it cannot be achieved by Configuration.
I am not sure if this could be done by authorization.

However as your ABAPer has said this can be achieved by implementing BADI PT_GEN_REQ.

You can write the code in the method "IF_EX_PT_GEN_REQ~SEARCH_FOR_NEXT_PROCESS" to achieve the same, in case things come to that.

Please let me know in case you find another way of achieving this.

Regards,

Mayank

[Former Member]

Hi Mayank

Yes this is what my ABAPer also informed. Let us see as others have replied it is possible using P_PERNR object.

regards

Subramanyam

[Former Member]

Dear Subramanyam,

1) Approver is coming from R3 side based on relationship maintenance but I am not sure on how from ESS, let me check

2) Is it auto approval then check options in table V_T554S_WEB