E-recruitment Applicant data transfer to PA

[vtgopalraj]

Hello,

We are running E-rec in a different instance and have completed the ALE setup. Iam able to get the applicant data in PA48 in my HR system.

While performing the hiring action, i can get the personal data, organisational assignment, address infotypes to be updated but could'nt find education, qualification and previous work experience data getting updated in HR system

Iam not sure if i have to define any filters in ALE (or) delete any filters...

Can some one help with info?

Thanks

G Raj

[Former Member]

Hi,

What congifuration we need to do to see the candidate information in T752F table in HR System.

Thanks for your response on this.

[romanweise]

Hi,

you need basically two things. First of all you need an activity of category 06 data transfer for the candidacy object which should be assigned to one of your process steps so you can create it in the candidate selection.

Furthermore you have to specify the RFC connection from SAP E-Recruiting to HR Core server. This is done in the IMG under SAP E-Recruiting -> Technical Settings -> Set System Parameters Parameter RECFA HRRFC.

When this is done you can create the activity and hit the data transfer button in the view to transfer the data to the HR server. When this is done you should find the table filled.

Best regards

Roman

[Former Member]

Hi Roman,

Thnaks for the detailed explanation.

We are implementing E-rec 6.0 with EHP4 on ECC 6.0 as a standalone solution. My core HR system is in SAP 4.7. I need couple of clarifications on the above architecture.

- Do we require employee data in PA tables in ECC 6.0 ?

- My understanding is, If we transfer Object type u2018Pu2019 from SAP 4.7 to ECC 6.0 using PFAL transaction it will create Business Partners ( Object type BP) in ECC 6.0 system. All the PA information (Infotype 0000,0001, 0002 and 1005) coming from 4.7 will reside in E-rec tables in ECC 6.0 u2013 Is my understanding is correct ?.

- We are creating requisitions in E-rec with respect to Vacent Position. So we need to transfer OM data (Orgunits, Jobs, Positions and its relations) from SAP 4.7 to ECC 6.0 u2013 Is this is correct or not.

Please correct me, If am wrong.

[romanweise]

Hi,

as a general hint - check note 997181 there are good documents attached which describe the integration scenarios for the different releases.

With EhP4 sap is replacing the ALE solution for e-recruiting. Before e-recruiting used an own implementation for HR BP integration. With EhP4 this is changed. In general it supports 2 different scenarios called I2A and I2B. I2A is the standalone instalation with only e-recruiting installed on a WebAS server. in this case the ALE transferes the PA data into new basis infotypes 558* from there the integration creates CP, BP and NA. The I2B scenario uses an ERP installation which only has e-recruiting in use. In this scenario ALE transfers PA infotypes 1:1, 0001 -> 0001 etc. The integration creates CP, BP and NA based on this. For details on the 2 scenarios check the note mentioned above there is a description for standalone instalation with capters especialy for EhP4.

If you want to use the org. assignmet for requisition maintainence (assign positions to requisition etc.) you have to transfere S, C and O object types with ALE.

Best Regards

Roman

[Former Member]

Hi Roman,

The I2B scenario uses an ERP installation which only has e-recruiting in use. In this scenario ALE transfers PA infotypes 1:1, 0001 -> 0001 etc. The integration creates CP, BP and NA based on this

In the above case, do we need PA configuration in ECC 6.0 (Where only E-rec is active).

Thanks a ton for your reply.

[romanweise]

Hi,

there is nothing written about configuration for PA in the documentation but I fear if you do not have some basic settings the ALE will fail due to inconsistencies.

What I tested so far is a TMC scenario working similar but only creating CP and BP after ALE without e-recruiting candidate. In this case the customer did not want to distribute the IT 0006 for address. But the HR BP integration which is also used by e-recruiting won't create a BP without address except you have some customizing for HR personal area done (some strange thing resulting from CRM requirements).

I expect that at least the base configuration for attributes in the infotypes based on customizing tables have to match (form of Address, Title, personal area, ...). But this needs verification. Perhaps you could reduce the necessary effort needed by creating only one personal area and subarea etc. and overwrite the IDoc accordingly. If the information is not needed in E-recruiting.

Best regards

Roman

[Former Member]

Roman Wise,

If HR data sits in PA infotypes, Then how can we call it as standalone ??... Standalone means only E-rec in that instance. Please correct me. If i am wrong. Any suggestions on how to conclude that we need PA config or not...

Thanks,

Sudhakar.

[romanweise]

Hi,

originally (prior to EhP4) e-recruiting standalone meant a WebAs with only e-recruiting installed. With EhP 4 we have the I2A and I2B scenarios. I2A is still WebAs with e-recruiting only, while I2B means a ERP installation with only e-recruiting used. Based on the fact that using I2B requires a modification instead of something like a T77S0 switch, I assume it was not something sap planned to build but something someone anywhen found out by chance and put into documentation.

I think there are not many I2B projects up to now. I have most know how of this scenario derived from a TMC consolidation system scenario which is similar to I2B. In my oppinion the necessary configuration depends on the data you transfer. You need IT 0000, 0001, 0002, 0006 (Subtype 0001) and 0105 (subtyoes 0001 and 0010). So you need at least the config for all these infotypes (the hiring actions, the employee areas, the titles, ...) except you blank /default some of the fields in ALE e.g. move all employees to one dummy employee area / subarea.

As I am usually not feared of systems and their adminis I would in last instance just request a system full backup, set up the ALE and throw in what I have in production HR core server and see what happens. Reroll the backup after you found out.

Best Regards

Roman

[Former Member]

Dear Roman,

With upgrade from EP2 to EP4, SP5, we have faced several issues. The most critical now is being on Data Transfer to HR system for hiring that is jeopardising out go-live activities.

We have two issues here, will you be able to kinldy help please.

Issue 1: In data transfer activitythe position is not getting defaulted although NB to S relationship exists in hrp1001 of e-rec . Hence, manually one has to give the position in the activity. Why the psosition and org unit are not getting defaulted when is do this activity?

Issue 2: In GON PA48, after the VR number is given, the position that is maintained during data transfer imanually s getting defaulted but the EG, ESG, PA, PSA details are not coming that is maintained for the position. Why is the PA, PSA, Org untit details, address a re not appearing here?

The RFC connection is working fine yet these issue?

I desparately need some input from you. Kindly reply.

Regards

Dhiya

[Former Member]

Hi,

These fields you have mentioned are not updated correctly from

E-Recruiting because of following:

supported infotypes for transfering data from the E-Recruiting to the

HR-System are the PA infotypes 0,1,2 and 6. There are 15 fields sent to

pa48 if they were filled in the E-Recruiting system, which are:

- forename, initials, surname

- gender

- birth date

- correspondance language

- address (street, city, streetcode, region, country)

- hiring date

- organisation unit

- position

- personel number (for internal candidates)

So the title, the qualification and past experience and all the rest are not included in the

standard fields. What you can do now is to create an own personnel

action for hiring of the E-recruiting system where you are using

all these fields, because then for PA30 they will be automatically

filled with these values.

Hope it helps!

Arpita