cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

CP-S relationship not delimited and INT-->EXT candidate not changed

Former Member
0 Likes
259

Hi gurus

I have noticed that when an employee leaves the company (terminate action) there are 2 problems:

  1. The candidate's reference user is not changed to RCF_CAND_EXT
  2. The CP-S relationship is not delimited, which means that the person still holds the position, when I look in PPOSE in E-Recruitement.

I discovered that employment status "0-Withdrawn" was excluded in the distribution model (BD64) on the HR side, so I changed that and now the employee is indeed sent, but on EREC it still makes no difference.

Another thing which seems "weird" to me is that terminated employees all get position "99999999" in HR with end date 31.12.9999. This "assignment" is also included in the idoc to EREC.

We use EREC as stand-alone and are on ERECRUIT 604 0010. Note 1643666 is already implemented.

Looking forward to hearing your thoughts.

Regards

Aage Kold Jensen

Accepted Solutions (1)

Accepted Solutions (1)

NicoleGeischnek
Product and Topic Expert
Product and Topic Expert
0 Likes

Hello Aage,

This was corrected in the last months. Please implement notes 1618643 and 1716811 (for the positions 1601361 and 1620244).

Best regards

Nicole

Former Member
0 Likes

Hi Nicole

Thank you very much for your prompt respone. I have done a little research:

1618643 - Not relevant, our scenario is I2

1601361 - Not relevant because of SP level

1620244 - Not relevant, no employees with multiple positions

1716811 - I am unsure about this one. HR employees access the BSP pages and I believe recruiting through the portal also calls those pages. But both internal and external candidates apply through WebDynpro and have a user and password on the backend. Looking in note 1017866 I find it difficult to determine our constellation and therefor if 1716811 is relevant for us. My guess is we use constellation "1".

Best regards

Aage

Answers (0)