PDL: Why Residency Official Ignores the Data Update Rule Entry when Set to Update/Insert or Safe Update?
(Doc ID 2645863.1)
Last updated on MARCH 31, 2020
Applies to:PeopleSoft Enterprise CS Recruiting and Admissions - Version 9 and later
Information in this document applies to any platform.
Trying to include Residency Official data to PDL but post to Production Tables ignores the Data Update Rule entry.
The data was successfully updated in the staging table PS_SCC_STG_RES_OFF and able to verify from the online Constituent Staging's "Additional Personal Info" page.
When Search/Match/Post is done, Residency data gets successfully loaded if the production table PS_RESIDENCY_OFF only when it does "not" already have a value for the same Empl ID, Career, Institution and Admit Term combination.
If production table already has some residency value for the same Empl ID, Career, Institution and Admit Term combination then the incoming residency data in staging table is completely ignored.
Further investigation showed that there's a delivered code (SCC_SL_TRANSACTION.ACCESSORS.ResidencyOff.OnExecute)that's causing it to bypass the Data Update Rule Entry and simply ignores the staging residency
data if a value already exists in production table for the same Empl ID, Career, Institution and Admit Term combination.
Why Residency update needs to ignore Data Update Rule Entry and rely on the PeopleCode logic to determine whether an "update" needs to be performed or not?
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