SAP ABAP IMG Activity CM_XX_REGI09 (BAdI: Subsequent Activities for Registration Dialogs)
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_REGI09 BAdI: Subsequent Activities for Registration Dialogs  
Transaction Code S_KK4_82001190   IMG Activity: CM_XX_REGI09 
Created on 20030109    
Customizing Attributes CM_XX_257_2_2   Multiple Usage: Non-Critical Activity (IS-HER-CM-AD, ASAP 257) 
Customizing Activity CM_XX_REGI09   BAdI: Subsequent Activities for Registration Dialogs 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name HRPIQ00REG0090    

Use

This business add-in (BAdI) is used in the Campus Management Administration (IS-HER-CM-AD ) component.

You can use this BAdI to trigger a subsequent dialog for selected dialog functions in the student file. For example, you can define that the system call the module booking dialog or specialization maintenance transaction after you have created an initial registration.

You can currently implement this BAdI for the following dialog functions (the activity which is triggered when you use the BAdI as a filter value is given in parentheses):

  • Initial registration (RA01)
  • Sessional registration (RK01)
  • Leave of absence (RL01)
  • Change of program (RQ01)

Note

The system calls this BAdI only if you use the standard dialogs in the student file. If you create a registration or change of program by calling an SAP function module from a user-defined function, the system does not call this BAdI.

Standard settings

The default implementation for BAdI definition HRPIQ00REG0090 is active in the standard system.

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.

See also

Methods

Trigger Subsequent Activity

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 471