UCAS Processing: Hard-Coding on Pushbutton Causing Issue When Importing Applicant Transaction Data.
(Doc ID 2949371.1)
Last updated on JANUARY 26, 2024
Applies to:
PeopleSoft Enterprise CS Recruiting and Admissions - Version 9.2 and laterInformation in this document applies to any platform.
Symptoms
UCAS: hard-coding on pushbutton causing issue when importing applicant data. The update button uses SCC_TRANSAC_DATA.SCC_SL_DERIVED.SCC_UPDATE_PUSH_BTN.FieldChange
This is hard coded with a CTM transaction of UCAS: &const.setUpdateRuleByTransName("UCAS");
But for applications from DFE, it need to use transaction type of APPLY as that has a different data rule assigned. Peoplebooks say not to hard code it.
Navigation: Student Admissions > UCAS Processing > Import Applicants > Transaction Data
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 |