SCHJ5000 - Match Scholarship Applicant to Person

Purpose

This job matches Scholarship Applicants to existing Callista students

SubSystem

Scholarships

Normally Run By Scholarship Specialist
Anticipated Frequency Regularly or as required
Structure  Block Match Scholarship Applicant to Person
Tab Parameters

  

To link a scholarship applicant, as recorded in SCHF1010, with a person_ID as recorded in ADMF1213, the applicant number is recorded as an alternate ID of type 'APPLICANT_ID for the person

The job performs that matching process and where a PERFECT match is determined, then the alternate person ID is created for the person.

If more than one perfect matchfor a scholarship applciant is found, then the matching person ID's are identified as possible (POTENTIAL) matches and flagged for closer examination by administrators. these multiple POTENTIAL matches can be viewed in ADMF5600 which is accesses from SCHF1010.

If just a partial match is obtained then the person ID is also flagged as a POTENTIAL match and flagged for further checking. If no perfect or potential matches are found, this will be indicated in the extract. The Person ID will need to be created via normal admissions/enrolments

The default matching criteria are:

  • Title
  • Given Names
  • Surname
  • Date of birth
  • TAC ID

These matching criteria can be altered by making changes to the open source code that performs the matching process

This job is accessed from the main menu.

 

The Bulk Scholarship Verification block contains:

Parameters Tab:

  • Creation Date
  • Applicant ID
  • Submission Start Date
  • Submission End Date
  • Create CSV Extract check box

Rules/Notes:

A previous extract can be regenerated by selecting a previous job run instance using the Creation Date LOV.

Applicant ID and Submission Start Date and End Date parameters can be used to limit the range of Applicant ID's to undergo the matching process.

Either Creation Date or one of Applicant ID or Submission Date Range must be populated, but not both.

If one date for the Submission Date range is populated then the other one must be too.

Submission Start Date must be earlier than or equal to Submission End Date.

If the user desires a CSV file to be generated, so as to display the results of the matching process in a spreadsheet, then the Create CSV Extract check box should be selected.

If an Applicant ID is entered as a parameter and that Applicant doesn't have a system Scholarship Status = PROCESSING and a system Scholarship Outcome Status = OFFERED, then a message, saying that the Applicant ID is already matched to Person or has no offered scholarships, is displayed in the csv file.

To find a match for a particular Scholarship Applicant:

  • Go to SCHJ5000
  • Enter the Applicant ID
  • Run the job
  • Examine the extract file generated

Rules/Notes:

A previous extract can be retrieved by selecting a previous job run instance using the Creation Date LOV.

To find a match for a umber of Scholarship Applicants created over a period of time:

  • Go to SCHJ5000
  • Enter the start date and end date values to cover the range o scholarship applications required
  • Select the create CSV extract to generate a more user-friendly output
  • Run the job
  • Examine the CSV file using MIcrosoft Excel (or equivalent)

Rules/Notes:

 

 

The S_EXTRACT_RECORD of type 'AP-MATCH', generated by this job, has the following table structure:

Field

Comment

S_EXTRACT_TYPE

AP-MATCH

CREATION_DT

Date when this job run occurred

SEQUENCE_NUMBER

Unique identifier that helps in identifying individual transactions

KEY1 Holds Applicant ID - Always populated
KEY2 Holds Matching StatusCan be ‘PERFECT’, ‘POTENTIAL’ and NULL
KEY3 Holds Person ID of the student identified as a perfect match for the applicant.
TEXT Holds a message indicating a general status of the matching.

 

 

Last modified on 28 May, 2008 4:05 PM

History Information

Release Version Project Change to Document
11.0.0.0.0.0 1437 - Scholarships New Job