CTM Erroneously Allows No Preferred Phone When Updating An Existing EMPLID After Applying Bundle 41

(Doc ID 2180505.1)

Last updated on FEBRUARY 23, 2017

Applies to:

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

Symptoms

ACTUAL BEHAVIOR
-----------------------------------
The transaction management process allows no preferred phone when updating an existing ID after applying Bundle 41.

EXPECTED BEHAVIOR
----------------------------------------
The transaction management process does not unselect the preferred flag of the existing phone type.

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

1. Set up File Parser Mapping definition with two Phone Types that are processed into staging:
  a. CELL - preferred flag = N
  b. HOME - preferred flag = Y
2. Find an existing ID that has a CELL phone number set to preferred.
3. Load that existing ID with only a CELL phone in the file (the mapping will set the preferred flag to N).
4. The CELL phone in CS PERSON_PHONE table will be set to preferred = N, even though there is no other phone type set to preferred.
5. The CS Publication is consistent by setting Cell phone preferred flag to N.
6. The HCM Publication will error out: “One phone number must be checked as preferred” .



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