Top of ADM | Index | Table of Contents | Feedback | ![]() |
ADMJ3210 - Process PRISMS eCoE file
Purpose |
This job uploads eCOE data from the PRISMS file into Callista. |
|
Subsystem | Admissions | |
Normally Run By | Admission or Enrolments Specialist | |
Anticipated Frequency | As required | |
Structure | Block | Upload PRISMS CoE and Student Data Export File |
Tab | Parameters |
The PRISMS Information system allows an authorised user to log in and request ESOS Student Visa Holder (SVH) data. The data is extracted from the PRISMS Information system in the form of a CSV File. This job uploads data from the CSV file into Callista SMS. The user can upload the CSV file by either:
The students contained in the CSV file are identified by their Person ID. The PRISMS COE Code corresponds to the Enrolment Confirmation Code in the Enrolment Confirmation entity in SMS. The COE Code is a unique identifier. The import process uses this uniqueness to identify existing SMS records and to assist in verifying records. Any discrepancies are logged as errors; for example if an eCOE code is recorded against a different person ID an error is created. The PRISMS file also contains the CRICOS Course Code for each record. This value is used to identify and verify the Student Course Attempt or ACAI record. If an error is encountered the job will log and continue to process the remaining records in the PRISMS file. The Confirmation of Enrolment data is stored in the Enrolment Confirmation entity. The job attempts to import all records in the file. The run log contains high level information, like the number of records processed and number of errors encountered. The detail of the errors is contained in the log tables (S_LOG and S_LOG_ENTRY). If there is no matching COE record in SMS: If it is an existing SMS record for the SCA with the same COE code but the PRISMS record details are different: If it is an existing SMS record and the PRISMS file details (COE Code, Course Code, Start and End dates) match: If an SCA E-COE record exists in Callista but there is no record with the same COE code in the PRISMS file: Refer to the Job Control and Scheduling Subsystem for details on scheduling and running standing requests. |
Upload PRISMS CoE and Student Data Export File block: Parameters Tab
|
Rules/Notes: All COE records not in error will be uploaded from the PRISMS export file to Callista, irrespective of the status of the matching Student Course Attempt / ACAI.
|
The PRISMS extract file contains more than 60 columns of information of which only the fields shown below are used by Callista. All records in the PRISMS file will be uploaded by callista.
CSV Position | Field |
2 | COE Code |
3 | COE Status |
6 | Provider Student ID |
29 | CRICOS Course Code |
51 | Actual Start Date |
52 | Actual End Date |
Last Modified on 25 February, 2011 2:23 PM
History Information
Release Version | Project | Change to Document |
11.0.0.0.0.0 | 1360 - ESOA Compliance 2008 Part 1 | New Help page |