My Oracle Support Banner

After Applying CS Bundle #41, CTM Triggers Messages Containing Updated Data to Human Resources (HCM) If Data Update Rule is DO_NOT_UPDATE (Doc ID 2149251.1)

Last updated on APRIL 22, 2019

Applies to:

PeopleSoft Enterprise CS Campus Community - Version 9 to 9.2 [Release 9]
Information in this document applies to any platform.

Symptoms

After applying CS Bundle #41, Transaction Management Process (referred to as CTM) is not adhering to the Data Update Rule setting of DO_NOT_UPDATE and publishes unexpected messages to Human Resources (HR)

This is also occurring when using the Add If Blank rule with actions set to Add if blank for entities, including Names. When posting a record, which should be an Update to an existing ID, one would find that some name data is being messaged, while there was no change on the CS side.

For example:

In CS there is an existing ID <emplid>.  That ID has name types, including the following:

PRI = Xxxxx Smith
PRF = Yyyy Smith

presumably on the HR side the data is the same.

The inbound record from staging, is matched to <emplid>. Names in that record are:

PRI = Xxxxxa Smith
PRF= Yyyyb Smith

A message gets published with the data for both names and then the data is updated in HR from the staging record Names.  In CS the names remain as:
 
PRI = Xxxxx Smith
PRF = Yyyy Smith

If the inbound/staging record had another name type with data which did not exist for <emplid>, then that would be considered 'blank' and that name type data would be added.

This issue impacts various messages containing constituent data, including the following:

Changes

 

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
Changes
Cause
Solution
References


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