SAP ABAP IMG Activity CM_XX_146 (BAdI: Organizational Unit of Alumnus)
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_146 BAdI: Organizational Unit of Alumnus  
Transaction Code S_KK4_82000502   (empty) 
Created on 20010119    
Customizing Attributes CM_XX_257_2_2   Multiple Usage: Non-Critical Activity (IS-HER-CM-AD, ASAP 257) 
Customizing Activity CM_XX_146   BAdI: Organizational Unit of Alumnus 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name CM_XX_146    

In this activity, you use the business add-in HRPIQ00_ALUMNUS_ORG to implement the following methods:

  • DEFINE_ALUMNUS_RELAT_EARLY: This method is implemented before the system derives the organizational unit. You can implement this method if you always use the same same organizational unit or if you do not want to create an alumnus relationship.
  • DEFINE_ALUMNUS_RELAT_LATE: This method is implemented after the system derives the organizational unit. You can use this method if you want to use a different organizational unit than was derived by the system.

Description

If the business add-in is implemented, these methods are called when a student is de-registered from a program and the indicator for creation of an alumnus relationship is set.

The method DEFINE_ALUMNUS_RELAT_EARLY is called before the system derives the organizational unit. If this method returns an organizational unit or an indicator specifying that an alumnus relationship should not be created, the system then does not derive the organizational unit. You can use this method if, for example, you want to ensure that the same organizational unit is used for each alumnus or that an alumnus relationship is not created.

The method DEFINE_ALUMNUS_RELAT_EARLY_LATE is called after the system has derived the organizational unit. If you want to, you can define an organizational unit different from the one derived by the system. For example, if the programs and modules are offered by the university departments, the system would derive "department" as the organizational unit for the alumnus relationship. However, if you do not want to assign the alumnus to a department but to the higher-level faculty, you can use the method DEFINE_ALUMNUS_RELAT_EARLY_LATE to determine this faculty and assign it to the alumnus.

Parameters

The current plan version (PLVAR), the object type (OTYPE), the object ID (OBJID) of the student and program, the registration end date, and the process and reason for program de-registration are transferred in the structure PIQALUMNUS_BADI. The proposed start and end dates of the alumnus relationship are also transferred in this structure; these dates can be overwritten. You can therefore not only define the organizational unit but also the validity of the alumnus relationship independent of the parameters that are transferred.

You can also use the method DEFINE_ALUMNUS_RELAT_EARLY to return the organizational unit you have defined or the indicator specifying that an alumnus relationship should not be created.

The method DEFINE_ALUMNUS_RELAT_LATE transfers the organizational unit derived by the system; this organizational unit can be overwritten. This method also transfers the organizational unit derived by the system, and the organizational unit assigned directly to the student, if one is assigned.

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 463