on ‎2016 Jan 27 3:46 AM
Hi
We have a requirement where we need to remove candidates which are beyond a time limit. Now if we do this by deleting them through SU01 then candidates appear in recruiter search but candidate wont be able to update his profile.
Do we have any standard way where we can remove users & can activate them when required.
Regards
Puneet
Request clarification before answering.
Hi Puneet,
I would like know why you want to delete users using SU01? What do you mean with "activate when required"?
Basically, the (external) candidate users are managed by their own (activated by application/registration - deleted by self deregistration in profile or by ILM (HRRCF_CAND)).
If you delete the data (by ILM object HRRCF_CAND), the data are gone -> there is no option to "reactivate" later. The ILM provides a services to warn the candidates that their profile is supposed to be deleted soon.
BR
Frank
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
there is a standard report called RCF_USER_DELETE. Maybe you wanna check if this report is meeting your requirement(s). The only thing this standard report is missing is writing a deletion change pointer to the table COM_SE_CPOINTER for deleting the candidate from the TREX search index (which is triggered by the RCF_PERIODICAL_SERVICES report which should be scheduled as job in SM36/SM37). So the candidate is still returned as a search result through the candidate search (same behaviour as simple deletion through SU01). You could copy the standard report and add the insertion of the deletion change pointer (after the successful deletion of the user) by a call of the following instance method
CL_HRRCF_SES_BUSOBJ_CAND_SPT->INSERT_CPOINTER_FROM_HROBJECT(...).
Another way would be to look at the class method CL_HRRCF_DELETE_MANAGER=>DELETE_CANDIDATE(...). The advantage with this method should be that it checks if still open relationships for the candidate exists (and only deletes the candidate if no open relationships exist). If I am not mistaken this is the method which is used in the standard for deleting candidates (maybe a where-used list of this method can help you to analyse the standard deletion behaviour of a candidate).
Best Regards and hope that I could help
Patrick
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Puneet,
My understandng is that you have many candidates that are stored in SU01 which you need to delete?
There is no standard report available to delete the candidates but you may wish to use the applications: ERC_A_DEL_EXT_CAND or ERC_A_DEREG_CAND
I hope this helps you.
Regards,
Keith
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.