Subject Requisite Types {SACADO-14}

This option is used to define relationships between subjects in terms of Pre-requisites, Co-requisites, Substitutes, Exposure, Module substitute, Warning and Illegal.  


Refer to the Processing Rules below for explanation of the rules and use of SODs and validations :
Panel Box: Search Result

Field Type
&
Length
Description
Academic Year YYYY The academic year for which this subject is valid.
Subject Code A7 The code of the subject that is being checked during enrolment.  The subject name is displayed.
Relation Type

A1 The following Types can be used:

Pre-requisite:

The Involved Subject must have been passed before the student may register for the Subject. Multiple Pre-requisites are allowed, in which case the student will be expected to comply with all Pre-requisites. 

Co-requisite:
The Involved Subject has to be registered for at the same time as the Subject, or must have been passed already. Multiple Co-requisites are allowed.

Substitute:
The Involved Subject is seen as a replacement for the Subject. 

Exposure:
The student must at least have been previously enrolled for the Involved Subject, before registration is allowed for a subject.
This relationship is similar to a Pre-requisite except that there is no need for the student to have passed the subject, as long as he was registered for it.
 
Module Substitute:
When the calculation program {SSTUD4-23} - "Compute MAIN Curriculum Module Subject Result" is run, the program checks if all the Compulsory Modules are registered or passed and if the Compulsory Module is not found, the check is done on the Module Substitute type.

Warning:
Warning records can be the same as Pre-requisites, but it will override the Pre-requisite check.
Registration for the subject and the involved subject may be done at the same time, as long as it is not for the same block, and the date of the involved subject's block ends before the Subject's block starts. If the block of the subject starts before the end date of the involved subject's block, the registration is not allowed.
This is typically used when institutions register for all blocks at the start of a new academic year.
At the end of the first block, the menu option {SREGC-14} can be used to cancel subjects with failed warnings/pre-requisites.
For {SREGC-14} to identify failed pre-requisites, validation 'W4' has to be changed to N'.
Illegal:
The Involved Subject and the Subject may not be registered for at the same time, i.e. in the same Year.
An Illegal requisite overrules a Warning requisite, so the program always checks for any Illegal requisites first.
If the rule is failed, the following message will be given: "<SUBJECT A> and subject <SUBJECT B> not allowed in the same year." 
Relation Group A2 Relation Groups are only applicable to Pre-requisites and Co-requisites.  Refer to Processing rules for further explanation.
Involved Subject A7 The code of the subject on which the test is done.  The subject name is displayed.
Qualification A6 If a specific combination of exposures, substitutes or pre- and co-requisites is only valid for a specific qualification, the qualification code is entered and the Qualification description is displayed.  A record for the' Subject / Qualification' combination must exist in the Curriculum.  If this field is left blank, the combination is true for all qualifications.

Typical entries could be:
Type Subject Involved Subject Qualification
P    English II          English I
Physics IB   Physics IA
English I   Special English
OR
P English II English I BSc
C Physics IB    Physics IA   BSc
English I   Special English BSc

Please be aware that the qualification code refers to the qualification that the student is registering for.
Minimum Final Mark N3 This is the minimum final mark that the student should obtain, in the involved subject, in order to qualify to register for the subject.  No validations will be done from {SDREGA-1} for 'Exposure' subjects.

Example:


Example of sacad-14b6p1i1



Processing
Rules
 
Pre-requisite, Co-requisite and Exposure Requisite testing can be done in two different ways, Inline or with the Validation report.

iEnabler registration:
  • Dependent on validations WS - "WEB Pre/Co Requisites" and WU (Web Distance Ed)
  • the iEnabler check is always done INLINE and is always FATAL.
Backoffice registration:
  • Dependent on validations PC - "Pre-Co Requisites on Subject Registration"' or DY (Distance Ed), and
  • SODs I1 - "Apply inline Pre-, Co-, Exposure test in the Registration Program?" and
    I2 - "Must the Pre- Co-, Exposure test be (F)atal or a (W)arning in the Registration Program?"
  1. The INLINE check is dependent on SODs I1 and I2:
  • If I1 = Y and 'I2' = F then:
If the Requisite is not met, the student cannot register and a message is given: "Pre-requisite XXXX must be registered prior to that of YYYY"
  • If I1 = Y and I2 = W then:
If the Requisite is not met, the student can register and a warning message is given: "Warning: Pre-requisite XXXX must be registered prior to that of YYYY"
  • If 'I1' set to 'N', then no Inline validations will be done during registration.
  • refer to "Real Time Validations" in the {SREGAR-1} manual, TAB - Subject Information, for further descriptions of I1 and I2.
  1. The VALIDATION report check is done if PC = Yes.
  • The validation report will automatically run after the subjects were committed on the registration program, e.g. {SREGAR-1}, TAB - Subject Information.
The program evaluates the student's subject records after it has been saved and all related processing activities finished (such as raising fees); the records are listed on the Subjects TAB and a requisite problem report is printed. The user then needs to remove the incorrect records from the registered Subjects.
    • In this scenario, the user can override the setting per student BEFORE committing the QUALIFICATION registration, through setting the radio button 'Pre- Co Requisites' = No in the' Validate' block on SREGAR-1 TAB - Qualification Information.
    • The Validation report and Inline check can be used at the same time. Refer to "Real Time Validations" in the {SREGAR-1} manual, TAB - Subject Information, for more detailed information.
Warning: On iEnabler
For a warning requisite to be tested on the iEnabler, the validation W4 - ''Implement Warning Requisite to Override Involved-Subject Requirement" must be set to Yes.
Block codes used during once-off registration has to be setup as Enrolment Type (S)emester in {SCODE2-1}

When a warning requisite record and a similiar pre-requisite record exists:
  • If W4 is set to Yes, the student will be able to register if the block dates are valid.
  • If W4 is set to No, the student will not be able register if he wants to register for both the subject and the involved subject, because the pre-requisite check will be a fatal.
When only a warning requisite record exists:
  • If W4 is set to Yes, the student will be able to register if the block dates are valid.
  • If W4 is set to No, no requisite check will be done and the student will be able to register even if block dates are invalid.
Relation Group:
Involved subjects linked to the same subject code
  • with the same relation group will be seen as 'AND' group of subjects that had to be passed before the student can register for subject or before the subject will be generated as planned subject.
  • with different relation groups will be seen as 'OR' group of subjects where only one of the groups of involved subjects had to be passed before the student can register for the subject or before the subject can be generated as planned subject.
  • All requisites where the relation group is NULL will always apply, this will be in addition to any other requisites where the relation group is not NULL.
Subject Involved Subject Group
A B  
A C X
A D X
A E Y
A F Y

The above table can be translated as follows:

A student may register for subject A if:
  • Passed Subject B  
  • AND
  • (Group X (Passed Subject C AND Passed Subject D))
  • OR
  • (Group Y (Passed Subject E AND Passed Subject F))
Pathways:
Pathways registration allows for separate activation and deactivation for requisite types and separate control for Subjects and Modules:

iEnabler registration:
  • V1 WEB Co-Requisite validation
  • V2 WEB Restricted requisite validation
  • V5 WEB Module Pre-requisite validation
  • V7 WEB Illegal reqisite validation
Distance registration:
  • V3 WDE Co-Requisite validation
  • V4 WDE Restricted requisite validation
  • V6 WDE Module Pre-requisite validation
  • V8 WDE Illegal reqisite validation


See Also:

History of Changes

Date System Version By Whom Job Description
01-Aug-2014 v04.0.0.0 Magda van der Westhuizen T196719 New manual format.
27-Jan-2016 v04.0.0.0 Magda van der Westhuizen t210653 Exposure Subjects
10-Jan-2020 v04.1.0.0 Magda van der Westhuizen t241344 Add new image and rules for the Relation Types and add field Relation Group.