Top of ADM | Index | Table of Contents | Feedback |
ADMJ4500 - Process UAC Offer Files
Purpose |
Allows TAC files to be read in a specified format while supplying UAC student details. |
|
Subsystem | Admissions | |
Normally Run By | Administration Specialist | |
Anticipated Frequency | As required | |
Structure | Block | Process UAC Offer Files Load |
Tabs | Parameters | |
More |
The UAC (University Admissions Centre) Offer Files Upload provides functionality to read UAC files in the specified format and call the appropriate Callista middleware with the UAC student details to create entries in the Admissions and Enrolment System for the potential students. The following process logic during the upload is:
See the TAC Process for Tertiary Admission Centre information. Three files are part of the UAC process. They are:
This job is accessed via the main menu. |
The Process UAC Offer Files Load block contains: Parameters Tab
More Tab
|
Rules/Notes: Validations include:
The following fields: Qualification File, Override Admission Category, Student Status, and Email Address Type are optional fields. All other fields and check boxes are mandatory. When a mandatory field is left null, a warning message is displayed. For example, selecting a different Academic Period that does not have a mapping to the selected Admission Period results in the Admission Period field being invalidated and displaying in red. |
The Offer File, Applicant File and Qualification File fields can have up to 60 characters. This must include file extensions and separators (For example, *.txt).
|
Rules/Notes: The report can be run directly after the upload, or in the near future. It can be run as many times as necessary for each upload. The report lists exceptions only; it does not list every applicant that was uploaded. The total number of records loaded are available from the audit log details. |
|
Rules/Notes: Student Address records are appropriately created with the Address Type defined to the parameter form during the upload of the Applicant File. Students are admitted under the Override Admission Category when it is defined to the parameter form. Student details are uploaded from the Applicant, Offer and Qualification files where the value defined to the REFNUM column matches an existing Students Alternate Person ID record. Student details are uploaded from the Applicant, Offer and Qualification files where the Surname, Given Name initial, Gender and Date Of Birth match an existing Students record. Student details are not uploaded from the Applicant, Offer and Qualification files where the Surname, Given Name initial, Gender and Date Of Birth match multiple existing Student records. Error reported to the S_LOG_ENTRY table. If a Student Course Attempt has a Fee Category defined and/or a Student Status that exists at the current date, then no change is made to the Fee Category value and/or Student Status when the Pre-enrolment process occurs. In these cases, depending on whether the pre-enrolment process occurs via ADMF3240 or ENRJ3100, a warning message is displayed in ADMF3240 or written to the S-LOG-ENTRY for ENRJ3100. |
Last Modified on 8 October, 2014 3:04 PM
History Information
Release Version | Project | Change to Document |
17.1 | 2055 - Gender Diversity | Changed 'Sex' references to 'Gender'. |
12.0.0.3 | 1408 - PC93 Pre-Enrolment Overrides | Added note about updating Fee Category and/or Student Status prior to enrolment process occurring |