CS/HCM Integration - EO Publish Multi EMPLID Messages Corrupting Person Data
(Doc ID 1377091.1)
Last updated on JANUARY 06, 2020
Applies to:PeopleSoft Enterprise CS Campus Community - Version 9 to 9 [Release 9]
Information in this document applies to any platform.
The Enterprise Components Batch Publish utility publishes PERSON_BASIC_SYNC messages with multiple EMPLIDs in the payload. This causes the subscription handler used for HCM/CS split integration to fail or corrupt data in the subscribing system.
This condition can be recreated in a number of ways. It has been seen with custom programs publishing email and address changes. In this example, the issue was recreated using the Financial Aid ISIR process. The result is serious corruption of data on the subscribing system.
- Configure the Financial Aid ISIR to update addresses when blank
- Load an ISIR file with existing people in it that have addresses so that the FAPSAR00 program will update the address in Campus Solutions and populate the EO staging tables with the changes.
- Run the EO publish App Engine. In our case we ran the process as a job.
- Review the data and xml published. The data for the first two emplids was seriously corrupted. The name, persona data effdt, and NID data was "merged". The third emplid processed as expected.
Similar corruption can occur to PERS_DATA_EFFDT, EMAIL_ADDRESSES, PERSONAL_PHONE and PERS_NID.
Due to this issue, users cannot depend on accuracy of data when integrating between CS & HR
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