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 with the System Transaction Type of 'Verify Batch'.

If the USI web service encounters a technical problem or experiences an outage during a verification request, or if an immediate USI verification request returns an error, a UPD record is saved for the student with a System Transaction Type of VERIFY. These records will also be processed by this job when this job is run with the System Transaction Type of 'Verify'.
The job can process VERIFY, VRFY-BATCH or both (VERIFY, VRFY-BATCH) records.
USI_REQUEST record will be created when job has run for any System Transaction type

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, a USI record is created for the student in the PERSON_USI table. The USI_PERSONAL_DETAIL record and any error records existing for that student in USI_HISTORY_LOG are retained and the S_USI_TRANSACTION_TYPE value is set to PROCESSED.

Records with USI_PERSONAL_DETAIL Transaction Type PROCESSED are not picked up by this job.

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:
• System Transaction Type
  

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.

Three 'System Transaction Type' options are available for this job:

• 'Verify Batch' to process students for which a request to verify a USI has been generated (UPD record with a System Transaction Type of VRFY-BATCH).
• 'Verify' to process records that have been impacted by previous USI request problems(UPD record with a System Transaction Type of VERIFY)
• Leave the System Transaction Type blank to process both types (UPD records with status VRFY-BATCH or VERIFY).

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.