EREC - Putting Requisitions "On Hold"

[Former Member]

We are on a seperate recruiting instance, 604-09. My clients would like to place a requisition "on hold" while some business decisitions are being made. They do not want to disposition via reject all the candidates that have applied. However, the system will not allow them to change the requisition status to "On Hold" with open assignments.

There doesn't seem to be another status I could use for the Candidates, like "On hold" and as long as they remain "in Process" I can't change the requisition status.

It seems the purpose of status "Oh hold" is for this very reason and rejecting all the candidates seems unreasonable. Has anyone come across this and found a way around it? Any assistance would be appreciated.

[Former Member]

Hi Kelly,

Just wondering if you already have an answer yourself. I'm currently having the same questions from my customer and I'm just walking into the same wall as you.

Appreciate your reply.

Jeroen

[NicoleGeischnek]

Hello Jeroen,

That's only possible by modification (eg. CL_HRRCF_REQ_MGMT_PL => HANDLE_STATUS()).

Regards

Nicole

[Former Member]

Hi Nicole,

Thanks, but by modification is it also possible to keep current candidates on the Requisition (and put their status on hold also) while putting the Requisition on hold.

Q from the business is that they want to put the req on hold with current candidates still attached to it and Re-start on a later date (not currently needed vacancy, no budget, etcetc).

What they're doing now is removing current candidates, close req, then after a while re-activate and search for the candidates again (which are mostly lost in the talent pool or haven't released their profile).

So, should be simple, click on hold, candidates should be notified, status candidates should be on hold........click re-activate, candidates should be activated also in their last known status, candidates should be notified, recruiter happy. That shouldn't be hard to accomplish.

Thanks for your toughs on this.

Jeroen

[NicoleGeischnek]

Hello Jeroen,

For that you would need an own candidacy/application status which will enlargen the modification a lot.

Just a thought but wouldn't it be possible to reject all candidates -> set the requisition to status 'on hold' and once the requisition is re-activated and released again, re-set the candidacies again to status 'in process'?

For that you would need only a status-changing activity which can set the status from 'rejected' to 'in process'. Then you could also send an automatical correspondance letter via workflow which informs all re-activated candidates about the change.

Regards

Nicole

[Former Member]

Nicole, I am curious about this approach. When I reactivate a rejected candidate, the status changes back to "In process" for the recruiter, but when the candidate looks at their status it still says Withdrawn.  The same for the Manager, it shows then as withdrawn.

Do you know why this is?  I had a ticket with SAP and they could not assist so we have not been able to use reactivate a rejectect candidate as intended.

Thanks,

Kelly Buff

[NicoleGeischnek]

Hello Kelly,

It shows as 'withdrawn' and not 'rejected' if recruiter rejected the application and not the candidate withdrawn it? Usually with an active BF3 you should see there 'not selected' now.

Regards

Nicole

[Former Member]

Hi Nicole,

Yes, sorry, the status a canddiate sees when they rejected is "Not Selected".  I just used the wrong word.  The issue we are having is when we reactivate them using the reactive rejected candidate activity, the status the candidate sees under "My applications" is still "Not Selected".  It is not changing them back to "In Process" as it should.  We have not been able to figure out how to accomplish this.  If you have any ideas we would really appreciate it!

Thanks,

Kelly

[NicoleGeischnek]

Hi Kelly,

Status is re-set in HRP5132 and HRP5133?

Regards

Nicole

[Former Member]

When I rejected the candiate the status on both tables showed as Rejected.  I then reactivated that candidate and the status on HRP5133 updated to In Process but on HRP5132 it did NOT.  That is it - the application status is not updating on the application object table HRP5132.  That is the status that displays to the candidate and the manager.  However, I checked the in SPRO and under "Assign a Status to a Status Changing Activity" for Activity 9200, Reactivate Rejected Candidate, I have a table entry to change status to In Process for NE (Candidacy - HRP5133), NA (Candidate) and ND (Application - HRP5132) objects.

Do you have any idea what I might be missing? Nicole I can't thank you enough, you have been so helpful.

Thanks,

Kelly

[NicoleGeischnek]

Hi Kelly,

Got it ... that is proabably because the main status changing workflow doesn't handle the changing the setting of both objects in status 'in process'. So you would have to adjust standard workflow WS51900010 for this reactivation - for that you can check the status 'rejected' to see the tasks you need.

Regards

Nicole

[Former Member]

Hi Nicole, Kelly,

Thanks so much for your answer, will go and write business case for this so the tech team can implement and keep you updated.

Jeroen

[Former Member]

Hi Nicole,

I sent this to my developer, he started walking through the workflow but wasn't really sure where a change would need to be made and couldn't find it.  Do you happen to know where in the workflow that change should be made? (Just thought I would ask in the event it could save us some time here!)

Thanks

Kelly Buff

[NicoleGeischnek]

Hi Kelly,

In fact you need a copy of the BOR method erc_candidacy.RejectAllOpenCandidacies where you set the status not to 2 from 0 but to 0 from 2 (so the other way round).

For that you can add in the 'in process' an own check and include task TS51900004 to get all candidacies of the application and then a copy of task TS51900006 which is calling the method created from above.

Hope that helps the developer,

Nicole