Purpose

To process a CART Request file and to generate a CART response.

SubSystem

Statistics

The administrator is able to process a CART request file and to generate a CART response. 

The function provides the administrator with the ability to browse their client machine to identify and load the CART request file.  The request file will need to be in an unzipped format.

The administrator is responsible for the unzipping of the CART Request and the zipping of the CART Response.

This job:

• Validates and logs any exceptions from the request header
• Matches the requested Student IDs to SMS Person IDs
• Loads the request for processing
• Determines the Response values for each CART Student Request:
  • Determines EFTSL Total
  • Withdrawn Units and
  • Course Details and
  • Extra Details (Mobile and Email Address).
• Creates and Returns entities to the CART Response according to defined SMS Job Output  and
• Clears the CART Entities ready for the next file.

STAJ0035 creates an exception file in csv format and documents any issues that may arise in the processing of the request file.  This file may be optionally produced depending on the job output definition for the job.

This job is accessed from the main menu.

The Process CART Request and Create CART Response block contains:

Tab

Parameters

• CART Request File
• Browse button

Rules/Notes:

The CART request parameter is not a parameter passed to the job. The contents of the file are loaded into the request_job_input_blob and accessed by the job when being executed.

The Browse button opens a file dialogue box, allowing the user to navigate to, and select a file to process. This file is loaded into the request_job_input_blob  table either when the schedule asap button on the toolbar is pressed (when called from the menu) or the save button (when called from JBSF5210).

Validations include:

• A Timestamp must exist
• The Timestamp in the header must be in the format CCYYMMDDHHMMSS.
• System Code must be CART.
• The Institution ABN in the request must be the same as the ABN in the configuration table
• The User ID in the request must be the same as the User ID in the configuration table