Problem with ALE data transfer to E-Recruiting in Test Enviroment.

[Former Member]

Hi,

We are on E-Rec 604 with seperated standlone e-rec system.

We have configurated the ALE in Development Test and all works ok, but the test enviroment doesn´t work correctly... and I don´t know what is the problem.

In Development Enviroment, all object are created ok and internal candidates are created with (CP, BP and NA).

But in Test enviroment there must be something wrong... All idocs arrives at e-recruiting in status 53, so I assumed that all works ok, but now, one week after, doing some testing I have found that when the employee has the infotype 105, subtype 0001 the internal candidate is never created, and sometimes when the employee doesn´t have it neither created.

No errors in slg1, no errors in st22

I can´t understand anything... Probably I forgot customizing something in test enviroment... But I have checked all that I know and I don´t find anything...

I have checked those things:

T77s0:

HRALX HRAC X

HRALX OBPON ON

HRALX PBPHR ON

HRALX USRAC X

Badis:

HRSYNC_P CONV_HR_DATA_TO_EREC (active)

HRALE00INBOUND_IDOC HRRCF00_INBD_NEWMOD (active)

HRALE00SPLIT_INBOUND HR_INB_PROCESS_IDOC (inactive)

HRALE00INBOUND_IDOC HRRCF00_DELETE_SPREL(inactive)

HRALE00SPLIT_INBOUND HR_INB_PROCESS_IDOC(inactive)

HRALE00INBOUND_IDOC HRRCF00_DELETE_SPREL(inactive)

And in the class CL_HRRCF_SYSTEM_CHECK we created an enhancement that sets the atribute IS_STANDALONE to TRUE.

I've forgotten something?.

Could someone guide me, please.

Best regards,

Esther

[Former Member]

Hi Esther,

Kindly check if the email ids are maintained for the candidates on IT105 subtype 0010. Unless an email id is maintained, the system will not create the BP for P. Also make sure that the users are maintained with a valid email id on user master (SU01). As of EhP4 SP04, this field has become mandatory for the users to be synchronised on HRALXSYNC.

[romanweise]

Hi Esther,

something which caused me trouble when setting up the ALE the first time for EhP 4 was a change required in the filters for the distribution model compared to EhP 3 and earlier. For EhP 4 the address (IT 0006) is no longer optional, it is now required. So you have to include ITs 0000, 0001, 0002, 0006 and 0105 (subtypes 0001 and 0010) in the filter for the P object in the distribution model. Furthermore you have to include the P -> CP relation (not the CP object itself but the record of IT 1001 with the P to CP relation).

Kind regards

Roman

PS: The modification in class CL_HRRCF_SYSTEM_CHECK i only required if you eRec installation is a full ERP installation instaed of only a WebAs plus eRec component. If you really have the full ERP installation there might be trouble because of the installation. Contrary to what SAP writes in note 997181, the HR - ERec integration for both installation options (I2A and 2B) behaves not completly the same. The HRALXSYNC processing does not process some steps in I2A as it interrnally determines that there is no ERP installed and some coding is not there so it is skipped. 

[christine_morin]

Dear Esther,

In release 604 as a standalone e-recruiting system, you should only have these BAdIs activated:

HRSYNC_P CONV_HR_DATA_TO_EREC

HRALE00INBOUND_IDOC HRRCF00_INBD_NEWMOD

As of release 604, the inbound processing lies in the method POST_PROCESS_IDOC of the implementation of the BAdI. The method DO_ALE_POST_PROCESSING of class CL_HRRCF_ALE_EE_INBOUND perfoms these activities :

- IT0105 is stored in IT5585. Then IT5585 contains the user for SAP E-recruiting

- The method uses BP and CP to create an internal candidate NA.

Please make sure you do not have any import locks in table T77TR for object CP.

Hope it helps,

Kind Regards

Christine