E-Recruiting: Batch Creation of Applicants

Question

Hi Experts,
I have the following questions and would really appreciate if anyone could help:
1) My job portal is an external system and I need to import in the applicants into E-Recruiting.  I know E-Recruiting does not have a BDC concept.  So how should I do it?  Is there a standard function module/program which I can call to create the application and necessary relationship tables like HRP5102?
2) In infotype HRP5102, for the Status field, there are two possible values for 'released' mode (1 and 2).  What is the difference?
3) In infotype HRP5102, for the ISTAT field, what does the different status value means?
Will appreciate if there are any documentation on it as online help did not elaborate much.
Many thanks.
william
Edited by: William Toh on Mar 16, 2008 9:34 AM

Answer 1

Hello William,
for question 1:
E-recruiting is does not support an complete interface for data maintenance like the BAPIs of the Business Partner. It has carious service classes to support customer developments but replacing the whole candidate frontend by a non sap solution will generate very huge expenses.
I am not sure why you do not want to use the frontend delivered with e-recruiting. It can be integrated into company web appearance which would be much easier and probably cheaper,too.
Perhaps you can highlight some reasons / restrictions which lead to the conclusion that you can't use the sap delivery here.
for question 2:
The reason for the 3 domain keys for only 2 values is a historical one. When the development of e-recruiting started the status management for candidates had 3 different value based on the assumption that candidates will be in the pool for a lon period of time:
- "not searching" - a candidate which has been in contact with the company but for any reason does not currently look for a new position, e.g. he just changed jobs. of course he stays in the system for identifying former contacts and perhaps in a year or 2 he is interested in a job again.
- "passive searching" - a candidate which is more or less satisfied with his current employment but won't complain about an new offer for a new challaging task or enough cash
- "active searching" - a candidate who is really unsatified with his current job and will take any acceptable offer
Anywhen SAP came to the conclusion that these 3 candidate states are very difficult to handle. In the end most candidates will take a new job if you put enough money on the table. So SAP changed the candidate status to "I only want to be checked on the positions I choose" (= profile locked) and "If you think you have a job I might fit just feel free" (= profile released). It seems that SAP was not really sure where they used 1 or 2 so they just gave both keys the same description. Within coding profile status is usually checked against key 0 with EQ or NE.
for question 3:
The standard HR components use a status concept for some of the objects e.g. an organizational unit can have different states (planed, requested, activ, ...) and the relation to other objects derive this concept. As all HR components use the same database structures e-recruiting infotypes have this field in their key structures, too. But e-recruiting does not use this concept so this field always should be 1 in all datasets.
Best Regards
Roman Weise