My Oracle Support Banner

Populating Campus ID For Existing Person Does Not Trigger PERSON_BASIC_SYNC (Doc ID 2237094.1)

Last updated on AUGUST 03, 2018

Applies to:

PeopleSoft Enterprise CS Campus Community - Version 9 and later
Information in this document applies to any platform.

Symptoms

ACTUAL BEHAVIOR
-----------------------
When a user populates campus id for an existing person and saves, it does not trigger the PERSON_BASIC_SYNC causing discrepancy between CS and HR.
If after that, a user updates a phone number for the same person, it creates the PERSON_BASIC_SYNC, but the PERSON_SA data is not present in the XML MsgData section.

Owner/Subscriber split CS to HR using PERSON_BASIC_SYNC_VERSON_4, all setup and transformation has been reviewed and all looks correct.

EXPECTED BEHAVIOR
--------------------------
When Campus ID is updated, it will be within the Publication Message for PERSON_BASIC_SYNC.

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


1. Add Campus ID and save the page.

2. Review SERVICE OPERATION MONITOR for the PERSON_BASIC_SYNC message.

3. Notice that PERSON_SA is not in XML.



BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, possible discrepancies between CS and HCM. Need to use IIU for resolving.

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Cause
Solution


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