Use

You use requirementcatalogsto map the general and special requirements (program requirements, exam rules and regulations, etc.) which your university uses as a basis for audits (see also Audit Overview ).

The requirement catalogs in Student Lifecycle Management have two functional levels:

In Customizing for Student Lifecycle Management (under Student Lifecycle Management Processes → Audits ® Requirement Catalogs ), you combine (abstract) requirements and requirement patterns to requirement catalogs, and specify which organizational unit is responsible for these catalogs. The requirement patterns provide a rough structure for your (abstract) requirements. You then assign each (abstract) requirement a requirement selection or an evaluation path:

A requirement selection is an implementation of the business add-in requirement selection . It determines the rule containers (object type RC) for the requirements from the academic structure.The rule container represents the instance of a requirement.

Using the evaluation path defined for the requirement selection, the system determines the academic objects which contain the subrequirements. If this academic object is a rule container (object type RC), the system uses this rule container . If the academic object in question is of a different type, the system uses the rule containers assigned to this object.

At the application level, the different organizational units of your university (e.g. faculties) can edit the requirement catalogs they require by assigning them their (concrete) requirements and subrequirements. When they make these assignments, they can create new requirements and subrequirements or use the existing requirements and subrequirements. The concrete requirements are the rule containers (object type RC), and the assigned subrequirements are the rule modules.

You may only assign each requirement ( rule container ) to one requirement catalog.

When you create a requirement profile for a student, the system combines these two functional levels. First, the system determines the requirement pattern for the main requirement catalog defined for the student in the student file. If the student is not assigned a main requirement catalog, the system searches for one using the evaluation path assigned to the audit type in question, and then uses the requirement pattern assigned to this main requirement catalog. Then, by reading the requirements of this requirement pattern, the system derives the rule containers (concrete requirements) and rule modules (subrequirements) for the assigned requirement selections and evaluation paths. Subrequirements can differ in the different requirement catalog versions. The system therefore chooses only those subrequirements which are contained in the main requirement catalog version assigned to the student. If the student is not assigned a main requirement catalog, the system uses the standard version of the main requirement catalog it derived.

In this way, the system assembles the concrete requirements and subrequirements for a student in the requirement profile.

The requirements that a student must satisfy can come from a single requirement catalog. They can also come from different requirement catalogs. For example, a university’s general academic requirements can be specified in one requirement catalog while the special program requirements of each faculty can be outlined in separate requirement catalogs.

You can link the general academic requirements with the top organizational unit of Student Lifecycle Management .

Integration

The audit program uses the:

Functions for performance index calculation and selection methods for index-dependent subrequirements

Functions for conditions and selection methods for index-independent subrequirements

Functions for key figures for auxiliary conditions

Features

When you edit a requirement catalog at the application level, you can assign this requirement catalog (concrete) requirements to which you can then assign subrequirements or auxiliary conditions. You can create new requirement elements or use existing ones. For existing subrequirements and auxiliary conditions, you can use the subrequirement manager .

When you create a subrequirement, you first define whether this subrequirement is index-dependent or index-independent. An index-dependent subrequirement is based on one or more performance indices; an index-independent subrequirement is based on a condition. This subrequirement category determines which elements you can assign to the subrequirement:

Elements of an index-dependent subrequirement:

Performance indices and their target values

The system uses a performance index, for example, to determine the number of modules taken or the number of credits earned.

Filters for selection of academic work objects

The system uses a filter, for example, to determine the academic work objects that belong to a specific category or discipline.You use the category or discipline as a parameter.

Selection method for module proposals

The system uses a selection method to determine the modules a student needs to book in order to satisfy the subrequirement. The system proposes all the modules the student is able to take.

Elements of an index-independent subrequirement:

Conditions (implementation of the business add-in subrequirement condition )

The system uses a condition, for example, to determine if the student has submitted a dissertation or taken academic work in a specific category.

Selection method for module proposals (see above)

When you create filters or conditions, the system proposes the parameters which are assigned to these filters or conditions in Customizing. Each parameter is listed in a separate line.

You must enter a value for the parameters which are not optional. Optional parameters can retain their initial values. If input help is defined for a parameter in Customizing for Student Lifecycle Management , you can use this here.

You implement the performance indices, filters, conditions, and selection methods you need when you define subrequirements in Customizing for Student Lifecycle Management . You must assign the selection methods you want to use for subrequirements to selection method group AUDS so that these are offered as possible entries in the input help.

You can useauxiliaryconditions like subrequirements, to map degree or stage requirements in the system. The system saves the auxiliary condition and the subrequirements in concrete requirements, technically speaking, in the rule container (object type RC) of infotype 1747. If only the auxiliary conditions of a requirement must be fulfilled, and not the implicit condition ("100 % of all subrequirements must be fulfilled for the requirement to be fulfilled“) and auxiliary conditions, you can switch off the implicit condition. If you do not switch it off, all subrequirements and auxiliary conditions must be fulfilled. You use key figures to define auxiliary conditions.

The system offers a version management function for your requirementcatalogs. You can use this version management function, for example, to map the different versions of your academic and exam regulations. When you generate a requirement profile for a student, you can define which catalog version, that is, academic or exam regulation version, is valid for this student. You can combine the versions which you use for each individual requirement catalog to a version set in Customizing.

Activities

To edit concrete requirements, subrequirements and auxiliary conditions for the different requirement catalogs, go to the SAP Easy Access screen and choose Student Lifecycle Management → Academic Structure (Curriculum) → Requirement Catalogs → Edit Requirement Catalog from the SAP Menu .

Choose the desired requirement catalog and audit type, and check the default catalog version.

Select a process part, and if required, a parameter value.

Whether or not you require a parameter value depends on the audit type. The audit type stage audit requires the parameter stage , for instance.

To list the assigned requirements, subrequirements and auxiliary conditions, choose  Select Requirements

You can copy the content of one requirement catalog version to another one by choosing the menu option Edit → Copy Version

You can transfer the responsibility for a specific requirement catalog to a different organizational unit by choosing the menu option Edit → Change Responsibility . However, you cannot define the authorization for the requirement catalog with this assignment. The assignment is used for evaluation purposes only.

You can view and change the requirement assigned to the academic structure and thus determine where it is used in the system by choosing the menu option Edit → Display or Edit Acad. Structure Assgmt .