|
SAP Community Network Forums
»
SAP Solutions
»
ERP HCM (HR)
Thread: e-Recruiting: External and internal candidate profiles
 |
This question is not answered.
|
|
Replies:
3
-
Pages:
1
-
Last Post:
Nov 8, 2009 10:46 AM
Last Post By: Roman Weise
|
|
|
|
|
|
|
Re: e-Recruiting: External and internal candidate profiles
Posted:
Nov 4, 2009 7:59 AM
in response to: oscar miak
|
|
|
|
Response to Question 1 - Yes, the external candidate would still be able to login to his old profile as an external candidate.The Recruitment administrator has a choice to delete external candidate after the hiring process has been completed or leave the candidate registration as it is.
Once the candidate is hired, the candidate information is again created in the E-Rec system (When an ALE distribution model is set-up to push in PA master data changes in to E-rec system in E-Rec stan alone implementation) but this time as an internal candidate where the CP object is associated with a Pernr for the employee to be able to access the recruitment links as an internal candidate and to apply for internal job vacancies.
Response to Question No. 2 - When a Person employment status is made Inactive, the status is updated in the E-Rec system usually through the ALE distribution model (in a E-Rec standalone scenario) against the candidate record in HRP5102 - Field name "IS_INACTIVE" = "x" (True). This indicates that the internal candidate is no more active in the HR system.
Hope this information helps.
Best regards
G Raj
|
|
|
|
|
|
Re: e-Recruiting: External and internal candidate profiles
Posted:
Nov 4, 2009 3:31 PM
in response to: G Raj
|
|
|
|
Thanks Raj. Appreciate your time. For the second question - What happens to the internal candidate profile. Is that delimited or deleted or some one should manually do it after the employee is seperated. Is there any way that this profile can be made external as the seperated employee can apply for a job as an external candidate.
|
|
|
|
|
|
Re: e-Recruiting: External and internal candidate profiles
Posted:
Nov 4, 2009 7:08 PM
in response to: oscar miak
|
|
|
|
Hey Oscar,
This Internal Reference user assignment for the Internal Candidate after the seperation, Security should go back and change it to External reference user manually.
Even though Security change it to External reference user, The candidate should use the same internal candidate login credentials to login as External candidate.
If the user is newly registered with the same user id as an internal candidate then in that case this will become a new external candidate in the system, because whatever user id he gives at the time of registration will become ALIAS in the System and System will generate a random user id for this.
Thanks
Vasa
|
|
|
|
|
|
Re: e-Recruiting: External and internal candidate profiles
Posted:
Nov 8, 2009 10:46 AM
in response to: oscar miak
|
|
|
|
Hi,
I think we have to get some things corrected here.
For the first question. If you hire an external candidate and have the integration set up properly and use PA48 for hiring action the external candidate is transformed into an internal one. The processing is a bit complicated and includes deletion / replication and moving of org.management entities and differs between the different possible installation scenarios for e-recruiting. Depending if you hire on date or in future also influences the order of processings done by e-recruiting. You can check note 997181 to get an idea what is done when hiring a candidate. In the end the external candidate should have become an internal one. If set up properly accessing the external candidate functions should be no longer possible as the internal candidate should not have the authorization for that.
For the second question: If an employee leaves the company, his candidate is transformed to an external one. This processing is much easier as only as described above the system sets the INACTIV flag in IT 5102 (table HRP5102). The candidate is still linked to a employee ID which is basically the indicator for being an internal candidate but this flag is overruling this. The reason why the link to the employee ID is kept is the posibilityof a later rehiring where a candidate get his former employee ID back. For testing purposes it is important to know that this is the only time dependent processing in the integration. So if you run the standalone scenario and enter an employee leave one month in advance the candidate will be put in the table T77RCF_P_STAT during ALE and a periodical service will do this when the leave date is reached, other than for example a change of adress which is processed directly in e-recruiting no matter if you maintained it months in advance. Again if set up correctly the system automatically changes the reference user for the candidate so there is no need to manually withdraw the authorization for the internal candidate functions. Only tricky thing here is granting the candidate access. As far as I have seen the newer releases set the old user as alias which could be used to log in (can't tell if this is so for every release / sp). But if you use SSO the candidate does not know his password and cannot request one as his email is the company one no longer accessable after leaving. Here you have to find a solution how to deal with the scenario.
Best Regards
Roman
|
|
|
|
|
