My Oracle Support Banner

UCAS DfE Apply Applications Import Long Name Process Leaves LAST_NAME Blank in the Constituent Staging Names Record With Staging Status Error '18180,117 - Last Name is required.' When Name is > 30 Characters with No Spaces (Doc ID 2864139.1)

Last updated on MAY 23, 2022

Applies to:

PeopleSoft Enterprise CS Recruiting and Admissions - Version 9 and later
Information in this document applies to any platform.

Symptoms

When running the DfE Apply Applications Import process, if 30 or more characters are imported for Surname without any spaces (e.g. Long-Name-Long-Name-Long-Names) the LAST_NAME is left blank in the constituent staging names record and the Staging Status is set to Error with Error Message '18180,117 - Last Name is required.' No errors are reported in the log for Import Applicant Data.

For surname values over 30 characters that include at least one space, the processing is working correctly to load the full name to StarN staging and truncate the LAST_NAME value in the constituent staging names record to 30 characters, and the long names record is then added as part of the import applicant data processing. 

The issue can be reproduced with the following steps:

  1. On Set Up SACR > Product Related > Recruiting and Admissions > UCAS > UCAS Configuration > UCAS Configuration, make sure the 'Use Apply' box is checked in the Apply Setup section.
  2. Navigate to Student Admissions > UCAS Processing > Import Applicants > Import Applicant Data and run the process.
  3. Navigate to Student Admissions > UCAS Processing > UCAS Applications > UCAS Applicant Summary, and choose student with 30 or more characters in Surname without any spaces.
  4. Note status and error message displayed on the page.

Changes

The issue occurs after applying the phase 4 updates for Apply Applications Import, which delivered additional functionality to create long names records where the incoming surname value exceeds the maximum 30 characters allowed for Last Name. This functionality was delivered in the following Bugs:

Release 9.2: <Bug 32155440>, in CS 9.2 PUM Image 22. 

Release 9.0: <Bug 32150772>, in CS 9.0 Bundle 62

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


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