Purpose

This job enables the verification of Unique Student Identifiers (USIs) for multiple students.

This job verifies student USIs that have been recorded by the system but which have not been verified. i.e. This can occur when an administrator enters USI details via ADMW3350 and clicks on the Save & Verify Later button in ADMW3354. It can also occur when a student enters a USI via Student Connect and the system is not configured to run immediate verification

These scenarios set a value of VRFY-BATCH for the transaction type in that student's USI_PERSONAL_DETAIL table.
In verifying the USI, the students’ information is sourced from the USI_PERSONAL_DETAIL table which contains the information from ADMW3354. Up to 500 records in this table with a USI Transaction Type of VRFY-BATCH will be processed when this job is run.

For USIs that have been submitted for verification, but are not verified the USI_PERSONAL_DETAIL record remains with its VRFY-BATCH status and a record for this student is created in the USI_HISTORY_LOG table. (If a USI_HISTORY_LOG record already exists for the student, it is replaced by the new one).
For each verified USI, the USI_PERSONAL_DETAIL record and any error records existing for that student in USI_HISTORY_LOG will be deleted and a USI record is created for the student.

This job will only submit up to 500 USIs for verification at a time. If all records awaiting verification are not included in the batch process, then a message 'Unprocessed Batch Verifications still exist.' is displayed in the run log.

This job is accessed from the main menu.

Parameters Tab

• Run For:
  

Rules/Notes:

Three 'Run For:' options are available for this job:

• Process all: This processes all USI verifications (where a record exists in USI_PERSONAL_DETAIL regardless of whether there are existing errors or not.
• Exclude errors: Only USI verifications that do not have a corresponding error in the USI_HISTORY_LOG are included.
• Errors only: Only USI verifications that have corresponding errors in the USI_HISTORY_LOG are included.

In each case the records are not retrieved in any particular order.

If an instance of this job is running then it must be complete before a another instance of the job can be run.

This job must be scheduled to run, it cannot be run in immediate mode.