e Recruiting WF-BATCH not allowing to create

[Former Member]

Hi

I am not able to create WF-BATCH as the program (RCF_CREATE_USER) is generating a message “Candidate already exists for the User."

DETAILS: We have manually created WF-BATCH initially and when the Requisition from (HR_MSSRCF_REQUISITION) is submitted, in the analysis, we found that system generated error “RCF_CAND_REG”. So I have deleted the user WF-BATCH and try creating the same user through program “RCF_CREATE_USER"., But I am not able to do as the program is generating a message “Candidate already exists for the User."

I have verified the SU01 there is no data with the name WF-BATCH. Please can you share your experience on how to resolve this issue?

[romanweise · Accepted solution]

Hi,

if someone created a candidate for the user WF-BATCH earlier and you only deleted the user the system will still find the relations between objects candidate - central person - user in the infotype 1001 (Table HRP1001) and throw the message. Check table HRP1001 for an entry which has OTYPE = CP, SCLAS = US, SOBID = WF-BATCH. If this record exists it causes the message. (In an integrated installation landscape the CP - US relation could also be emulated via a record in IT0105).

If the record exists, creating user WF-BATCH should result in a working candidate object. As WF-BATCH gets SAP_ALL, according to SAP recommendation, eRec authorizations should not be an issue. But be aware that WF-BATCH is not created by using transaction SU01. You have to use transaction SWU3 instead. When you run the node for configuration of RFC destination the WF-BATCH user is created if you are assigned to group SUPER.

Kind regards

Roman

[Former Member · Accepted solution]

Hi Roman

Thank you verymuch

[Former Member · Accepted solution]

Hi Roman

The Workflow is working alright now.

The data from Requisition HR_MSSRCF_REQUISITION (MSS page) is not getting populated on the Recruiter dashboard. The form is duly approved by the Manager and the approved Requisition is displayed on the Manager dashboard (on draft status), but it was not appeared on the Recruiter dashboard.

I have created a recruiter group and assigned 3 recruiters to the form as a support group. Out of three one is a default recruiter. However, the form is not displayed on any of the recruiter’s dash board.

Am I missing any configuration or do I need to verify specific table. Please guide me.

Thank you in advance

[Former Member · Accepted solution]

Hi Robin,

I know it's been almost 2 years completed for this posting. But still i am also experiencing the same issue since few days. Can help me on the same if you have the solution for the same?

I am working on EHP5 ans SP 11. Can you please give me your inputs on this.

Thank you,

Regards,

Sekhar

[Former Member · Accepted solution]

Hi Roman,

I am working in Standalone architecture where Recruiting server is in another instance apart from HR system.

We are using WS45600028 standard workflow.

When Manager submits the Requisition to higher level manager to approve, its done successfully and the notification is going to the Manager. But after approval, Requisition is not going to Requiter's POWL queries.

I have maintained Support Group, Lead Recruiter in it and assigned this to Requisition.

I have checked HRP5131 table. But there is no SOBID which sould be flaged as Lead Recruiter.

When Higher level Manager approves the Requisition, It is successful bu there is an error in slg1.

Error: Error when ending the Work item 0000007704 in HR system.

The system returned the call of interface SAP_WAPI_WRITE_CONTAINER in this context

System Response:

Call ended with an error. The function was not executed.

Procedure: Remove call.

At the same system is throwing the error for the User (This user is used for RFC creation using with transaction SM59): No candidate for this User.

Details of error: The error occurred in program CL_HRRCF_CANDIDATE_ADMIN_BL===CM00B line 77

Procedure for system administration:

Check the context in which the error occurs.

Since it it probably program error and not an input error, you should contact SAP.

Can you please look into the above issue and address me if you have any solution for the same.

Thank you.

Regards,

Sekhar