SAP ABAP IMG Activity CM_XX_MOBU08 (BAdI: Cancellation Reason for Withdrawal From Module)
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_MOBU08 BAdI: Cancellation Reason for Withdrawal From Module  
Transaction Code S_KK4_82000811   (empty) 
Created on 20011106    
Customizing Attributes CM_XX_257_2_2   Multiple Usage: Non-Critical Activity (IS-HER-CM-AD, ASAP 257) 
Customizing Activity CM_XX_MOBU08   BAdI: Cancellation Reason for Withdrawal From Module 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name HRPIQ00CANCELREASON    

Use

You can use this customer enhancement to set a cancellation reason for the withdrawal from a module which is dependent on the cancellation date in the business add-an HRPIQ00CANCELREASON. To set a cancellation reason, you must implement the method SET_REASON.

When you create a withdrawal from module for a student, the system reads the module bookings that have the status

  • 01 (booked),
  • 05 (selected), and
  • 06 (prebooked).

It then sets the status to

  • 04 (cancelled) or
  • 07 (prebooking cancelled).

The system either updates the cancellations directly or displays the cancellations in list form depending on the Customizing setting of the IMG activity Define Module for Withdrawal from Module Dialog. You can edit the listed cancellations if required. You set the cancellation reasion using this customer enhancement.

The SET_REASON method uses the following parameters:

  • Import parameters
    • STUDENT: Student for whom the module is cancelled
    • DATE: Date on which the module is cancelled
  • Export parameters
    • CANCEL_REASON: Cancellation reasaon which the system sets in the module booking records

Further notes

You should perform this activity only if both of the following conditions are satisfied:

  • The SAP standard processes do not cover your requirements.
  • You have an in-depth knowledge of the ABAP programming language.

Business add-in implementations are code extensions and therefore apply across clients. If you have a multiclient system, you have to define how the customer enhancement is to be used within the implementation for each client using the system variable SY-MANDT.

Business add-ins without multiple usages can have several implementations. However, only one of these implementations may be active at any one time.

You must also make sure that instance creation for the implementing class (Properties tab page) is declared as public and not as private, protected, or abstract. Otherwise unwanted short dumps may occur during runtime.

General information and implementation instructions for business add-ins are found in the SAP library under Basis Components -> ABAP Workbench (BC DWB) -> Changes to the SAP Standard (BC) -> Business Add-Ins. You can also access this documentation from the initial BAdI builder screen via Help -> Application help.

Activities

After calling up the IMG activity, a dialog box appears, in which you can enter a name for the implementation.

If you have already made other implementations for this BAdI, another dialog box appears, in which the existing implementations are displayed. In this case, choose Create, and proceed as follows:

  1. In the dialog box, enter a name for the BAdI implementation in the Implementation field, and choose Create.

    The screen for creating BAdI implementations is now displayed.

  2. Enter a short text for the implementation in the Short text for implementation field.
  3. From the tab index, choose Interface.

    The Name of implemented class field is already filled on the tab page, as a class name was automatically assigned to the implementation when you named it.

  4. Save your entries, and assign the implementation to a development class.
  5. Place the cursor on the method, and double-click to enter method processing.
  6. Enter the code for the implementation between the statements method <Interface name> ~ <Name of method> and endmethod.
  7. Save and implement your code. Return to the Edit Implementation screen.
  8. Save the entries on the Edit Implementation screen.

    Note: You can also create an implementation, and then activate it at a later time. In such a case, end the processing stage at this point.

  9. Choose Activate

    The code you stored in the method will be run when the application program is executed.

Business Attributes
ASAP Roadmap ID 257   Create User Exits 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20030113 
SAP Release Created in 464