This job requests USIs for students whose details have been recorded but for whom the USIs have not been immediately requested in ADMW3352.
To be included in batch processing the user must click on the Save & Request Later button in ADMW3352. This sets a value of RQST-BATCH for the transaction type and N for the submitted indicator in that student's USI_PERSONAL_DETAIL table.
The students’ information for the USI is sourced from this table which records the details for verification from ADMW3354.

The USI batch request process involves:

a) Initiating a batch request

This assembles up to 500 student USI applications, selected on a first in - first out basis.
To initiate a batch request select one of: 'Process Batch', 'Errors Only' or 'Exclude Errors' in the 'Run For:' field.

To only include Unsubmitted applications select 'Exclude Errors'.

These students all have a USI_PERSONAL_DETAIL record with a status of RQST-BATCH and their inclusion in each type of request is determined by the existence of USI_HISTORY_LOG records for the students (indicating previous requests with errors).
A USI_REQUEST record is created with a receipt number to identify it, for later 'Previous Request' selection.

To only include applications previously submitted but with errors select 'Errors Only', and for both submitted and unsubmitted applications select 'Process Batch'.

This job will only submit up to 500 students to the USI office at a time. If not all students waiting for a USI are submitted (i.e. after processing, there are records with a status of RQST-BATCH and submitted indicator = N), then a message 'Unprocessed Batch Requests still exist.' is displayed in the run log.

b) Retrieving results for an existing request

Once a request job is run and a receipt number has been received, the job must be run again to retrieve the results for that request. To retrieve results from a previous request, select the Previous Release Run For: option and then either select the most recent receipt or from the list of earlier ones.

This will retrieve a response for each of the students sent in the request. The response will contain either a USI for a student, or any errors found while creating a USI for a student.

When a USI is returned for a student, a record is created for that student in the PERSON_USI table and the USI_PERSONAL_DETAIL record and any error records existing for that student in USI_HISTORY_LOG will be deleted.
If the request is not successful, the USI_PERSONAL_DETAIL record remains with the RQST-BATCH status and the submitted indicator is changed back to N. Errors records are created for the student in the USI_HISTORY_LOG table. (Where a USI_HISTORY_LOG record already exists for the student it is replaced by the new one). These students may be included in subsequent requests where the Run For option is 'Errors Only' or 'Process Batch'.

This job is accessed from the main menu.

Parameters Tab

• Run For:
• Previous Receipt
• Latest Receipt check box

Rules/Notes:

A Run For: option must be selected to run this job.

For Run For: options are available for the running of this job:

• Process Batch - The job will request USIs for students that have been nominated for a batch request regardless of whether they have previously been submitted and returned with errors or not.
• Errors Only - The job will retrieve USIs for students that have previously been submitted but which generated errors. i.e. In the US_PERSON_DETAILS table the Transaction Type = 'RQST-BATCH' and the Submitted indicator is not Y and with an existing record in the USI_HISTORY_LOG table for this student.
• Exclude Errors - The job will request USIs for students that have no record in the USI_HISTORY_LOG table for this student.
• Previous Request - This retrieves USIs requested (or errors generated) in a previous run of this job. The Latest Request check box or a Previous Receipt must be selected along with this option.
  

Users can select the Latest Receipt check box to source the latest incomplete request batch record (check box) or else nominate a previous request batch instance.

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

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