SAP E Recruiting - Manage future leaving employees in standalone EREC system.

[Former Member]

Program HRALXSYNC

We are using E Recruiting system as a separate server and employee master data comes via ALE IDOCS

1. Is report HRALXSYNC need to run in case of separate server also?
2. It is creating user ids which we do want as our system administrator creates user ids and user ids comes from central CUA system with Info Type IT105.

Can we stop this background job as it is creating unwanted user ids in our SAP E- recruiting system, as mentioned in our case both the server are different and ALE being used for master data flow.

Processing of Future leaving / terminating employees

If we stop this Background job then how the suture leaving / terminating employees will be processed in our SAP E-Recruiting system.

In our case both the business function HCM_ERC_CI_3 is active and as per OSS note 1779471 (ERE: Information for processing future) Leavings it is mentioned to run program HRALXSYNC.

1.      Considering this behavior do we need to start periodic service PROCESS_CAND_STATUS_CHANGE.

2.      Is there any way program HRALXSYNC do not create user id ?

[NicoleGeischnek · Accepted solution]

Hi Sandeep,

I anwered the first questions in your other post.

The future leaving questions are explained in the wiki page sent also in that post (Incorrect reference user assignment - ERP Human Capital Management - SCN Wiki).

Regards,

Nicole

[Former Member · Accepted solution]

Hi Nicole

Thanks a lot for your reply.

As you said job HRALXSYNC is must require also in case if E Recruiting system running on separate instance also along with ALE master data distribution.

- Every one will not have user id assgned then this job should not create random users. Generation of multiple users may impact licences. 

How we can stop randon users creation by this job?

- Also we have multiple companies rollout implemented in E recruiting system. And one company internal candidate should not apply job to other company.  In this case if this job creates a random internal candidate user then they got assigned RCF_CAND_INT reference user and with this they are able to apply to any company. Whic is a wrong business process for us and a big issue.

- For future leaving employee - they are not getting convert to external in our system. Meaning this job do not assign RCF_CAND_EXT to future leavinf employees.

Please can you help us, Highly appreciated your inputs in this direction.

Thanks and regards

Sandeep

[NicoleGeischnek · Accepted solution]

Hi Sandeep,

Not only HRALXSYNC automatically creates the users -> the ALE idoc processing does too. E-Recruiting needs a user otherwise it won't work.

If you have differenct companies in one client on E-Recruiting side, you can eg. restrict the job search due to branch assignment of the employee for example.

The future leaving is done via HRALXSYNC - see other post and the wiki page I sent.

Regards,

Nicole

[Former Member]

Thank you so much Nicole for your sugestions.