SAP ABAP IMG Activity CM_XX_135 (BAdI: Student Number Assignment)
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_135 BAdI: Student Number Assignment  
Transaction Code S_KI4_55000324   (empty) 
Created on 20000315    
Customizing Attributes CM_XX_257_2_2   Multiple Usage: Non-Critical Activity (IS-HER-CM-AD, ASAP 257) 
Customizing Activity CM_XX_135   BAdI: Student Number Assignment 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name CM_XX_135    

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

You can use this BAdI to implement the following methods:

  • CHECK: Check Student Number (External Number Assignment)
  • GET_NEXT: Get Next Student Number (Internal Number Assignment)

Description

If the business add-in is implemented, the system calls these methods when you create a student master record. It calls the method CHECK if you use external number assignment. It calls the method GET_NEXT if you do not enter a student number.

You can therefore map your rules for student number assignment in the system and, for example, use the check digit procedure and year-specific number assignment.

Parameters

In addition to the current plan version (PLVAR), the object type (OTYPE) and object ID (OBJID) of the student, the system transfers the start date of the student master record and the date on which the student is created. This enables you to use year-specific number assignment and your own number range object. The student number you enter is transferred to the method CHECK in the field STUDENT_NUMBER. When the method GET_NEXT is called, the student number is transferred to the calling program in the field STUDENT_NUMBER.

In addition, all the data stored in the Personal Data infotype (1702) is transferred. Which data this is depends entirely on the method that was used to create the student. The system does not check if the data fields of the Personal Data infotype (1702) contain data before it calls the business add-in.

Note

The standard functions of Campus Management ensure that the student number is a unique identification criterion.

If you derive the business partner number from the student number, you should configure your system so that subsequent changes to the student number are not allowed. You can do this by not assigning the authorization for transaction PIQSTU1 (change student number ).

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

If implementations already exist, choose the required implementation by double clicking it.

If no implementation exists, proceed as follows:

  1. Enter a name for your implementation, and choose Copy.
  2. Enter an implementation short text.
  3. On the tab page Interface, choose a method for the implementation by double clicking the required entry.

    After you have selected the method, the system prompts you to save your implementation.

  4. Save your implementation, and enter a development class.

    The Class Builder appears.

  5. Enter your own program code between the statements method if_ex_... and endmethod.
  6. Save your entries, and return to the BADI Builder: Change Implementation screen.
  7. Choose Activate.

Further notes

See also

Methods

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