Top of CRS | Index | Table of Contents | Feedback | ![]() |
CRSF2210 - Maintain Basic Unit Details
Purpose |
To enable the creation and maintenance of institution defined Unit Versions and details relating to the Unit Versions |
|
SubSystem | Course Structure and Planning | VET Sector Information |
Normally Run By | Course/Planning Specialist | |
Anticipated Frequency | Before the commencement of the Course Year, or as required | |
Structure | Block | Unit Version |
Tabs | Credit Points | |
Sub Unit Controls | ||
More | ||
Buttons | Sector (overlay) | |
Other Unit Details (overlay) | ||
Unit Offering (CRSF2310) | ||
Unit Version Notes (CRSF2280) |
Unit Version This form is used to record and maintain details of the Units of Study offered by the institution. Each Unit is defined by numerous attributes. A definition of each attribute is included in the Subsystem Glossary section of this manual. Versions of Units are created when changes to a Unit are considered, by the institution, to be minor. The institution will determine that at some point, the changes to a Unit are of sufficient importance to warrant the creation of a new Unit or a new version of a Unit. Unit Versions are therefore a history of changes made to the attributes of a Unit. Students enrol in particular Unit Versions. For example, for a new Unit, current details are entered. These details may be changed. Institution policy may determine that a change has altered the definition of the Unit to the extent that newly enrolling students should enrol in a different Version. This will permit the precise identification of the Unit Version which a student has completed. Institution policy will also determine if changes to a Unit have been of such significance as to warrant the creation of a new Unit. |
The Unit Version block contains:
Tabs
Buttons |
Rule/Notes: The content of selectable items in each Tab block is dependant on what is selected in the Unit Version block. The fields in the Tab blocks (left column), are listed before any field in the Unit Version block is selected. Once fields are selected in the Unit Version block, some fields will not be available or visible. |
To
create a new Unit using the Maintain Basic Unit Details form:
|
Rules/Notes: A new Unit is automatically assigned the version number 1. see 'To create a new Version of an existing Unit using the Maintain Basic Unit Details form' for creation of a new Version of an existing Unit. When creating a new Unit, the Unit Status must be set to one with a corresponding System Unit Status of 'PLANNED'. Changing the Unit status to one with a corresponding System Unit Status of 'ACTIVE' is specifically described in To modify a Unit Version using the Maintain Basic Unit Details form (below). The following rules apply to Unit Status changes:
There can only be one Version of a Unit with a Status of ACTIVE and an unset Expiry Date. You cannot alter the details of a Unit Version once it has been made INACTIVE, with the exception of changing it back to ACTIVE. Some data will preclude this status change. A quality check is performed when the status change is attempted. The Unit Version will only be active if the quality check is passed, otherwise a new version will need to be created. Advisory messages are displayed. Some check box fields are selected by default on creation of a new record. All default values should be checked for correctness. An End Date can only be specified for Unit Versions where the Unit Status has been changed to one with a System Unit Status of INACTIVE. For example, an End Date cannot be entered when creating a new Unit. Similarly, the Unit Status can only be changed to INACTIVE when an End Date has been entered. i.e. Both events must happen in a single update transaction. The Title, Short Title and Abbreviation fields should contain carefully considered data as this data may be used to generate Handbook entries, etc. CLOSED Organisational Units, Unit Statuses, Unit Levels and Unit Internal Course Levels cannot be used to define a Unit. Courses containing these closed values cannot be activated. The End Date for a Unit must be >= the Expiry Date if an Expiry Date is set. Sub Unit relationship constraints:
If the Override Credit Point (CP) check box is not selected, the Override CP Increment, Maximum and Minimum fields must be blank. If the Override CP check box is selected, then values can be entered for some or all of Override CP Increment, Maximum and Minimum. If both CP Maximum and Minimum contain values then CP maximum must be greater than or equal to CP Minimum. Min/Max CP values must be in accord with CP Increment value (if it exists). For example, if Enrolled CP = 4 and CP Increment = 2, then CP Min value may be 2, but cannot be 3, CP Max value may be 6, but cannot be 5. CP Min <= Enrolled CP <= CP Max. The Supp Exam check box in this form overrides the Supp Exams Permitted check box in the Maintain Basic Course Details form (CRSF1210). die. The Unit Supplementary Exam check box overrides the Course Supp Exam check box. Selecting the Override Credit Points check box also allows the override of EFTSL for individual Student Unit Attempts in the Record Enrolments form (ENRF3000). Selecting the Override Title check box allows for the overriding of the Unit Title for an individual Student Unit Attempt in the Record Enrolments form (ENRF3000). Selecting the Include Superior Unit in Course Completion Evaluation check box, allows the user to record whether the Unit Version is counted when course completion is evaluated and the Unit is enrolled as a superior Unit in a sub-Unit relationship. Setting the check box (ticked) allows the Unit to be included in Course Completion evaluations. Otherwise, the Subordinate Units are included in Course Completion evaluations. The check box setting can be overridden at the Course Sub-Unit Relationship level. Selecting the Include Superior Unit in Load Calculation check box, allows the user to specify whether the Unit is included in student load calculations when it is enrolled as a Superior in a sub-Unit relationship. Load calculations are used for fee assessment and the derivation of Attendance Type. Setting the check box (ticked) results in load being derived from the Superior Unit. Otherwise, load is derived from the Subordinate Units. The check box setting can be overridden at the Course Sub-Unit Relationship level. Work Experience In Industry Codes are maintained in STAF1134 (Maintain Work Experience In Industry Code). |
To create a new Version of an existing Unit using the Maintain Basic Unit Details form:
|
Rules/Notes: When creating a new Version of a Unit, any attached assessment items will be carried over also. |
To
create a new Unit based on an existing Unit using the Maintain Basic Unit
Details form:
|
Rules/Notes: When creating a new Unit based on an existing Unit, any attached assessment items will be carried over also. |
To
modify a Unit Version using the Maintain Basic Unit Details form:
|
Rules/Notes: It is unlikely that a Unit Version will be modified other than to correct data which has been entered incorrectly. Changes to Unit Versions in which students are, or have been, enrolled will usually result in the creation of a new version of the Unit. For changes to other Unit details see the instructions for their particular maintenance forms. |
To delete a Unit Version using the Maintain Basic Unit Details form:
|
Rules/Notes: Unit Versions cannot be deleted if they have been used elsewhere in the system. For example, if students have been enrolled in the Unit Version. It is unlikely that a Unit Version will be deleted other than to remove data which has been entered incorrectly |
Last modified on 02 November, 2006
History Information
Release Version | Project | Change to Document |
9.0.0.0.0.0 | 1187 - Update Help for VET | Clean up to represent only HE |
8.0.0.0.0.0 | 0976 - DEST Load EFTSU for EFTSL | Replace EFTSU with EFTSL |
7.1.0.0.0.0 | 0954 - Fees COPAI Part 2 | VET info added |