UCAS: Entry Point Mapping Behaviour (Doc ID 2072064.1)

Last updated on JANUARY 30, 2017

Applies to:

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

Goal

UCAS: Entry Point Mapping Behaviour  

Set Up SACR > Product Related > Recruiting and Admissions > UCAS > Mappings > Entry Point

The UCAS Entry Point to CS Academic Level mapping is an optional piece of configuration, and when an application is imported with an entry point that is not mapped, the Academic Level on the ADM_APPL_DATA record is left blank (as it is not a required field), and the Year of Program (for programme enrolment) is set to 00 (Not Set).

When a ivStarC record is imported where the Entry Point has changed, the behaviour above is the same (as expected).

However, when a UCAS Transaction is generated where a change in Entry Point is being sent as part of the decision, the process does not update the CS Application (including Admit Term, Program, Plan etc) if no Entry Point mapping exists. This is inconsistent with the Entry Point processing before this. The process should simply not touch the Academic Level if no mapping is found (as per ivStarC processing) rather than not process the application at all.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms