When Using a CAF Field Using Calculated Mapping Option with PDL, Process Fails
(Doc ID 2079738.1)
Last updated on MAY 06, 2019
Applies to:PeopleSoft Enterprise CS Recruiting and Admissions - Version 9 and later
Information in this document applies to any platform.
When trying to use a calculated field with a custom app class for an ACT test score file to strip the leading hyphen, the result is that the field is not uploaded. This is attempted when using an institution-specific field conversion for position 91 (Social Security Number/ACT ID) into a new CAF field, stripping the leading hyphen that denotes a non-SSN value. This works ok if a “Direct from File” mapping option is used, but the data is uploaded with a leading hyphen.
The calculated field should strip the hyphen and update Social Security Number/ACT ID correctly.
The issue can be reproduced at will with the following steps:
- Create a common attribute ACT_ID.
- Create an app class ACT_ID under SAD_PDL_PROCESS:File_Parser_Calculated_Fields:ACT. Map the new field.
- Run the file parser process. With this mapping, no value is uploaded.
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