Update Process

The job validates batch files that were created by ASSF5340 or uploaded to SMS via a web service, and uploads successfully validated records into the system.

The electronic upload process:

• Validates each record against the configurations established in the Maintain Results Entry Configurations form (ASSF01K0).
• Records successfully validated records as Student Unit Attempt Outcomes, which can be viewed in ASSF53B0.
• Uploads validated records into Callista.
• Produces an Electronic Outcome Upload Report (if specified when running the job) in which it lists records that were successfully uploaded and those that were not.
• Produces an Exception Report that lists all exceptions encountered through validations configured in ASSF01k0.
• Uploads those records that could not be validated and were designated as HOLDING (according to criteria given in ASSF01K0), into the non-enrolled Student Outcome structure for resolution at a later date. Details of these actions are listed in the Exception Report.

Refer to 'Electronic Upload of Results' in Assessments for the Subsystem Specialist for further information on the Electronic Upload process.

Run Details

This job is usually run at the end of each Assessment Period but can be run at any time.

It is recommended that this job be run in batch mode. However, it can be run online, particularly where the report is run with parameters specifying a small data set, such as a specific validated sequence number (batch number).

This job is dependent on batch files having been created by the Validate Electronic Outcome Upload File process (ASSF5340) at a previous time.

The validations for the upload files are configured in the Maintain Results Entry Configuration form (ASSF01K0).

Staff Connect

This existing report makes it possible to call it from the Staff Connect Reporting interface as well as via Callista web forms. Results display appropriately within ASSF53B0 for students who have had results uploaded.

Can be run in Immediate or Job Scheduler mode. Can upload single or multiple units. See Staff Connect Information for further details.

Grades Uploaded from a Web Service

Grades and marks may be uploaded to Callista SMS via the 'resultsLoad' web service. Once the data is uploaded, the ASSJ5341 job is run to create the Student Unit Attempt Outcome records. The user name of the administrator who ran the job is recorded in the STDNT_UNIT_ATMPT_OUTCOME table.

Upload Student Unit Attempt Outcomes block:

Parameters tab

Nominated Period:

• Assessment Calendar
• Teaching Calendar

If an Upload Report is required for specific criteria, then specify the criteria on the next page ('More' tab) of the parameter form.

More tab

Specific Details:

• Location Code
• Unit Mode
• Unit Class
• Unit Code
• Finalised Outcomes check box
• Validated By
• Validated Batch

Rules/Notes:

Note: The % symbol indicates that the parameter is not considered for processing.

The Finalised Outcomes check box allows the user to upload the Student Unit Attempt Outcomes. If Staff Connect functionality is available, this check box is automatically selected.

The Validated By field allows the uploading of batch files validated by a particular user.

The Validated Batch field allows the uploading of a particular batch file.

See ASSJ3500 for descriptions of other parameter fields used in this job.

The Electronic Outcome Upload Report (that is produced if specified in the parameters for the job) lists the following information:

• Students not able to be uploaded by the job. (Person ID, Name, Unit Code, Location, Mode, Class, Mark, Grade.)
• Students successfully uploaded by the job. (Sequence No., Unit Code, Location, Unit Class, Enrolled, Loaded, Validation On, Validated By.)

The report is presented in landscape mode.

An Exceptions Report displays all exceptions encountered through the validation of the batch files. The exceptions reported relate to the validations configured in ASSF01K0. The exceptions are:

• WARNING
  Occurs where the validation for Mark/Grade Invalid in ASSF01K0 is set to 'Warning Only'. Records are loaded into the system and no action is required. When a mark is entered for a Grade that has the 'Record Grade Only' check box selected in ASSF5110, then the grade only is uploaded and not the mark.
• ERROR
  Occurs where the validations are set to 'Don't Load' or 'Abort File' in ASSF01K0. The records are not loaded into the system and must be resolved by an assessments specialist.
• DUPLICATE
  Occurs where a Student Unit Attempt Outcome has already been loaded into the System. The duplicate is not loaded into the system and no action is required.
• HOLDING
  Occurs where a validation is set to 'Holding' within ASSF01K0. For example, Unit Not Enrolled. There are four types of HOLDING exception reported. They are:

• HOLDING
  The record is successfully loaded into the Non-enrolled Student Outcome structure for resolution. Non-enrolled Student Outcomes can be viewed in the Non-Enrolled Student Outcomes Report (ASSR06J0).
• HOLDING DUPLICATE
  The record already exists in the Non-enrolled Student Outcome structure. The duplicate record is not loaded into the system and requires no action.
• HOLDING ERROR
  This exception will be fairly rare. It occurs where a valid Unit Version cannot exist for the record. For example, a Unit Version is made invalid part way through a Teaching Period, Student Outcomes may exist. However, the Unit Code is no longer valid within the System. The record is not loaded and must be resolved by an assessments specialist.
• HOLDING UNWANTED MARK
This occurs where a mark is recorded with a grade which has the 'Record Grade Only' check box selected in ASSF5110. This record is copied into ASSF5333 where it can be resolved.