e-Recruiting: Display authority for requisitions and assignments

[Christian_Gaert]

Hi all,

my customer has the following requirement: a certain user should only have display authority for requisitions and assignments.

The user is not allowed to change, copy, create requisitions. Also, the user is not allowed to change assignments (create activities, assign candidates to the requisitions, etc.) but only to see the assignments and data overviews of the candidates, etc.

Does anyone know how to do that? Is it possible via authority restriction? Or is there a web dynpro application without modfiy authority?

Thanks for any tipps and hits.

Regards

Chris

[former_member131723 · Accepted solution]

Hi Chris

Yes this is possible!

If it is for recruiter there are 2 roles delivered in standard, restricted recruiter which allows only certain access and standard recruiter role which can be customized to allow only certain access to certain objects etc through the authorization objects and this can be customized and assigned via SU01 and PFCG transactions.

The documentation is very comprehensive in this regard - see this link

http://help.sap.com/erp2005_ehp_04/helpdata/en/6c/c9b54015c4752ae10000000a155106/frameset.htm

and also this wiki link for overview of roles in E-Recruiting.

http://wiki.sdn.sap.com/wiki/display/ERPHCM/Role+assignment

Hope it would help and best of luck!

Sally

[Christian_Gaert · Accepted solution]

Hi Sally,

thanks a lot for your reply.

I know the restricted recruiter. But i need a even more restricted role. To be specific: a role only for look-up of requisition data and assigned candidates.

Background: the customer wants his workers council to be able to check every requisition and its assigned candidates without - of course - being able to change any data.

Regards

Chris

[former_member131723 · Accepted solution]

Hi Chris

You would need to restrict authorization then in that case

(sorry my link to the documentation specifically on roles didnt work! Try here

http://help.sap.com/erp2005_ehp_04/helpdata/en/6c/c9b54015c4752ae10000000a155106/frameset.htm

Data Overview

You can use the authorization object P_RCF_VIEW to assign the authorizations to display data overviews.The following activities are relevant for the authorization to view data overviews:

● ACT_DOVR (Overview of the activity)

● APPL_DOVR (Overview of the application)

● CAND_DOVR (Overview of the candidate profile, also relevant in Audit Trails) ************

● CDCY_DOVR (Overview of the candidacy data) *****************

● PINST_PBL (Overview of the publication)

● REQ_DOVR (Overview of the requisition data, application group data, and posting data) ********

● EEO (Display of completed questionnaires with Equal Employment Information)

● SGR_DOVR (Overview of the support group)

● TG_DOVR (Overview of the talent group)

Activities - so here restrict all authorizations:

You use the authorization object P_RCF_ACT to determine the type of access to activities that is possible for a user. An activity in SAP E-Recruiting is therefore identified through the assigned process and through the activity type.

You can store the following access types to an activity using the authorization field ACTVT (Activity):

● Add or Create

● Change

● Delete

There are additional auths for recruiter - auth object P_RCF_WDUI

You might need to think about creating a custom role though to be honest as one problem is the talent pool, In this case, in standard the only way to restrict access to the talent pool is if you change authorization for the role "P_RCF_POOL" and restrict the possibility to maintain candidate data for CAND_MAINT in recruiter scenario, so that could be a problem because is in standard the recruiter role does have access to his or her support teams applications.

Having said that I cant see any other issue with custom role to achieve what you are looking for with the current authorization objects available!

[former_member131723 · Accepted solution]

re-post

Edited by: Sally Redmond on Sep 6, 2011 8:51 PM

[Christian_Gaert · Accepted solution]

Hi Sally,

unfortunately it doesn't work with authority restriction because i made an authority-trace. The application only checks for infotype display authority. Your always get the modify, create, etc. buttons.

I'm about to try a different approach: I copied the POWL-Feeder-Class and make some changes theres to prevent the modify-buttons from being displayed. Let's see......

Thanks.

Regards

Chris

[romanweise · Accepted solution]

Hi Chris,

using authorizations won't lead to success. The eRecruiting application is simply not build for a display mode. What might work is having an own portal role remove not needed links and copying the OBN navigation to use separated WD4A and floorplan manager configurations to hide buttons, deactivate fields, etc on all screens. Still you might need additional developments to replace feeder classes and change the application where the system behaviour can't be effected by configuration. This is a really huge amount of work.

The customer aproach is very "personal administration like", where a display role means simply having the same screens just without the possibility to change any field. Unfortunately eRecruiting is not designed that way. This is why I am usually using a complete different approach when the customer has the business requirement for a role which is suppossed just to see information but not to change anything. I build something near to the MSS. A list of requisitions (depending on support team assignment or even other attributes) with a navigation to a list of candidacies. The list of candidacies contains the most important information all other information is provided by linked data overviews (req data overview in req list, candidate / application data overview in candidacy list).

This fullfills the business requirement with a much lower application complexity which is an additional asset when the user is accessing the applicantion not every day or is not very used to eRec (e.g. work concil). Even if you decide to have a special requisition and candidacy / application data overview the development effort is far lower than your original solution. I'd assume it's perhaps 20%.

Best regards

Roman

[Christian_Gaert · Accepted solution]

Hi Roman,

thanks for your reply.

The portal solution does not work because the custmer does not run a sap portal.

It might work with the feeder class: the user can't change/create etc. a requisition anymore but he get's the dataoverview of the requisition. With click on button "Assignments" i execute the application with a special configuration so that no save button etc. is displayed. Moreover the acitivities can't be created / modified because of lacking authority. So far it's not that bad. But I must test it still very thoroughly.

Maybe Nicolas told you about this issue / customer at your meeting in berlin last week?

Regards

Chris

[romanweise · Accepted solution]

Hi Chris,

I am a bit confused about the following statement:

> The portal solution does not work because the custmer does not run a sap portal. 

If you are using EhP 4 with business function HCM_ERC_CI_2 activated it is a technical requirement to use SAP portal. running the system without portal is not supported by SAP!

Best Regards

Roman

[Christian_Gaert · Accepted solution]

Hi Roman,

sorry for my late reply.

Well, fact is, that the customer does not have a portal and erecruiting works quite well.

There are only a few things, that cause some problems, for example:

• approval of requisition release (because the approval-mail goes into uwl of portal)

The recruiter use the dashboard and some other links, that are stored on an intranet-page.

Regards

Chris

[SrinivasCh]

Hi Roman,

We are having similar requirement. We are implementing in integrated scenario (both HCM and Erec on the same instance with ESS/MSS).

Total company is divided into 15 regions and each region will have HR.Managers in respective raises the recruitment requisition it will come to his approval and he will approve it. This part is taken care through wf customisation.

Now, he should only process his region's requisitions and all employees in the company should be able to apply. Pls guide me how to gin this case.

What I am thing is customising the Recr admin role, where in he can go in and route the requisitions to respective recruiter. Pls guide me whether this will be right approach OR anything else better than this OR any standard way. Thanks.

Regards,

Srini Ch