You are not authorized to execute this application in SAP E-Recruit

[Former Member]

Hi,

We are getting the below error while going to recruitment page for recruiter:

"You are not authorized to execute this application"

At the same time when we check in SLG1, we get the below errors:

No candidate could be found for US E0023127

The error occurred in program CL_HRRCF_CANDIDATE============CM003 line 361

Apart from this we are not getting any dumps/traces in ST22/ST05/ST01.

When we encountered this error for the first time, we executed the report RCF_CREATE_USER in SE38 and the problem was resolved.

We got the error again 2 days back, after that also it got automatically resolved. But, now we are getting this error continuously.

We also tried re-executing the report RCF_CREATE_USER and HRALXSYNC but no use.

The service user (for recruiter) is a reference user from RCF_CAND_INT.

We have also tried giving different roles and authorizations to the user.

SAP_ERC_RECRUITER_CI_4
SAP_RCF_RECRUITER
SAP_ERC_REC_ADMIN_CI_4

SAP_ALL

We are in ECC 6 EHP 6 and we have a standalone EREC system with ERECRUIT 617 SP3.

We are stuck at this point in our EREC project.

Kindly provide your valuable suggestions for this issue.

Thanks in advance!

Regards,

Khushboo

[romanweise · Accepted solution]

Hello Khushboo,

the message you are getting is a bit misleading as it is the standard behavior of the quick search if the user you are logged in as recruiter does not have a candidate assigned. So the message in SLG1 points into the correct direction.

I am not sure what you are meaning by "the service user (for recruiter)". Although table T77RCF_ROLE allows to specify a reference user for all roles in eRec only the entries for internal and external candidates are actually used. So the authorization assignment for the recruiter specific roles has always to be done directy for each user. A reference user could be overwritten / reset to RCF_CAND_INT by the ALE.

What bothers me a bit is the user name and that you mention RCF_CREATE_USER and HRALXSYNC at the same time. This might be the reason for your issue. Looks like you created a candidate for a user using RCF_CREATE_USER which is later transferred in the ALE from HR Core to eRec. This was not a good idea. RCF_CREATE_USER is only for creating project users when the HR core to eRec and for special users who need a candidate while do not have an employee id in HR core (e.g. WF-BATCH). This is why I always recommend to use non-production user Ids for everyone during project phase. Its been quite a time some of my projects did otherwise and I remember a similar issue with one of the customer admins. Everytime data for the user / employee was send in ALE the candidate / user was messed up.

Getting this fixed was quite troublesome. In the end we had to dump the original candidate. We deleted all records between candidate object, central person, business partner and person object in HRP1001. By that time the customer was still on the old ALE version so today I would also delete all entries in HRP558X infotype tables for the employee. Then I would first try to finger the employee id (e.g. change the name, save, directly change it back, save again ) so it is transferred during the nightly processing of the change pointers and put in the IDoc. If this is not working I would try to transfer it again using PFAL.

Kind Regards

Roman     

[Former Member]

Hello Roman & Sridevi,

Thank you so much for your reply!

As of now it's working by deleting the cookies and cache data of the browser.

But, this error occurs frequently.

As we discussed with the other projects, this is a common error and it occurs always.

Still, I wonder if we could get a permanent solution to this.

Thanks & Regards,

Khushboo

[Former Member]

Hi,

Did you check if the relationship is being removed in the standard tables of HRP1001 for the Candidate ID? Is this relationship being deleted periodically