One gobal e-Recruiting with different lokal HR installations

[Chris_S]

Hello everybody,

we actually have a global e-Recruiting installation, but our HR Systems are decentralized. We have one for Europe, one for North- and one for South America.

All these countries have to use the global e-recruiting System, so we created an ALE connection from every HR to e-Rec.

In the ALE outbound-BAdI we modify the ObjectID of P and CP and add a prefix to keep the numbers unique in e-Rec.

As far as I know SAP recommends a 1:1 system constellation with one e-Rec and one HR system.

This becomes even more relevant by starting to transfer the hired candidates back to HR.

At the beginning of our project we were not interested in that feature because the standard functionality offers only a few information like Name, Address, ... .  We decided to make the entry in HR 'manually'.
Some countries would like to have that transfer and the question comes up how to differentiate between the target HR system?

Are there any ideas how to handle that or any suggestions about that topic?

The system parameter RECFA HRRFC also allows only to maintain only one RFC connection to one system.

Thanks for your answers and hints,

Chris

[romanweise · Accepted solution]

Hello Christoph,

data transfer to different HR core systems is not supported out of the box. In your scenario I recommend to define 3 activity types of the data transfer activity category ("data transfer EU", "data transfer NA" and "data transfer SA") as it is more flexible than directly linking to any attribute of the requisition. So setting up these activity types would be the first step.

In the second step you have to change the method TRANSFER_DATA of class CL_HRRCF_ACT_DATA_TRANS_RECORD by either adding a modification or an overwrite enhancement. This is the method which actually contains the RFC call to the HR core system. You read the activity type of the currently processed activity (call  method GET_RECORD or simply use the existing local variable LS_RECORD. Specify the matching RFC connection for each activity type and adjust the function module call(s). If you are using the same name for the RFC connections on development, test and production systems a CASE statement will do. If you use different names I would personally add a custom table with client, activity type, rfc connection and delivery class A so you can easily define the correct RFC name on every layer of you system landscape.

If you have any doubts in your recruiters picking the correct data transfer activity you can support them by providing proper process templates. If this is still not enough you could have separate recruiter authorization roles für EU, NA and SA which  are restricted to only their activity type using the authorization object P_RCF_ACT.

Best Regards

Roman

PS: if you are using the eRec system also for internal hiring you have to redo the changes in the employee id for the internal candidate you made in the ALE outbound BAdI. This you could do in the same method.    

[Former Member]

Hi,

The ALE input from SAP to E-Rec is been understood as being controlled with the prefix in P and CP. However, to transfer the data for hiring into the respective HR systems can be enhanced with the requisition details referred and then transferred in the ALE to respective HR system.

Example: If the requisiton has been raised for Europe (company code), should transfer the candidate data to Europe HR system.

[Chris_S]

Do you know where to enhance the system to make the decision possible concerning to the country or the selected company in the requisition?

[Former Member]

maybe you can create an interface on EREC to the different HR systems with a filter on country to a ZTABLE in the HR systems. Than create a "ZPA48" to read the Z table and start the hiring for example.

Or create a ZPA48 to read the EREC system via RFC (filtered on country). That's maybe better.