Audit

Purpose

You can use Student Lifecycle Management audit functions like S tage Audit and Degree Audit to set the general and special requirements students have to fulfil, and to check if the academic work they have completed meets these requirements.

(See also: Audit Overview )

Prerequisites

You have made the required settings in Customizing for Student Lifecycle Management under Start of the navigation path Student Lifecycle Management Processes Next navigation step Audits End of the navigation path .

For index-dependent subrequirements, you require performance indexes. You define these in Customizing for Student Lifecycle Management under Start of the navigation path Student Lifecycle Management Master Data Next navigation step Performance Indexes End of the navigation path .

For index-independent subrequirements, you require conditions. You implement these in Customizing for Student Lifecycle Management under Start of the navigation path Student Lifecycle Management Processes Next navigation step Audits Next navigation step Requirements Next navigation step Subrequirements Next navigation step BAdI: Subrequirement Condition End of the navigation path .

For auxiliary conditions, you require key figures . You define these in Customizing for Student Lifecycle Management under Start of the navigation path Student Lifecycle Management Master Data Next navigation step Key Figures End of the navigation path .

If you want the system to generate module proposals for a subrequirement, you must create the appropriate selection methods. You define these in Customizing for Student Lifecycle Management under Start of the navigation path Student Lifecycle Management Processes Next navigation step General Settings Next navigation step Selection Methods End of the navigation path . The system uses the selection method group AUDS for audits. For more information, see Object Selection Using a Selection Method .

Process Flow

  1. You edit requirement catalogs by assigning them (concrete) requirements, subrequirements, and auxiliary conditions.

    You can access the requirement catalog editing transaction from the SAP Easy Access screen by choosing Start of the navigation path SAP Menu Next navigation step Student Lifecycle Management Next navigation step Academic Structure (Curriculum) Next navigation step Requirement Catalogs Next navigation step Edit Requirement Catalog. End of the navigation path You use the Subrequirement Manager to assign existing subrequirements and auxiliary conditions.

    You define the usage for requirements. General university requirements (rule container) are linked to a faculty, that is to an organizational unit (object type O), program requirements to a program (object type SC,) and requirements for academic specializationsto module groups (object type CG).

  2. You assign the main requirement catalog and catalog version to each student on the Requirement Catalogs tab page in the Student File .

    Note Note

    If you do not want to assign each individual student a main requirement catalog, you can assign the main requirement catalog to a specific organizational unit (object type O) in the academic structure. If you do so, you must also assign the audit type an evaluation path which the system can use to find this organizational unit. You assign the evaluation path in Customizing for Student Lifecycle Management by choosing Start of the navigation path Student Lifecycle Management Processes Next navigation step Audits Next navigation step Basic Settings Next navigation step Define Audit Types End of the navigation path .

    End of the note.

  3. If the requirements for a student are taken from different requirement catalogs, the system uses the catalog version you have flagged for each requirement catalog.

    The catalog version is determined as follows:

    1. If you have assigned the student a specific version of the requirement catalog in the student file, the system uses this catalog version.

    2. If you have not assigned the student a specific version of the requirement catalog in the student file, the system uses the version within the requirement catalog version set which is flagged as the default version . You set this flag in Customizing for Student Lifecycle Management under Start of the navigation path Student Lifecycle Management Processes Next navigation step Audits Next navigation step Requirement Catalogs Next navigation step Define Structure of Version Sets End of the navigation path .

      Note Note

      If the system finds a rule container (object type RC) using a requirement selection, the rule container contains the name of the requirement catalog to which it belongs. The system also requires the catalog version when it determines the subrequirement.

      End of the note.

  4. You create a requirement profile for the students for whom you want to run an audit.

    If you want the system to generate requirement profiles (and execute audit runs) automatically, you can use the following report programs:

  5. You start the audit run with one of the above report programs. In the audit run, the system compares the requirements in the requirement profile with the student’s completed and transferred academic work, and displays the results.

    Note Note

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

    End of the note.