Alternative to Report RCF_CREATE_USER

[Former Member]

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.

[Former Member · Accepted solution]

Hi Sharath,

If you try running report hr_sync_person you can do this for mass groups of people or for all changes since a set date. This is better than using the rcf_create_user report.

Regards,

Jon

[Former Member · Accepted solution]

Hi,

you can also login in E-Rec as an admin (hrrcf_start_int & rcfSpId=0004), there you have a function "User Maintenance" where you can also create or change the E-Rec users.

Regards,

Thorsten

[Former Member]

Hi Roman

We are implementing our eRecruitment in version 6.0 in a standalone systeme.

Our HR system is on R/3 entreprise and we using ERP 2004

Which strategy should we adopt then ? ALE is there a config to do ?

Thank you

[Former Member]

Can someone please explain to me the process around importing employees from the HR system using the master date interface (ALE)? Is it a periodic batch program running on the HR system that triggers IDOCs to be sent to the E-recruiting side? What idoc message type does that require? The documentation on this is almost non-existant.

Please contact me at nathancmartin@hotmail.com if it is too complex to expand on this forum

Thanks

[Former Member]

Just in order to clarify the difference between HR_SYNC_PERSON and RCF_CREATE_USER.

HR_SYNC_PERSON is just applicable in ECC systems. In E-Recruitment standalone systems it is not existing.

RCF_CREATE_USER is just used, within test systems, standalone systems without internal candidates or standalone systems without connection to SAP HR systems. The recommended way to create internal candidates is using ALE.

The option "Create User" within the administrator page is nothing but a BSP frontend for RCF_CREATE_USER.

In ECC systems this report must not be used!!!

[Former Member]

Hello,

We are in the testing phase for implementing E-recruiting on a separate box from our R/3 system. I have used the transaction PFAL in the R/3 system to transfer the HR data from infotypes 1001, 1000, 0000, 0001, 0002, 0105, you can use 0006 also. PFAL transaction creates the IDOC information to transfer into the E-recruiting system. You need to build the ALE model before using PFAL. Within PFAL, you can specify to overwrite all the data each time it is executed or setup a change management background job and frequency of when the data needs to populate or repopulate changes in the E-recruiting system. The message type within PFAL displays as HRMD_ABA. Table T000 controls this with the client assigned to logical system. Message type is from table EDIMSG in our system.

For ALE you need to setup the RFC connections, ports, logical systems, partners, and some configuration in the T77S0 and T77AR tables. After this is done you can set up the ALE model. The message type depends on your R/3 system and E-recruiting system levels. Pick the latest one that matches both environments, for us it matched to HRMD_ABA04 IDOC type for our release levels. You can set up the distribution of data to collect idocs or process immediately.

We have transferred the data using the IDOCS from our development, test, and QA clients to the same in E-Recruiting clients.

Hope this helps,

Cindy

[romanweise]

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

[Former Member]

Hi Roman Weise,

We are implementing e-Recruitment.

I just want to know whether we can transfer IT 0022 IT 0023 IT 0024 data using the standard IDoc type HRMD_A07

thanks for your help.

Jayanthi.K

[romanweise]

hello,

trnsfering the data should be possible but as the data is not stored in the same data structures it comes from out of the hr core system a customer implementation would be necessary as the standard implementation of the inbound business add ins, sap delivers, do not cover these infotypes.

I never checked if the data is really comparable as we use other techniques for making former employers and stuff available in the e-recruiting. But even this is very rarely as most companies judge their employees by there performance in the own company much more than being interested in what they have done before.

Best Regards

Roman Weise

[NashT]

Hi Roman,

you seem to know quite a bit on this topic.

we are starting to implement eRecruiting 6.0 and will have eRec in a separate system (stand alone).

Our SAP-HR data resides in our ECC 5.0 and we plan to feed eRec with HR data via ALE

As I understand, In a distributed landscape like ours (where we have our SAP-HR data and eRec data in separate systems), we have to use ALE to convert all internal employees from SAP HR to internal candidates instead of using RCF_CREATE_USER.

Do you have any documentation that shares:

1. How to run ALE for e.g. do you run with all objects at once or is there a sequence like for e.g first orgunits then jobs and pos then employees etc. We also have a qualification catalogue set up in our HR source system. Do you need to use an eval path or do you leave it blank so it converts all infotypes. What info do you sent from HR to erec and vice versa.

2. steps in terms of how to set up ALE e.g. I understand you have to activate BADIs: HRALE00SPLIT_INBOUND and HRALE00INBOUND_IDOC).

3. Once I am able to transer HR data (e.g. email and address from IT0006), how do I check in eRec if transfer was successful i.e. which infotype/table stores the email and the address of a candidate. It is not in IT5102 (candidate info).

Thanks

Nash

[Former Member]

Dear Nash,

My apologies for answering a question intended for Roman.

I thought the following thread maybe of some assistance to you. Hence the intrusion:

As to how to check the address & emailid etc,

Whenever NA is created for a P in the eRec system there is a BP object(Business Partner) which is also created. & the address & email id should be reflected there as in eRecruiting, these details are picked from the relevant BP for a NA.

So, the relation would be something like this:

P->CP

CP-> BP

CP-> NA

CP-> US(User)

If the data transfer is successful, you can check for the following relations in the infotype 1001 in the eRec system.

For a particular Na, pick the relevant BP & check in transaction BP to see for details like address.Alternately, you can also check table BUT000.

Regards,

Sowmya

[Former Member]

Hi Jon

Thanks a lot for the clarification. I will try this out. I have a small doubt. I have already run this report and all the employees are processed. At this point can I perform the steps which u have mentioned after creating the users in SU01 and then run the report HR_SYNC_PERSON again?

[Former Member]

Sharath,

This will only be useful if you select the option

CHANGES SINCE. Otherwise the same old data is processsed.

regards,

Bharat

[Former Member]

Hi Jon and Thorsten

Thanx a lot for the help. But i have one more doubt. In the report RCF_CRETE_USER, it asks for the user name and when I execute it, the given User name is generated. Then I go to SU01 and assign roles to that user. But when I use HR_SYNC_PERSON, it generates the User name is same as PERNR. But when I go to SU01, it says 'User does not exist'. Can u please correct me, if i am missing anything.

[Former Member]

Hi,

To use HR_SYNC_PERSON you need to have created the user in SU01. You also have to ensure that the user has a HR record created (PA40 - hire). In their HR record they <b>must</b> have their <b>infotype 6</b> (address) and <b>105</b> (email and username-from SU01) completed. Then when you run the report this should create the candidate with the details from their HR record.