Top of CRS | Index | Table of Contents | Feedback |
CRSF2190 - Maintain Course Sub-Unit Relationships
Purpose |
The purpose of this function is to enable the creation and maintenance of Sub-Unit Relationships that are specific to a Course Version. |
|
SubSystem | Course Structure and Planning | |
Sector | Cross-sector | |
Normally Run By | Course/Planning Specialist | |
Anticipated Frequency | At the beginning of the Course Year, or as required. | |
Structure | Blocks | Course Version |
Course Sub Unit Relationship | ||
Button | Sub Unit Relationships (CRSF2250) |
Sub-unit relationships are selected from relationships previously created by the function Maintain Sub-Unit Relationships (CRSF2250), and are restricted to relationships where an open superior unit version sector matches the sector of the course. Course sub unit relationships are created in order to specify overrides of the superior and subordinate units 'Count in Completion', 'Include in VET Government Enrolment File' and 'Count in Load Calc' indicators, where these indicators are required to operate differently within specific courses. In addition, if the sub unit relationship 'Restrict SU Relationship to Crs' indicator is set to 'Y' and the relationship is defined for a specific course or courses, then only students enrolled in the course/s can enrol in the superior and sub units in the relationship. The Superior Count in Completion indicator, Superior Include in VET Government Enrolment File indicator and Superior Load Incurred indicator settings at the course version sub-unit relationship level will default to the settings recorded for superior unit version, but can be overridden. CRSF2190 is accessed through CRSF1210, via the Other Course Detail ... button, then selecting the Sub Unit Relationship arrow (last on list). |
The Course Version block contains:
The Course Sub Unit Relationship block contains:
Spread Table
|
Rules/Notes:
|
To
Create a new Course Sub-Unit Relationship:
|
Rules/Notes: Only able to Insert, Update and Delete Superior or Subordinate Units to a Course Version that has a Status of ACTIVE or PLANNED. Unable to define a Course Sub-Unit Relationship to a Course where the Units have been set to ARCHIVED. A Course Sub-Unit Relationship cannot be inserted if the sub_unit_relationship record it is based on is logically deleted. Course version Sector, the superior and Subordinate Unit versions must have a matching open sector code. The SU Relationship Creation Date field is populated with the Creation Date of the Sub Course Relationship. The SU Relationship Deletion Date field is populated with the Deletion Date of the Sub Course Relationship. If the Restrict SU Relationship to Crs indicator is set, this restricts the Unit to the Course when Enrolling a Student into this Course. When the Include Sup in Crs Completion indicator is set to Y, the Course Sub-Unit Relationship is considered for Course Completion. When the Include Sup in Load Calc indicator is set to Y, the Course Sub-Unit Relationship is used the Course Load. When the Include Sup in VET Govt Enr File indicator (VET Only) indicator is set, the Sub-Units are displayed for the Student Course Attempt on the VET Govt Enrolment File Output. The Superior and Subordinate Unit Tile fields can contain up to 100 characters. If the Course Sub-Unit Relationship (CSUR) 'Sup Incl VET Govt Enrolment File' indicator is set to N, then the CSUR 'Sup Load Incurred' indicator cannot be set to Y. This is a VET-only validation (i.e. only applicable to VET applications or VET courses). |
To Modify a
Course
Sub-Unit Relationship:
|
Rules/Notes: Once in use, a Course Sub-Unit Relationship should not be modified. |
To
Delete a Course
Sub-Unit Relationship:
|
Rules/Notes: A Course Sub-Unit Relationship can be closed preventing any further use by selecting the Closed check box. |
Last modified on 02 November, 2006
History Information
Release Version | Project | Change to Document |
13.1 | 1323 - Online Help consolidation | Added cross-sector label |
12.0.0.3 | n/a | made cross-sector |