Hierarchy

⤷

⤷

IMG Activity
ID | CM_XX_STUD16 | BAdI: Status Display in the Student Data Header |
Transaction Code | S_KK4_82000946 | IMG Activity: CM_XX_STUD16 |
Created on | 20020124 | |
Customizing Attributes | CM_XX_257_2_2 | Multiple Usage: Non-Critical Activity (IS-HER-CM-AD, ASAP 257) |
Customizing Activity | CM_XX_STUD16 | BAdI: Status Display in the Student Data Header |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | HRPIQ00_ST_HD_HS |
Use
This business add-in (BAdI) is used in the Campus Management Administration (IS-HER-CM-AD) component.
You can use this BAdI to control the setup of the status line in the student file and student master data header.
If you do not create an implementation, the system uses the SAP default implementation. In this implementation, the system first determines all active statuses of the student and the study objects assigned to him/her. Then it compresses the data records as follows:
- If several data records exist for one status of an object (student or study) in different sessions, the system displays only one status record in the status header.
- If the same status exists for several objects, the system determines the number of statuses and displays this number behind the respective status.
Apart from the student status, the standard system displays the student group and the student's part-time and full-time status in the status line.
You can format the status line according to your own requirements by creating a user-defined implementation of the method BUILD_STATUS_LINE. We recommend you use the standard implementation as a template.
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:
- 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. - On this screen, enter a short description for your implementation in the Implementation Short Text field.
- 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.
- Save your entries and assign the Add-In to a package.
- To edit a method, double-click its name.
- Enter your implementation code between the
method <Interface Name>~<Name of Method>.
andendmethod.
statements. - 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: - Choose Activate.
When the application program is executed, the code you created is run through.
See also
Method
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 | 20030122 |
SAP Release Created in | 464 |