ERECRUIT - Inbound ALE deletes email address for internal candidate profile and BP

[NashT]

INBOUND ALE DELETES EMAIL ADDRESS FROM CANDIDATE PROFILE& BP

We have upgraded our SAP eRecruiting system from ver 6 EHP3 to EHP6. We have a distributed scenario where our SAP-HR (ECC) system and SAP eRec are on different boxes and we use PFAL to distribute employee and organizational data from HR to eRec.

After the upgrade, we have the issue that everytime we run PFAL for object 'P', the private 'email address' that was previously entered in the internal candidate profile gets deleted and the internal candidate is forced to re-enter the email address. Before the upgrade this was not happening.

Before the upgrade we have always enabled the internal candidate to enter the private email address directly in eRec (in the personal data section). The reason is that many employees in our organization don't have a corporate email account or office PC. For e.g. outside (non-office based) workers. We allow them to register & update candidate profile with their private email address (gmail, yahoo etc) for erec correspondence purpose. Therefore we don't distribute IT0105 subtype 0010

Has anybody ran into this issue and any suggestions.

Here is the gist of response we got from SAP,

Normally, internal candidates are not allowed to change their e-mails on E-Recruiting side, the corporate e-mail from infotype 0105 subtype 0010 usually takes over when the candidate is hired.  This is a premise that E-Recruiting was built on, that every employee would receive a corporate e-mail upon hiring. Currently, even if you do not distribute infotype 0105/0010, the code that handles integration with business partners sees that as the employee doesn't have an e-mail on the data distributed from HR, the corresponding business partner shouldn't have either, and removes it

Nash

City of Vancouver

Canada

[romanweise · Accepted solution]

Hello Nash,

since EhP 4 SAP uses a different implementation for ALE, documented in note 997181 you probably know. It changes some of the detailed processings (different BAdI implementation, use of infotypes 558X, transfer of central person required). This includes the E-Mail address and probably leads to your issue.

A soution for your problem might be a new function delivered in the customer connect program for eRec which has recently been completed. Check for note 1977871 and 1963021. This new function allows to have a business and a private email address for internal candidates in parallel.

Kind regards

Roman

[NashT · Accepted solution]

Hi Roman,

Thanks for your input. I expected that if there is one person that would respond, it would be you.

Yes, you are right about the recently completed notes. SAP did point out the 2 notes that you pointed out earlier but upon later review, SAP realized that they won't work for our scenario so we had to reverse the note. As per SAP, note 1963021 doesn't support when there is no corporate e-mail address. Candidates cannot have 'only' private e-mail. So note 1963021 is not the solution for our scenario where there are lot of employees that are not office based (e.g. outside workers) and don't have PCs, don't have a corporate email address and just have a private email address.

I guess we'll have to do a core mod because it is a show stopper for our upgrade Go-Live

core mod to CL_HRRCF_ALE_EE_INBOUND=>UPDATE_CANDIDATE to not update the email address

Nash

[romanweise · Accepted solution]

Hello Nash,

thanks for the update.

so far I was not aware that the solution is currently not supporting a scenario where some internal candidates do not have an internal email address. I know some of the customers which registered for this customer connect request and most of them have exactly the situation that certain groups of employees e.g. in manufacturing do not have PC access and therefore have no internal mail address.

From my perspective this is a bug and we will have to take this for discussion with SAP.

Kind Regards

Roman

[NashT · Accepted solution]

Hi Roman,

Yes our team also agrees with you that this is a 'product error' but we could not convince SAP. From their position they say that this is a per design and the premise is that everybody needs to have an email address in IT0105 subtype 0010.

Since we have tight deadlines for upgrade we decided to go core mod and we are in the process of testing if this works. sofar so good.

Thanks for your input and now we know that we are not alone that have this issue.

Nash