Top of ADM | Index | Table of Contents | Feedback |
ADMF3250 - Direct Admissions Unit
Purpose |
To allow the recording and maintenance of units forming part of an Admission application. |
|
Subsystem | Admissions | |
Normally Run By | Administration Specialist | |
Anticipated Frequency | As required | |
Structure | Blocks | Admission Course Application Instance |
Admission Course Application Instance Unit | ||
Buttons | Course | |
Person (ADMF3000) | ||
History |
Depending on the policy of the institution, applicants for Admission may be able to apply for specific units within a course. Where this is allowed, the units applied for are recorded in this form. The form is also used to record an application outcome for each unit This form is accessed through form ADMF3000, via the Application button (bottom block), and then through form ADMF3240, via the Unit button (bottom block).
The availability of this form and the validations and processes initiated from it are dependent on the way the Subsystem has been set up at particular institutions. Depending on setup, Offered Units may be automatically pre-enrolled in the Enrolments Subsystem upon the applicant being made an offer. Otherwise the Offered Units will be pre-enrolled by a batch process (ENRJ3100). Features of this Form Information LAMPS are displayed in particular circumstances:
|
The Admission Course Application Instance block contains:
The Admission Course Application Instance Unit block contains:
|
Rules/Notes: The underlaying functionality of the Admission Course Application Instance block has been altered to consider Admission Method Type in all appropriate Admission Process Category Step functionality This
change is introduced as a part of the changes to Admission Process Category
Step.
The following field has been added as a column to ADM_PROCESS_CAT_STEP
table:· ADMISSION_METHOD_TYPE (Text) |
The Admission Course Application Instance block displays the Context Course Application record brought forward from ADMF3240 and is not queryable. Record details of units which form part of the application. The Admission Unit Outcome Status defaults. An application can be recorded without specifying Location Code, Unit Class and Unit Mode details, however, these must be specified prior to the units being offered. Unit Class and Unit Mode must not conflict. Record an Admission Unit Outcome Status mapped to OFFER or REJECTED when these become known. All units must have a status mapped to OFFER or REJECTED before the course outcome status can be changed to OFFER or COND-OFFER. The History button displays the Unit Outcome Status history. |
Rules/Notes: Unit details can only be recorded for Course Applications with an Application Status of PENDING. Unit details can only be recorded if the Subsystem setup included the step UNIT-RESTR. Setup includes the ability to restrict the number of units applied for. Units cannot be added, updated or deleted if the Course Application Outcome Status is OFFER or COND-OFFER. A Unit Version must have its Teaching Period linked to the Academic Period of the Admission Application. The Teaching Period must also be a superior of the application's Admission Period. The Unit Version must not have its Award Course Only check box selected if the Process Type of the application is NON-AWARD. Where the Admission Process Type does not include the step RESEARCH, Research Units should not be recorded for the Course Application. Where a Research Unit is added and the Research Candidature has not been recorded for the Course Application, the unit Outcome Status cannot be set to OFFER. |
Last Modified on 17 February, 2004