SAP ABAP IMG Activity CM_XX_AUDIT31 (Set Up Views of BSP Applications)
Hierarchy
☛ IS-PS-CA (Software Component) IS-PUBLIC SECTOR CONTRACT ACCOUNTING
   ⤷ IS-HER-CM-AD (Application Component) Administration
     ⤷ PMIQ (Package) Campus Management
IMG Activity
ID CM_XX_AUDIT31 Set Up Views of BSP Applications  
Transaction Code S_KK4_82001290   (empty) 
Created on 20031021    
Customizing Attributes CM_XX_204_2_2   Multiple Use: Non-Critical Optional Activity, IS-HER-CM-AD, ASAP 204 
Customizing Activity CM_XX_AUDIT31   Set Up Views of BSP Applications 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name CM_XX_AUDIT31    

Use

In this IMG activity, you set up the views of the BSP application PIQ_AUDIT. This BSP application offers different views of the application, which are intended for different users (students, experts, etc.). For each of these views, you can define which actions and exceptions are allowed.

You can call the BSP application PIQ_AUDIT with several SAP-defined views, which are as follows:

  • EV01 - Expert view (with reference to processes)
  • EV02 - Expert view
  • EXV1 - Extended maintenance (with reference to processes)
  • EXV2 - Extended maintenance
  • SV01 - Student view (with reference to processes)
  • SV02 - Student view

If you use assessment processes when you map your university's processes, you can use the BSP applications that refer to an assessment process. If you do, the system displays the assessment process before it creates a requirement profile or an audit.

The views for the different user groups (students, experts, etc.) and for extended maintenance have different editing options.

You can define actions and exceptions for each view, and thus change the appearance of the user interface. If the creation of exceptions is not permitted in a particular view, the system will then not display the create action as a pushbutton. If, in a particular view, you do not set the exception which allows key figures to be overwritten, then the relevant fields are not ready for input in this view.

Actions and exceptions can be used in the following applications:

  • Requirement profile editing
  • Audit editing
  • Independent of the above applications

You can define in which application an action or exception should be used by specifying the reference type in the action group or exception group.

Note: You can change the SAP action names according to your individual requirements. You make this setting in the next IMG activity Change SAP Action Names.

The system offers the following independent actions:

  • AR01 - Create audit
  • ARTM - Create audit with template (copy)
  • EXC1 - Create exceptions for subrequirement
  • EXC2 - Change exceptions for subrequirement
  • EXC3 - Delete exceptions for subrequirement
  • EXC4 - Display exceptions for subrequirement
  • OVOA - General audit access

    If this action is not allowed, you will not be able to display or edit audits.

  • OVOP - General requirement profile access
  • OVTA - General audit access for test purposes
  • OVTP - General requirement profile access for test purposes

    Note: The system distinguishes between requirement profiles which are official and those which are used only for test purposes. The official indicator is set for the requirement profile type of official requirement profiles. The system also makes this distinction for audits by means of the execution mode indicator.

  • PR01 - Create requirement profile
  • SIMU - Simulate requirement profile

The system offers the following actions for audits:

  • AR02 - Change audit
  • AR03 - Delete audit
  • AR04 - Display audit
  • AR05 - Save audit
  • AR06 - Create audit for test purposes
  • ARRC - Check audit

    You can use this action to reevaluate an existing audit without changing the modules assigned to it.

  • ASSI - Assign modules to subrequirements
  • AUTO - Automatic calculation

    You can use this switch to control automatic calculation in the user interface

  • BOOK - Test booking

    You can use this switch to test book the modules you want to use in an audit.

  • CALC - Recalculate key figures and performance indices
  • EVAL - Reevaluate audit

    Here, new modules are assigned to the subrequirements, unlike in the check audit action.

  • PRNT - Print preview
  • PROP - Propose modules for subrequirement
  • RELA - Release audit
  • SRSM - User-defined search for modules. The modules the system finds can then be assigned to the subrequirements
  • UREL - Undo release of an audit
  • ANAL - Check if the modules are used as specified in the filter definitions of the subrequirements (see also exception MODA - freely assign modules).

The system offers the following actions for requirement profiles:

  • PR02 - Change requirement profile
  • PR03 - Delete requirement profile
  • PR04 - Display requirement profile
  • PR05 - Save requirement profile
  • PR06 - Create requirement profile for test purposes
  • LOCK - Lock requirement profile
  • UNLO - Unlock requirement profile

The system offers the following exceptions for audits:

  • CRHV - Change the grade and credits of the modules assigned to a subrequirement
  • KEYV - Overwrite key figures
  • MODA - Freely assign modules to subrequirements (even if these do not correspond to the module selection definition of the subrequirement)
  • RESV - Overwrite final results of subrequirements and requirements

The system offers the following exceptions for audits:

  • EXCP - Insert and delete subrequirements

Activities

  1. Combine the actions you want to use in a view to an action group. You must make this setting for the following applications:
    • Actions in a view for audit editing
    • Actions in a view for requirement profile editing
    • Independent actions

      You can use an action group for more than one view.

  2. Combine the exceptions you want to use in a view to an exception group. You must make this setting for the following applications:
    • Exceptions for audits
    • Exceptions for requirement profiles
    • Independent exceptions

      You can use an exception group for more than one view.

  3. Then set up the views. You can now assign action groups and exception groups to each view. You can also create views based on the following attributes:

Example

You can use a view to define that students are allowed to display an official audit, but not change it.

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
VC_T7PIQAUDDVIEW C - View cluster SM34  
History
Last changed by/on SAP  20031023 
SAP Release Created in 472