Hierarchy

⤷

⤷

Basic Data
Data Element | PIQPERIDUP |
Short Description | Higher-Level Academic Session |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | PIQPERID | |
Data Type | NUMC | Character string with only digits |
Length | 3 | |
Decimal Places | 0 | |
Output Length | 3 | |
Value Table | T7PIQPERIOD |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | UPPER_SESSION | |
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | HL Session |
Medium | 15 | HL Session |
Long | 20 | Higher-Level Session |
Heading | 10 | HL Session |
Documentation
Use
You can arrange academic sessions in hierarchical order. A higher-level session in the hierarchy can have any number of lower-level sessions. A lower-level academic session may only be assigned to one higher-level session. You can set up as many hierarchy levels as you require.
The system uses the session hierarchy when it performs various checks. For example, if a student is registered for a program which belongs to a higher-level session, (s)he can book the modules offered in the assigned lower-level sessions.
The system also uses the session hierarchy when it filters academic work. For example, you want to display the academic work objects of an academic session in the student file overview. The system will display the academic work objects which are directly assigned to this session as well as the ones assigned to its lower-level sessions.
Example
You want to split the summer session into two lower-level sessions.
- Summer session part 1
- Summer session part 2
You then assign these two lower-level sessions to the summer session.
History
Last changed by/on | SAP | 20050224 |
SAP Release Created in | 472 |