Primary Name Issue In Integration Between Hcm And Crm (Doc ID 2127353.1)

Last updated on SEPTEMBER 01, 2016

Applies to:

PeopleSoft Enterprise CRM HelpDesk for HR - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

Currently, names in CRM do not have a Status or an Effective Start/End Date logic (like instead it exists for Contact methods - email, address, phone). This creates a problem when CRM is integrated with HCM and when users add new names to Persons (see Business Scenarios below). Customer would like CRM Development to create and populate a different table in CRM like PS_NAMES table in HCM. Such new CRM table should be in sync with the content of PS_NAMES table in HCM: if there is no preferred Name in HCM, there should not be any Preferred Name in CRM also.

Right now, even if there is no Preferred Name in HCM, CRM will still have a Name of Type "Preferred".

 

BUSINESS SCENARIOS/EXAMPLES
===========================
1) in HCM, create NameOne = Primary and NameTwo = Preferred on the same day;

2) in CRM, one will see NameOne and NameTwo both as Preferred, with Primary checkbox enabled for NameOne.

3) in HCM, add a new Primary Name, NameThree, which has got as starting date tomorrow => after one day, NameThree becomes the Primary Name

4) in CRM, one can see three Preferred names: NameOne, NameTwo, NameThree, and the Primary checkbox enabled for NameThree.

The issue now is that in CRM we have NameTwo and NameOne that are both Preferred and that have been both created on the same day; so they both appear to be proper Preferred names in CRM. However, in HCM only NameTwo appears as Preferred name. This means that Names data is NOT in sync between HCM and CRM.

 

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms