SAP E Recruiting - Manage future leaving employees in standalone EREC system.
We are using E Recruiting system as a separate server and employee master data comes via ALE IDOCS
- Is report HRALXSYNC need to run in case of separate server also?
- 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 ?
Nicole Geischnek replied
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.