SAP ABAP IMG Activity CM_XX_STAT05 (Assign Hold Types to Callup Points and Activities)
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_STAT05 Assign Hold Types to Callup Points and Activities  
Transaction Code S_KK4_82000799   (empty) 
Created on 20011026    
Customizing Attributes CM_XX_204_2_1   Multiple Use: Critical Optional Activity, IS-HER-CM-AD, ASAP 204 
Customizing Activity CM_XX_STAT05   Assign Hold Types to Callup Points and Activities 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name CM_XX_STAT05    

Use

In this IMG activity, you can assign hold types to the callup point and activity combinations and define a message for each assignment.

Activities in Campus Management can be blocked by holds which are active on a given key date. If you want the system to check specific holds at a callup point within an activity, you must assign the respective hold type here.

The settings you make in this IMG activity affect the system's response:

  • If you do not assign a hold type to a given callup point, the system cannot block the activities defined for this callup point with a hold.
  • If you assign a hold type but not an activity to a given callup point, the system can block all the activities defined for this callup point with a hold (activity-independent entry).
  • If you assign both a hold type and an activity to a given callup point, the system can block the assigned activity at this callup point with a hold (activity-dependent entry).

Please note that you may not create both an activity-independent and activity-dependent entry for a particular callup point and hold type combination.

Optionally, you can define a message for each callup point and hold type combination. If you do not specify a message here, the system uses the message which is assigned to the hold type in the IMG activity Assign Attributes to Hold Types. If you do specify a message, the system uses this message.

Requirements

Here, you can only use callup points which have been flagged as relevant for status indicators (see table T7PIQCHECKTP (Callup Points)).

You can only choose the activities that are actually assigned to a callup point. You can view these assignments in the IMG activity Assign Activities to Callup Points. The system uses these assignments as a foreign key table to block activities with holds at specific callup points.

Standard settings

Activities

  1. Choose a callup point and assign it an activity.
  2. Then assign a hold type.
  3. Assign a message if required.
    1. Choose a message type.
    2. Enter a message class. In the Message field, specify the number of the message within the given message class.
    3. You can enter up to four message variables.
      In the message variables, you can enter a user-defined text (see example below).

Example

You want to make module booking dependent on a specific hold. You assign the appropriate hold type to the combination of callup point 0001 (Module Booking (General) and activity MB00 (Module Booking).

You also specify a user-defined message for this entry. You use message 001 which you have created in message class ZCUSTOMER for this purpose. This message contains the following short text:

&1 is not possible because of &2

You then make the following entries in this IMG activity:

  • Message type: E
  • Message class: ZCUSTOMER
  • Message: 001
  • Message variable 1: Module booking
  • Message variable 2: Academic hold

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 1   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
V_T7PIQHSCHECK_H V - View SM30  
History
Last changed by/on SAP  20041203 
SAP Release Created in 464