CTM- Work Experience Phone Numbers Blanked Out When Setting the Constituent Status Manually
(Doc ID 2391550.1)
Last updated on FEBRUARY 06, 2019
Applies to:PeopleSoft Enterprise CS Recruiting and Admissions - Version 9 and later
Information in this document applies to any platform.
On : 9 version, Prospect/Admissions Data Load
CTM- Work Experience Phones blanked out when setting the Constituent Status to "Add New ID"
This issue impacts temp ids that contain Work Experience rows with phone number data in Constituent Staging. When data is changed in the Constituent Staging page (such as NID), and then the Constituent Status is updated from “Loaded” or “Suspended” to “Add New ID”, the Work Experience Phone number will be blanked out.
Navigation: Student Admissions- Application Transaction Mgmt – Constituent Staging
(Work Experience is located on the Participation Details page, the SSN is located on the Constituent Details page, and the Constituent Status field is located in the header of all pages in the component.)
Component Name: SCC_CONST_STG
The phone number loaded in the staging table should always be populated in Constituent Staging irrespective of any constituent status.
The issue can be reproduced at will with the following steps:
1- Load an application file using File Parser (Setup SACR – System Administration – Utilities – File Parser- Run File Parser)
2- One of the records that you load in step #1 needs to have Work Experience data loaded to Constituent Staging (Student Admissions – Application Transaction Mgmt – Constituent Staging). You can add the Work Experience data to the file or you can manually add it in staging after the initial load.
The Constituent Status should be “Loaded” at this point.
3- Go to the Constituent Details page and change another data element, like DOB, NID, Name, etc. Save.
4- Lastly, change the Constituent Status at the top of the page to “Add New ID”. Save
5- Go back to the Participation Details page. The Work Experience phone number that you added either by loading through File Parser or manually to the page will have been blanked out.
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