Purpose

To maintain the hierarchical Relationship structure which may exist between Units

On the right hand side of the Unit Code fields of both the Superior Unit Versions and Subordinate Unit Versions fields are zoom buttons , one corresponding to each record displayed in these fields. These buttons permit the adjacent record to be dropped or elevated into the context block allowing its Superior and Subordinate Unit Versions to be displayed.

Superior Unit Versions

The Superior Unit Versions block displays all Unit Versions which have been defined as Superiors of the Unit Version displayed in the context block. New Superior Unit Versions can be added in this block.

If, in the example below, a module can also be taken as part of another unit, the Unit Version representing the module can be displayed as the context record and the other unit can be recorded as a Superior.

Unit Version

The Unit Version block (context block) displays the Unit Version for which Superior Unit Versions and Subordinate Unit Versions are displayed, added or deleted. On entering the Maintain Sub-Unit Relationships form, the Unit Version block will display the context record which was the most recently selected Unit Version in the Maintain Basic Unit Details form. Superior and Subordinate Unit Versions will be displayed for this context Unit Version.

This function allows for many layers of Superior/Subordinate relationships. It also permits a sub-unit to have more than one Superior unit and vice versa.

For example, some institutions have adopted a concept where the completion of a unit is dependent on the successful completion of two or more modules. ie. The unit has been subdivided into modules. Sub-unit relationships can now be used to represent this scenario, with the unit being the Superior and modules now becoming Subordinate units of the Superior.

Subordinate Unit Versions

The Subordinate Unit Versions block displays all Unit Versions which have been defined as Subordinates of the Unit Version displayed in the context block. New Subordinate Unit Versions can be added in this block.

Using a similar scenario as the examples above, if a unit is split into two modules, the unit can be displayed as the context record and the two modules can be recorded as Subordinate units.

This form can be accessed through Other Unit Details button in CRSF2210, then the Sub-Unit Relationship arrow from the overlay.

The Superior Unit Versions block contains:

• Unit Code
• Version Number
• Sector

Spread Table

• Title
• Unit Status
• Creation Date
• Deletion Date
• Restrict SU Relationship to CRS
• Award CP on Sub Unit Completion (not shown in VET)

The Unit Version block contains:

• Include Detailed Relationships check box
• Unit Code
• Version Number
• Sector
• Unit Status
• Title

The Subordinate Unit Versions block contains:

• Unit Code
• Version Number
• Sector

Spread Table

• Title
• Unit Status
• Creation Date
• Deletion Date
• Restrict SU Relationship to CRS
• Award CP on Sub Unit Completion (not shown in VET)

Rules/Notes:

To create a new Superior Unit Version to the context Unit Version using the Maintain Sub-Unit Relationships form:

• Navigate to the Superior Unit Versions block
• Enter insert mode or select a blank record
• Select the required Superior Unit Version from the list of values (or key a valid Unit Code) in the Unit Code field
• Save

Rules/Notes:

Superior Unit Versions can only be created if their Superior Unit check boxes are set to yes (i.e. selected) on the Maintain Basic Unit Details form.

A new relationship cannot be created if a relationship already exists between the Unit Versions.

A PLANNED Unit Version cannot be the Superior of an ACTIVE Unit Version.

To delete a Superior Unit Version relationship using the Maintain Sub-Unit Relationships form:

• Ensure that the correct Unit Version is displayed in the context block
• Select the desired Superior Unit Version
• Delete record. (The record is logically rather than physically deleted, permitting later inquiry on former relationships. The logical delete date is inserted by the System.)
• Save

Rules/Notes:

To inquire on the relationships of a Unit Version other than that initially displayed:

• Select the displayed Unit Version in the Unit Version block
• Enter query mode
• Enter query details in the appropriate field(s)
• Execute the query
• Where more than one Unit Version is returned, scroll through the records until the correct record is located or
• Redefine the query details and repeat this process

Rules/Notes:

It is possible to inquire on deleted relationships by selecting the Include Deleted Relationships check box. Deleted relationships can be identified by the existence of a Deletion Date.

• Navigate to the Subordinate Unit Versions block
• Enter insert mode or select a blank record
• Select the required Subordinate Unit Version from the list of values (or key a valid Unit Code) in the Unit Code field
• Save

Subordinate Unit Versions can only be created if their Subordinate Unit check boxes are set to yes (i.e. selected) on the Maintain Basic Unit Details form.

A new relationship cannot be created if a relationship already exists between the Unit Versions.

An ACTIVE Unit Version cannot be the Subordinate of a planned Unit Version.

To delete a Subordinate Unit Version relationship using the Maintain Sub-Unit Relationships form:

• Ensure that the correct Unit Version is displayed in the context block
• Select the desired Subordinate Unit Version
• Delete record. (The record is logically rather than physically deleted, permitting later inquiry on former relationships. The logical delete date is inserted by the System.)
• Save

Rules/Notes: