Automatic Generation of Requirement Profiles

You can create requirement profiles automatically with the following report programs:

• RHIQAUDIT_MP_CP (Audit (Process-Dependent))

• RHIQAUDIT_MP_CS (Audit (Process-Independent))

Manual Creation of Requirement Profiles

You can use the BSP application PIQ_AUDIT to edit requirement profiles individually. The BSP application enables you to make manual changes, for example, if a result is not fulfilled.

Start the BSP application PIQ_AUDIT with the required audit type and view, and then proceed as follows to create a profile:

Choose a student.

If you use processes like an assessment process, you first have to choose a process part.

The system displays the main catalog and version for which it generated the requirement profile.

Choose a requirement profile type.

Generate a requirement profile for the main requirement catalog.

The system determines the requirement pattern and the associated (abstract) requirements from the main requirementcatalogand the catalog version. Using a requirement selection or the evaluation path you defined in Customizing for Student Lifecycle Management , the system derives the concrete requirements and, from the assigned catalog version, the concrete subrequirements and auxiliary conditions. Based on this information, the system generates an initial requirement profile and then displays it.

You can change this initial requirement profile by

Creating additional subrequirements and auxiliary conditions

Defining that a given default subrequirement does not have to be fulfilled

In this case, you delete the subrequirement from the profile.

Creating an exception reason and a note

Specifying exceptions for subrequirements and auxiliary conditions.

Choose the Exceptions tab page in the BSP application PIQ_AUDIT.Exceptions can be:

The subrequirement is fulfilled.

You can change the target values of subrequirements, for example, specify that only 2 creditsare required instead of 8.

You can save the requirement profile you have created and edited under a specific profile name.

When you save the requirement profile, the system saves it in the form displayed. When you call this requirement profile the next time, the system does not generate it again but simply displays the requirement profile it saved.

You can lock the requirement profile to prevent it from being changed.

You can execute additional audit runs based on the saved requirement profile.