SAP E-Recruiting - strange behaviour HRALXSNYC

[Former Member]

Hello experts,

we are implementing for on of our customers SAP E-Recruiting based on EHP4.

The system architecture runs on the integrated scenarion. This means e-recruiting and HR are on the same system.

For that reason we are using the wonderful end extremly well programed HRALXSYNC to create internal user.

Unfortunately we are getting some strange system behaviours during running hralxync.

All employews will be created with assignment to the reference user RCF_EXTERNAL_CAND. ???????

After debugging hralxsync i found the reason fo that mistake. hralxsny call a method form cl_hrrcf_candidate->is_employee.

So for that method the return value is always false. This means the employee is not active and has to be handled as an external user.

After checking what exactly habben in metho ->is_employee if found a logic witch proves if the candidate has an entry in hrp5102.

OK now the main problem........

The system of our customer has 700000 entries in HRP5102 and 57000 entries in HRP1000 fo object 'NA' without running SAP E-Recruiting.

How can this be possible???????? HRP5102 is reserved for SAP E-Recruiting, isn't it?

After doing some research of older projects within this company we find a project from the year 2006.

--> Implentint SAP E-Recruiting based on EHP3 which was stopped before go-live.

Could it be possible that from the old ehp3 project is a badi still active which is responsible for the integration from PA to EREC or somethin else?

What could be the reason for that entries in HRP5102?

Many Thanks

Marco

[christine_morin]

Hello Marco,

Yes, BAdI HR_INTEGRAT_TO_EREC is responsible for creating the corresponding BP and NA objects when the employee is hired using PA40 transactio. Please make sure that you have the recent notes implemented :

1437387 HRALXSYNC writes change pointer even if BP is unchanged

1499589 HRALX: PPOM*: Business partner not saved after creation

1582647 Memory not refreshed correctly in case of multiple LUW call

1490909 Exception occurs in method get_ee_details_from_cp

1540502 EREC: ALE Inbound Errors - Address doesn't exist (AM010)

1556918 HRALX: Customer not created from business partner

Hope it is helpful,

Kind Regards

Christine

[christine_morin]

Hi Marco,

The report first changes and creates the assigned BPs. then it creates the missing candidates. To do this, the report calls the BAdI implementation HRSYNC_P. The following activities are executed within the DO_POST_PROCESSING method if no candidate has not been created yet for the personnel number :

- The method reads the user name and the e-mail address from the data in IT0105.

- The method uses the BP number to create an internal candidate NA and link this with the CP object.

- The method also creates an entry in IT5102 for the candidate and sets the indicator IS_INACTIVE to FALSE if idoc data from IT0000-STAT2 = 3.

I would ask you to delete the candidate object NA relation in HRP1001 and afterwards run again report HRALXSYNC for this object to overcome this data inconsistency. It is possible that your old ehp3 system has created all these NA objects in HRP5102 but now you need to know if they still exists on the system or if you want to delete them.

If you want to clean up your system :

1. delete CP with RHRHDL00

2. delete NA with RHRHDL00

3. delete BP with BUPA_DEL

4. delete the user with SU01

but of course this can only be done if no other relations (object NE, NF) are still existing.

Hope it helps,

Christine

[Former Member]

Hi Christine,

amny thanks for your reply.

The cleaninf of HRP1000, HRP1001 and HRP5102 with relatet objects na,cp.... was also my first intention.

But than we recognize that there are new entries in HRP5102.

This means some interface, badi or whateever still creates entries in that table.

So I think first of all I shou find the reason for that entries.

What we could see is that if someone modify a PA infotype over PA30 a entry in HRP5102 will be written or a entry in HRP5102 will be determined.

So this means somethin from PA is triggering the entries in HRP5102. Could this be a BADI like the BADI

HR_INTEGRAT_TO_EREC which is still active?

Many Thanks!

Marco