SAP ABAP IMG Activity CM_XX_500 (BAdI: Determine/Derive Organizational Unit of Student)
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_500 BAdI: Determine/Derive Organizational Unit of Student  
Transaction Code S_KK4_82000716   (empty) 
Created on 20010419    
Customizing Attributes CM_XX_257_2_2   Multiple Usage: Non-Critical Activity (IS-HER-CM-AD, ASAP 257) 
Customizing Activity CM_XX_500   BAdI: Determine/Derive Organizational Unit of Student 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name HRPIQ00_STUDENT_ORG    

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

You can use the BAdI HRPIQ00_STUDENT_ORG to implement the following methods:

  • STUDENT_ORGUNIT_GET_EARLY: Determines the organizational unit for a student before the standard process is executed
  • STUDENT_ORGUNIT_GET_LATE: Determines the organizational unit for a student after the standard process has been executed
  • STUDENT_ORGUNIT_DERIVE_EARLY: Derives the organizational for a student before the standard derivation is executed
  • STUDENT_ORGUNIT_DERIVE_LATE: Derives the organizational for a student after the standard derivation has been executed
  • STUDY_ORGUNIT_DERIVE_EARLY: Derives the organizational unit for a study object before the standard derivation is executed
  • STUDY_ORGUNIT_DERIVE_LATE: Derives the organizational unit for a study object after the standard derivation has been executed

Description

If the business add-in is implemented, the system calls these methods when:

  • determining the organizational unit for a student
  • deriving the organizational unit for a student
  • deriving the organizational unit for a study object

As the method names indicate, there are two methods for each activity:

  • The methods STUDENT_ORGUNIT_GET_EARLY, STUDENT_ORGUNIT_DERIVE_EARLY and STUDY_ORGUNIT_DERIVE_EARLY are called before the standard process or standard derivation is executed. You can therefore implement your own algorithms for determining and deriving the organizational unit. If the methods return an organizational unit, the standard process or standard derivation is not executed.
  • The methods STUDENT_ORGUNIT_GET_LATE, STUDENT_ORGUNIT_DERIVE_LATE and STUDY_ORGUNIT_DERIVE_LATE are executed after the standard process or standard derivation. You can therefore determine a different organizational unit based on the results of the standard process or standard derivation.

    Example: The result of a standard derivation is a university department. Instead of the department, you want the result to be a faculty. You can use these methods to determine the faculty to which the department in question is assigned, and return this faculty as the result.

Parameters

All methods have the import parameters STUDENTORG_PARAM and BEGDA, and the changing parameter ENDDA. The parameter STUDENTORG_PARAM contains the plan version, object type and object ID of the student for whom the organizational unit is being determined or derived. BEGDA and ENDDA delimit the validity period of the result. The start date (BEGDA) is fixed

The methods STUDY* also have the import parameter STUDYORG_PARAM which contains the plan version, object type and object ID of the study object for which the organizational unit is being determined or derived.

The methods *EARLY have the export parameter ORGUNIT_OBJID which returns the result of the method to the SAP standard implementation.

The methods *LATE have the changing parameter ORGUNIT_OBJID which contains the result of the SAP standard implementation at the beginning of method execution. During method execution, this parameter can be changed so that the result of the method is returnd to the SAP standard implementation at the end of method execution.

All methods have the exception DERIVATION_ERROR. This exception is triggered when an error occurs in the method.

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 you call the IMG activity, the system displays a dialog box where you enter a name for the implementation.

If implementations of this Business Add-In have already been created, the system displays them in a dialog box. You then choose one of them by choosing Create, and continue as follows:

  1. In the dialog box, enter a name for the implementation of the Add-In and choose Create.
    The system displays the initial screen for creating Business Add-In implementations.
  2. On this screen, enter a short description for your implementation in the Implementation Short Text field.
  3. If you choose the Interface tab, you will notice that the system has populated the Name of the Implementing Class field automatically, by assigning a class name based on the name of your implementation.
  4. Save your entries and assign the Add-In to a package.
  5. To edit a method, double-click its name.
  6. Enter your implementation code between the method <Interface Name>~<Name of Method>. and endmethod. statements.
  7. Save and activate your code. Navigate back to the Change Implementation screen.
    Note: You can also create an implementation for an Add-In and not activate it until later. If you want to do this, do not perform the following step:
  8. Choose Activate.
    When the application program is executed, the code you created is run through.

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