You can compare the requirements defined in the requirement profile with the academic work taken by the student by means of an audit.
The system can generate requirement profiles and execute audits automatically. It does this when you run the following report programs:
R H I Q A U D I T _ M P _ C P ( A u d i t ( P r o c e s s - D e p e n d e n t ) ) R H I Q A U D I T _ M P _ C S ( A u d i t ( P r o c e s s - I n d e p e n d e n t ) )
If you want to change individual requirement profiles (and subrequirement exceptions) or
correct audits manually, you can use the BSP application PIQ_AUDIT.
You use requirement catalogs to 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
have two functional levels:
In Customizing for
), 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 determines the rule containers (object type RC) for the requirements from the academic
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 (object type RC), the system uses this . If the academic object in question is of a
different type, the system uses the
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
(object type RC), and the assigned subrequirements are the rule modules.
You may only assign each requirement () 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
(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.
© 2009 SAP AG
| bpx.sap.com 157