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:

Symptoms

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.

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

1. Create a common attribute ACT_ID. 
2. Create an app class ACT_ID under SAD_PDL_PROCESS:File_Parser_Calculated_Fields:ACT. Map the new field.
3. Run the file parser process. With this mapping, no value is uploaded.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.