cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

MSS for e-recruiting - error with workflow user since no candidate exists

mraffel
Participant
0 Likes
432

Hi all!

We are trying to set up the requisition request in MSS based on the new standard WF templates specified in SAP note 949625.

I can create a requisition request but the WF failes to create the e-recruiting requisition (NB) because our workflow system user does not have a candidate defined (No candidate could be found for US WF-BATCH).

How can we address this issue?

Thanks in advance and best regards,

Mathias

Accepted Solutions (1)

Accepted Solutions (1)

romanweise
Active Contributor
0 Likes

Hello Mathias,

everyone working in e-recruiting needs a candidate (together with all linked objects like CP and BP). This rule includes the WF-BATCH.

If you want to use workflows in e-recruiting you'll need to create a candidate using RCF_CREATE_USER for WF-BATCH. Then all should work fine.

Best Regards

Roman Weise

PS: be sure to assign a printer to WF-BATCH if you want it to send correspondences by workflows. The SMARTFORM processing requires a printer even if it's send via email.

mraffel
Participant
0 Likes

Hi Roman!

Thanks for your answer. I forgot to mention that we run the SW on one instance, so the ABAP RCF_CREATE_USER will not work for us.

And the ABAP's HR_SYNC_PERSON or HRALXSYNC do not work since I can not select any user (the user options is grayed out). So our workflow system user can not be selected.

Any other ideas?

Thanks and best regards,

Mathias

romanweise
Active Contributor
0 Likes

Hello Mathias,

using RCF_CREATE_USER for creating the candidate of the WF-BATCH user is the right way. I set one on the very few integrated installations in the DACH area life earlier this year.

You just run the report like you probably used it in the initial phase of the e-recruiting roleout to create candidates for the implementation team. (Getting all the integration set up for e-rcruiting 600 usually takes eternities and w/o HRALXSYNC can't be used for them.)

I remember some trouble when ramping up e-recruiting 600 that the report did not create CP->US relations so it did not work correct. But this did not happen in the newer support packages. In case you want to check if everything is correct just test one of the standard candidate handling classes like cl_hrrcf_candidate method get if you are unsure if the report did its job.

Best Regards

Roman Weise

mraffel
Participant
0 Likes

Hi Roman!

Of course you were right. RCF_CREATE_USER worked even we are using the integrated installation. Thank you very much for the help.

But I had to actually use an employee number on the selection screen. In the development system that is OK. But in production I do not want to assign the WF user to an employee record.

Any workaround for that?

The SAP design still does not make too much sense to me. If the WF agent and the corresponding candidate would be used, I could understand it. But the WF background user? Not sure why they did that.

Thanks again and greetings to Germany!

Best,

Mathias

Former Member
0 Likes

Well, you do not really create an employee entry for WF-BATCH.

You are just creating a virtual personnel number for the User in HRP1001 relations.

There is no infotype entry in PA* infotypes created.

Though you will be able to find the WF-BATCH user in employee search in e-recruiting, this is the right and only way to do it.

You need to assign an employee number. But you can choose a virtual one.

Former Member
0 Likes

Hi Experts-

Im pretty much going through the same scenario now. On registration external candidate does not receive verification email. I am thinking this has got to do with WF-BATCH not behaving. Plz guide me through this. What values do we need to use in the report. RCF_CREATE_USER. I am giving the following values and not able to proceed further. I am using an exisiting PERNR and getting a msg

'A candidate already exists for the employee number'

First name : workflow

Last name : batch

User name : wf-batch

Personnel number : existing PERNR (75481235)

Position : above PERNRs position number (2184)

E-mail address : as maintained on wf-batch user (xxx@xxx.com)

Alternatively if i give a candidate number in the place of personnel number its giving another msg;

'Enter a value for field langugage according to ISO 639. Not sure if some config needs to be maintained somewhere on this but entries on T002TX seems alrite.

Appreciate your time!!

Thx in advance

Roopa Reddy

Answers (1)

Answers (1)

Former Member
0 Likes

Hi,

You try executhing the fu. module HRWPC_EREC_CREATE_EREC_OBJECT manually by giving the notification id and type. debug this fn module, which is not too big. u will find out the problem.

i m just releived this isssue.

after a week struggle, the NB object got created in eRecruitment just now.

hope u r using WS16900009 / WS169000010

regards

jayanthi.K