Alternative to Report RCF_CREATE_USER

Question

Hi Friends
  I am currently working to get the E-recruiting system up. Currently, I am using the report RCF_CREATE_USER to create the User Id and candidate. But in the documentation of the report, it is said as follows:
  'Note that this report should be used for exceptions only. As a rule, external candidates register using the appropriate Web scenario of the application, and employees are imported from an HR system using the master data interface (ALE)'.
  Can anybody please suggest a detailed procedure. Thanks in advance.

Answer 1

Hello Sandra,
i am not sure if this is still a valid issue but in general first thing to know is the landscape you plan e-recruiting to be installed. furthermore the release installed for e-recruiting and the hr core system is important.
if you install e-recruiting on the same system the hr core (admin, org. mgmt, payroll) is running, the integration depends on the e-recruiting release. for e-recruiting 300 the integration is asynchrous. You have to run the SYNC_PERSON report mentioned above periodically to make internal candidates from all employees and keep their data up to date. If you install e-recruiting 600 there is a synchronous integration. Setting up this integration is one of the most difficult task in the technical steps of an e-recruiting implementation (the documentation is not really complete ;o(). If it is set up completely, every change in the hr master data is directly transfered to the e-recruiting. For the initial transfer there is report HRALXSYNC which has to be run once for all employees to create their internal candidates - but this report needs the full integration configuration.
if you install the e-recruiting on a separate system the creation of internal candidates is done by the ALE integration. The configuration depends in parts of the releases of e-recruiting and hr core system, esp. when it comes to the IDOC types. The standard configuration transferes parts of the organizational structure (O, S, C) and creates internal candidates from employee infotype 0000, 0001, 0002, 0006 and 0105 (Subtype 0001, 0010). While the transfer of the organizational entities is standard hr data distribution, the candidate creation is implemented in BAdIs an can be changed up to a certain point.
For the initial data transfer there is the transaction PFAL which is run from the HR Core System to create IDOCs for all Org. entities and Employees. After the initial transfer a periodical job has to run every day to process the hr change pointers.
Some configuration options are strongly recommented from my experience to avoid problems when booking the IDOCs into e-recruiting, like asynchronous import and no packaging. Furthermore everyone transfering IT0006 should have a look at a new note, released only some days ago, which is supposed to solve a problem with adress information update existing since e-recruiting 200.
For more detailed information please supply additional information of you landscape.
Best rgds.
Roman Weise