Top of ENR

Index

Table of Contents

Feedback

Pre-enrolment

Pre-enrolment is one of the key enrolment management processes within Callista. All offers of Admission to courses must at some stage go through the Pre-enrolment process to transfer data created in the Admissions Subsystem to the Enrolment Subsystem. It is also recommended that all returning students are pre-enrolled a minimum of once per Academic Cycle. Typically this means that all students seeking to enrol should be pre-enrolled once per year. This involves the automatic creation of Student Course Attempts and/or Unit Attempts and/or Unit Set Attempts in the Enrolments Subsystem. This may occur:

• Individually for each new student through the Admissions Subsystem.
• Individually when confirmation of a Student Course Attempt is attempted in ENRF3000, an Admission Application exists but Pre-enrolment has not been performed
• As a batch process for new students through the Admissions Subsystem.
• As a batch process for new Student Course Attempts entered directly in the Enrolments Subsystem.
• As a batch process for returning students (students continuing in an existing Course Attempt).

In each case, Pre-enrolment is subject to constraints.

Index

• New Student Overview
  • Admission Course Application Instance (ACAI) to Student Course Attempt (SCA) - Advanced Standing
• Pre-enrolment of Students Individually Through The Admissions Subsystem
  • A New Application with No Course Attempts in Enrolments
  • An Application With the Course Attempt Already Existing in Enrolments
  • In Both Cases
• Pre-enrolment of a Student Attempt in ENRF3000
• Batch Pre-enrolment of New Students Through the Admissions Subsystem
• Batch Pre-enrolment of New Student Course Attempts Entered Directly in Enrolments Subsystem
• Returning Students Overview
• Batch Pre-enrolments for Returning Students
• Pre-enrolment Constraints
  • Pattern of Study Constraints
  • Determining Which Unit Offering Option to Pre-enrol

New Students Overview

The components of Pre-enrolment differ between students being admitted to a course for the first time, and those gaining Admission or re-Admission to an existing Student Course Attempt.

For new students, the Pre-enrolment process creates in ENRF3000 new Student Course Attempt Enrolment records and may add the following detail:

• A Funding Source record
• A Fee Category record
• A Correspondence Category record
• Values in the nominated completion year and nominated completion period fields
• A link to the Research Candidature record, where one was created as part of the Admission Application
• A Government Cohort Year
• Unconfirmed Student Unit Attempts.

As a part of Pre-enrolment, it is also possible to establish fee contracts between the institution and an individual. More details are given about this in the Student Finance Subsystem. See Individual sponsorship and contracts in Understanding Student Finance, and Contracts/predictive assessment at Admissions in the Specialist Overview.

In ENRF5F00 the process inserts the Enrolment Category record which will be used to process an enrolment and enrolment variations in the forthcoming Academic Period. In certain circumstances Pre-enrolment can be used to override the default enrolment due date.

In addition the new student Pre-enrolment process copies into:

• ENRF3252 any Unit Set details recorded as part of the Course Admission Offer
• ENRF3110 Commonwealth Supported Places if recorded at Admission time.

For new students, the Pre-enrolment process can be configured to operate as an integral component of individual Admission Application processing, as a scheduled batch process or as an immediate (ad-hoc) batch process. If run in batch, an exception report is generated which can be configured to report various levels of detail.

Admission Course Application Instance (ACAI) to Student Course Attempt (SCA) - Advanced Standing

The copying of Advanced Standing details from ACAI to SCA occurs as part of the pre-enrolment process for both online and batch, in all cases where the SCA corresponds to an Admissions offer. Online pre-enrolment occurs in ADMF3240 and ENRF3000 processing, while batch pre-enrolment occurs via the job ENRF3100.

During the pre-enrolment process, the associated ACAI Advanced Standing records (ADVF2000) are copied and recorded in a SCA Advanced Standing context (ADVF4200). 

If the transfer of ACAI Advanced Standing encounters an error, then pre-enrolment of the applicant/student will fail. The error in the pre-enrolment process results in a Student Course Attempt not being created for the student. The error condition is displayed via the standard ADMF3240 / ENRF3000 functionality for the displaying of errors. For the Batch Pre-enrolment Process the existing transfer log includes any reasons for failure resulting from the Advanced Standing transfer. This means that the Administrator can then resolve the issue and has the option of reinitiating the pre-enrolment process.

For more insights on Advanced Standing, see Understanding Advanced Standing (ADVINTR3).

Pre-enrolment of Students Individually Through the Admissions Subsystem

Callista's Pre-enrolment process can be configured to operate as an integral component of individual Admission Application processing.

At the time of recording an Admission Application for a potential student, the application is assigned an Admission Process Category. This determines which steps of the Admission Process are performed on the application. If the Admission Step PRE-ENROL is included in the Admission Process Category assigned to the application, Callista can perform Pre-enrolment for the individual application. If the step PRE-ENROL is not included, a batch process performs Pre-enrolment for those Admission Applications not already processed (see Batch Pre-enrolment of new students through the Admissions Subsystem). The institution determines which of the Pre-enrolment methods is used. (Refer to Defining Admissions Processes for details of Admission Process Categories and their steps)

Individual Pre-enrolment is automatically performed on-line when the Outcome Status recorded against the student's course application in ADMF3240 is changed to either OFFER or COND-OFFER.

A New Application With No Course Attempt in Enrolments

Providing that a Student Course Attempt does not exist in the Enrolments Subsystem, the Pre-enrolment process creates a Student Course Attempt based on the Admissions Offer, and its:

• Funding Source is defaulted from Funding Source Restriction Details recorded in CRSF12A0
• Fee Category is defaulted from Admissions or the default Mapping (Fee Assessment tab in ADMF3240)
• Correspondence Category is defaulted from Admissions or the default Mapping (ADMF3240)
• nominated Completion Year/Period are defaulted from Admissions Expected Completion Year/Period (Completion Period tab in ADMF3240)
• Course Attempt Status is added as unconfirmed, if the Pre-enrolment process is called while making an offer of Admission in ADMF3240
• Course Attempt Status is added/changed to inactive if the Pre-enrolment process is called when an offer of Admission is accepted in ADMF3240.

An Application With the Course Attempt Already Existing in Enrolments

In certain circumstances, an offer of Admission will be made to a Student Course Attempt that already exists in the Enrolments Subsystem. This may arise where a student gains re-Admission following an incomplete prior attempt or where a student is made a new offer of Admission, typically in a subsequent year, after not proceeding with an offer to the same course in a prior period.

Under these circumstances the Pre-enrolment process performs the following actions:

Where a Student Course Attempt already exists in the Enrolments Subsystem and its status indicates that it is no longer active, and:

• Its status is DELETED, then:
• The status is changed to UNCONFIRM
• Location Type, Attendance Mode and Attendance Type, Funding Source, Fee Category and Correspondence Category, nominated completion year and period are set to the attributes of the new offer
• Its status is DISCONTIN and the new offer has not been accepted, then:
• The discontinuation is lifted and the status is changed to INACTIVE
• Location Code, Attendance Mode and Attendance Type, Funding Source, Fee Category and Correspondence Category, nominated completion year and period are set to the attributes of the new offer
• Its status is LAPSED and the new offer has not been accepted, then:
• The lapsed date is cleared and the status is changed to INACTIVE (or ENROLLED if a form due date is not yet reached)
• Location Code, Attendance Mode and Attendance Type, Funding Source, Fee Category and Correspondence Category, nominated completion year and period are set to the attributes of the new offer
• Its status is INACTIVE (i.e. the new offer has already been accepted) or UNCONFIRM, then:
• Location Code, Attendance Mode and Attendance Type, Funding Source, Fee Category and Correspondence Category, nominated completion year and period are set to the attributes of the new offer
• Its status is COMPLETED, ENROLLED or INTERMIT, then:
• No Pre-enrolment action takes place.

In Both Cases

The Pre-enrolment process attempts to register the Student Course Attempt in an Enrolment Period, with a nominated Enrolment Category, creating a Student Course Attempt Enrolment Record. This is seen in ENRF5F00 (accessed via ENRF3000).

The Enrolment Period is determined:

• From the relationship between the Admission Calendar Instance in which the offer is made and the Enrolment Calendar Instance and can be viewed in ENRF5F00. If the relationship has not been set up, the application will not be pre-enrolled. (see Configuring Admission Calendars)

 The Enrolment Category is determined from either:

• The category specified against the Admission Application in ADMF3240, or
• The default mapping between Admission Category and Enrolment Category (as established in ADMF2M20 and recorded in ADMF3240).

This is copied into ENRF5F00.

Where no Enrolment Category can be determined, the application will not be pre-enrolled.

If a Student Course Attempt Enrolment Record already exists for the Course Attempt, with the same Enrolment Period as determined above but a different Enrolment Category, the Enrolment Category is updated.

The Pre-enrolment process attempts to copy Unit Set details recorded for the Admission Application to the Student Course Attempt (in Enrolments), creating a student Unit Set Attempt. Either:

• A new Student Unit Set Attempt is created as unconfirmed or
• If a Student Unit Set Attempt already exists for the Course Attempt and its End Date is in the past (it is ended), a new record is added (subsequent attempt) or
• If a Student Unit Set Attempt already exists for the Course Attempt and is current, no action is taken and the current record remains.

If a Student Status has been specified against the Course Admission Application (under the Fee Assessment tab T-list item in ADMF3240), these details are copied to the Student Course Attempt. If a Student Course Attempt Student Status already exists, it is End Dated and the new Student Status is recorded. Where a Fee Contract is established as a part of Pre-enrolment, the Student Status may determine the rate at which the contract should be set.

If a Research Candidature Record has been created as part of an Admission Application, the Candidature Record is linked to the Student Course Attempt. The proposed commencement date (recorded as part of the Research Candidature) is mapped to the Student Course Attempt Commencement Date, when an offer is accepted.

Where Units have been recorded for the Admission Application and their Outcome Status is OFFERED, they are copied to Enrolments as Unconfirmed Student Unit Attempt records in the pre-enrolled Academic Period.

Where a Pattern of Study exists for a pre-enrolling course, that Pattern of Study may, subject to the listed constraints, be used to create unconfirmed Student Unit Attempts. This Pre-enrolment is performed for the target and future Academic Periods, depending on the 'number of periods' specified to be pre-enrolled for the Pattern of Study (in CRSF1441).

By default, the Pre-enrolment process also establishes an Enrolment Due Date for the Student Course Attempt. The Due Date defaults to the value of the Form Due Date Alias established in the Enrolment Calendar Configuration form, ENRF01F0. This default date can be overridden either by directly inserting a record in the Enrolment Form Due Date field within ENRF5F00, or for a group of students by re-running Pre-enrolment as a pre-cursor batch process to enrolment form production.

Pre-enrolment of a Student Course Attempt in ENRF3000
(where an Admission Application exists but Pre-enrolment has not been performed)

If an attempt is made to confirm an Unconfirmed Student Course Attempt in ENRF3000, the Pre-enrolment process is automatically activated. It checks for the existence of a corresponding Admissions offer in the relevant Admissions Period. If none is found, Pre-enrolment is not performed. If the Admissions Offer exists, Pre-enrolment is performed as described under 'An application with the Course Attempt already existing in Enrolments' in the section Pre-enrolment of students individually through the Admissions Subsystem.

Batch Pre-enrolment of New Students Through the Admissions Subsystem

At the time of recording an Admission Application for a potential student, the application is assigned an Admission Process Category. This determines which steps of the Admission process are performed on the application. If the Admission Step PRE-ENROL is not included in the Admission Process Category assigned to the application, Pre-enrolment is not performed on-line (see 'Pre-enrolment of students individually through the Admissions Subsystem' for on-line Pre-enrolment). In these circumstances a batch Pre-enrolment must be performed on all offers and conditional offers of Admission. (Refer to Defining Admissions Processes for details of Admission process categories and their steps)

Each institution must determine which Pre-enrolment method (on-line or batch) is most suited to each group of students. If an enrolment form is generated as part of the Admission Offer process, batch Pre-enrolment may be more suitable as it:

• Allows the institution to specify a different enrolment form Due Date for each group of students
• Gives the institution the option to pre-enrol ad-hoc groups of units through the batch process Pre-enrolment parameter form

If production of an enrolment form is not part of the Admission Offer process, and applicants go through a two stage Admission and enrolment process (involving acceptance via Admissions followed by a separate enrolment process), then on-line Pre-enrolment at offer is appropriate. The possibility remains of running the batch process again when enrolment forms are created.

Pre-enrolment can be performed for those Admission Applications where the Outcome Status recorded against the student's course application in ADMF3240 has been changed to either OFFER or COND-OFFER.

Batch Pre-enrolment is performed by the batch process ENRJ3100. ENRJ3100 is usually set up as a standing request in the Job Scheduler and would typically run nightly. It can, however, be run both at other times and for subsets of qualifying Admission Applications. For example, a Course Pattern of Study could be approved after some students have been pre-enrolled in the course. ENRJ3100 can be rerun for that course only, in order to apply the Pattern of Study to both the pre-enrolled students and any other new applicants for the course not yet pre-enrolled. The subset of applications/Student Course Attempts affected by the batch process is determined by the selections made in ENRJ3100's Parameter form. Refer to ENRJ3100's documentation for recommendations regarding the use of Parameters.

ENRJ3100 can also be run in immediate mode for subsets of qualifying Admission Applications. Immediate mode Pre-enrolment is particularly appropriate when small groups of offers of Admission, including an enrolment form, are being made. In this case the Course Type, Responsible Org Unit, Person ID Group and Course Code parameters can all be used to refine the set of Student Course Attempts which are processed. Immediate mode Pre-enrolment can also be used to pre-enrol approved Pattern of Study units.

 For nightly processing, it is unlikely that any Parameter other than the current Academic Period will have been specified. In this case, the batch process will only consider applicants and students if:

• No Student Course Attempt is already recorded for their application, or
• The Course Offering of their recorded Course Attempt has a Pattern of Study, but no unit Pre-enrolment has occurred in the target Academic Period.

For each applicant/student record selected, Pre-enrolment is performed as described in Pre-enrolment Individually for each new student through the Admissions Subsystem.

Batch Pre-enrolment for New Student Course Attempts Entered Directly in the Enrolments Subsystem

Students' Course selections may be keyed directly onto the System in Enrolments (this is not a recommended approach), bypassing the Admissions Subsystem. For each, a Student Course Attempt is created with a Status of UNCONFIRM. These Student Course Attempts can be pre-enrolled by the batch process. By selecting the Person Add check box and the Course Add Allowed check box in ENRF0192, students and Student Course Attempts can be keyed directly onto the System in ENRF3000 bypassing the Admissions Subsystem. Whilst this is not a recommended approach, Course Attempts created in this manner are established with a Status of UNCONFIRM. These Student Course Attempts can be pre-enrolled by the batch process ENRJ3100 but are treated on this one occasion as returning students.

ENRJ3100 can be set to run as required but would typically be run nightly for the purpose of enrolling Student Course Attempts. Pre-enrolment takes place when:

• The job ENRJ3100 detects that attributes of the Student Course Attempt match the Parameters specified for the job, and
• The Student Course Attempt has a status of INACTIVE / INTERMIT
• The student is not deceased or Encumbered for the entire Academic Year

The selected Student Course Attempts are processed as for returning students.

Refer to Recommended Parameter Usage documentation for recommendations regarding the use of parameters.

Returning Students Overview

The Pre-enrolment process operates differently for returning students. Here the process is designed to create an ‘eligible to re-enrol’ record. The process:

• Checks to see if the Student’s Enrolled Course Version is on offer and issues a warning where necessary
• Checks if the student’s last Student Status was flagged to expire at the end of the prior Academic Period and issues a warning where appropriate.
• In certain circumstances, creates unconfirmed student Unit Attempts.

In ENRF5F00 the process updates the Enrolment Category record which will be used to process an enrolment and enrolment variations in the forthcoming Academic Period and can be used to override the default Enrolment Due Date.

For returning students, Pre-enrolment only operates as a scheduled batch process or as an immediate (ad hoc) batch process. Again, an Exception Report is generated which can be configured to report various levels of detail.

Batch Pre-enrolment for Returning Students
(students continuing in an existing Course Attempt)

Returning students are those who have already been enrolled for one or more years of a course (for the purpose of discussion here. See the Enrolments Glossary for a full definition of 'returning student'). Pre-enrolment is performed for these students in order to prepare their enrolments records for the upcoming year. If a re-enrolment form needs to be created, Pre-enrolment becomes a mandatory process. Typically this means that all returning students are pre-enrolled once annually.

Returning student Pre-enrolment can only be done using the batch process ENRJ3100. It is recommended that Pre-enrolment is run in tandem for logical groups of students with ENRJ3161, the Enrolment Form extract process. Running these two processes together allows the institution to set an Override Form Due Date Value in the Pre-enrolment parameter form which is appropriate for each group of students who are to receive a re-enrolment form. Following successful Pre-enrolment, this override value is displayed in the Student Course Attempt Administration Details form, ENRF5F00. 

Pre-enrolment takes place when:

• The job ENRJ3100 detects that attributes of the Student Course Attempt match the parameters (see ENRJ3100) specified for the job, and
• The Student Course Attempt has a status of INACTIVE or INTERMIT (and the intermission is due to expire in the upcoming Academic Period)
• The student is not deceased or Encumbered for the entire Academic Year

For each Student Course Attempt selected:

• The Enrolment Category is determined from the previous Pre-Enrolment Period. If no previous Pre-enrolment is found, the Enrolment Category must be specified as a parameter prior to running ENRJ3100, otherwise Pre-enrolment is not performed for that record.
• A Student Course Attempt enrolment record is created using the Enrolment Period nominated in the Parameters for ENRJ3100 and the Enrolment Category determined from the previous step. If a record already exists for the Enrolment Period, the Enrolment Category is updated if it is different to the existing Enrolment Category.
• If the student's last Student Status was flagged to 'expire at end of Academic Period' and ended before the start of the Academic Period being pre-enrolled, a warning is written to the Exceptions Report (ENRR3100)
• The System checks that the student's 'enrolled' Course Version is still being offered within the target Academic Period. If not, a warning is produced but Pre-enrolment is still performed.
• If the Pre-enrol Pattern of Study Units Parameter in ENRJ3100 is set to 'Y', Unit Attempts may be pre-enrolled via a Pattern of Study (subject to Pre-enrolment constraints). For a Pattern of Study, Pre-enrolment is performed for the target and future Academic Periods, depending on the 'number of periods' specified to be pre-enrolled (in CRSF1441).

Pre-enrolment constraints

When pre-enrolling a student, the units to be pre-enrolled could potentially come from:

• Units specified in the Admission Application (for 'new' students through Admissions)
• Units specified as Parameters in the Pre-enrolment batch job, ENRJ3100
• A Pattern of Study attached to the course

Only one of these sources can be used for an individual's Pre-enrolment. The System checks, in the order shown, for the existence of data in each source. It uses the first source found to contain data. For example, if units are specified in the Admission Application, the System attempts to pre-enrol these but no attempt is made to enrol either units specified in the batch job or Pattern of Study units.

Subject to this hierarchy, if there are Unit Attempts already recorded against the subject Course Attempt:

• Units specified in Admissions can still be added, providing they don't already exist
• Units specified in the batch job, ENRJ3100, can still be added, providing they don't already exist
• No attempt is made to pre-enrol Pattern of Study units. Pattern of Study logic will not attempt to merge a Pattern of Study over existing units

A unit will not be pre-enrolled where:

• The student is currently excluded from the unit
• The student has GRANTED or APPROVED advanced standing (of type CREDIT(100%) or PRECLUSION) in the unit
• The Unit Attempt (of any status) already exists in the Academic Period

Pattern of Study Constraints

Subsequent runs of the batch process can be used to apply a Pattern of Study to a student but only where no Unit Attempts are currently recorded.

For example:

• A student is made an offer through Admissions in Course A300 in the 2004 academic year and a Pre-enrolment is performed on-line. There are no units specified against the Admission Application and the Pattern of Study for this course for 2004 is not yet approved. Pre-enrolment does not pre-enrol any units.
• ENRJ3100 (Pre-enrolment batch process) is set up to run once per week. This job has its Pre-Enrol Units Parameter set to 'yes' and the combination of its other Parameters means that it will process course A300 (and possibly others).
• A few weeks later the Pattern of Study for A300 is approved for 2004. When the batch process next runs, the student is selected (as their course has a Pattern of Study and they have no pre-enrolled units in 2004) and units are pre-enrolled according to the pattern.

Pattern of Study Pre-enrolment is not performed where:

• A student has granted or approved 'Unit Level Advanced Standing' in the Course Attempt
• A student has a current 'Unit Requirement' Encumbrance which is not satisfied by the Pattern of Study units recorded for the course
• For a returning student, progress has not been according to the prescribed pattern. (This is determined by the by the existence of passed or incomplete Unit Attempts in Teaching Periods nominated by the pattern)
  Note: This check is overridden where the 'Always Pre-enrol' flag is set for a Pattern of Study.
• The Pattern is not approved (in CRSF1441) for the target Academic Calendar Instance.
  Note: If no approved Calendar Instance is recorded for the Pattern of Study, this means that approval is not required.)

Determining Which Unit Offering Option to Pre-enrol

Units in a Pattern of Study can be specified with only a Unit Code. The specification of a Location and/or a Unit Class is optional. However, the creation of a Student Unit Attempt requires that a specific Unit Offering be nominated. The Pre-enrolment process uses the following method to determine the Unit Offering option to use when Location and/or Class are not specified.

• The process searches for all available Offerings of the unit within the relevant Academic Period which match the Pattern of Study Teaching Calendar Type. Multiple records may be returned if the unit is offered in various Location/Class combinations.
• If the Location Code has been specified in the Pattern of Study, only Offerings at that Location are considered.
• If the Location Code has not been specified, only Offerings at the Student's Course Attempt Location are considered.
• If the Unit Class has been specified, only Offerings in that class are considered.
• If the Unit Class has not been specified, Offerings of any available mode are considered. If the mode of an Offering matches the mode of the Student Course Attempt, that Offering is given preference over others.

This selection process typically reduces the available Unit Offerings to one. If more than one remains, one of the remaining options is selected at random. (Note: The only scenario where this occurs is when the unit is offered in multiple classes within a mode. For example, 'Day' and 'Evening' classes within 'On-campus' mode.)

Last Modified on 18 December, 2007 12:59 PM

History Information