Rules
The rules in
Student Lifecycle Management
are used for formal checks, period and deadline checks, and checks based on the academic structure.
Each application area has its own set of rules:
Prerequisites/Conditions: These rules are checked when a student applies for admission and registration, selects academic specializations, and books modules.
Progression monitoring: These rules determine whether the academic performance of a student meets the requirements set by the university.
Applications, such as module booking, have specific callup points at which the system evaluates the predefined rules (for example, the
module booking (single)
callup point
is processed when a student books a module).
The following table provides an overview of the callup points used in
Student Lifecycle Management
functions. This table lists only the generic term for a group of related callup points; for example
module booking
refers to all callup points related to module booking. The number of callup points within a particular group is given in brackets next to the generic term. For example, the generic term
module booking (3)
comprises the three callup points module booking (general), module booking (set), and module booking (single).
Function |
Generic Term with (Number) of Callup Points |
Type of Callup Point |
|---|---|---|
Admission |
Admission (2) |
Academic and non-academic (see explanation below) |
Registration |
Registration (4) |
Academic and non-academic |
Re-registration |
Re-registration (4) |
Academic and non-academic |
Leave of absence |
Leave of absence (4) |
Academic and non-academic |
De-registration |
De-registration (2) |
Only non-academic |
Academic specialization booking |
Academic specialization booking (3) |
Academic |
Module booking |
Module booking (3) |
Academic |
Progression |
Progression (1) |
Academic |
Callup points are distinguished by their
type
, which can be
academic and/or non-academic:
Academic callup points are used to link rule containers , which are the central objects within the rules, with objects of the academic structure, such as programs or modules . The rule containers are then valid for the object of the academic structure to which they are assigned, and for all subordinate objects linked to this object.
In the case of
non-academic callup points
, the system makes no distinction between the different objects of the academic structure.Instead, it evaluates all the rule containers assigned to these non-academic callup points.You assign rule containers to non-academic callup points in Customizing for
Student Lifecycle Management
in the section
Rules
Rule Containers
Assign Rule Containers to Callup Points
.The rules are based on a three-level concept.At the top level are the rule containers.Rule containers are objects that are either linked with other objects of the academic structure or are assigned directly to specific
Student Lifecycle Management
applications in Customizing.The rule containers contain rule modules.Rule modules contain one or more rule elements, and are modular and reusable.The rule elements are validations or substitutions that belong to the application
Validations, Substitutions, Rules (VSR)
.
Note
For more information about rules, see
Rules
in the
Student Lifecycle Management
Implementation Guide.We recommend you also read the documentation in the SAP Library in the section
Accounting
Financial Accounting
Special Purpose Ledger
Validations, Substitutions, and Rules
.
Examples
One rule container can contain the checks that apply for admission of domestic students. Another can contain the checks for admission of international students.
A rule module can contain the checks which, for example, determine whether a student fulfils the Mathematics prerequisites.
A single rule element then checks whether the student has passed the Mathematics entrance test.
See also: