E-CRM: Name Type is not updated correctly in CRM when using PERSON_BASIC_SYNC to Sync Names Type from HCM to CRM (Doc ID 3030531.1)

Last updated on JUNE 27, 2024

Applies to:

Symptoms

Issue in syncing names data between HCM to CRM using PERSON_BASIC_SYNC

There is an issue in PERSON_BASIC_SYNC to sync names data between HCM to CRM in a specific scenario, when there is a historical name in HCM with name type other than Primary, and then we are trying to add a new effective dated row with the same name but with the name type as Primary, then PERSON_BASIC_SYNC is actually updating the historical name in CRM, the problem here is that the updated row has a name type ALTERNATE and primary indicator as 'N' instead adding a new row with the name type as PREFERRED and primary indicator as 'Y' in CRM, this is leading to mismatch in the names data between HCM and CRM.

The issue can be reproduced at will with the following steps:

1. In both HCM and CRM, activate PERSON_BASIC_SYNC (PeopleTools > Integration Broker > Integration Setup > Service Operation Definition)
2. In HCM, navigate to Workforce Admin > Personal Info > Modify Person, open an existing employee
3. Add a new effective dated row with the same name but with the name type as Primary
4. In CRM, it shows as Primary but with Name Type as Alternate instead of Preferred

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.