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_REGW04 | BAdI: Overriding of Message Types |
| Transaction Code | S_ANI_82001564 | (empty) |
| Created on | 20050314 | |
| Customizing Attributes | CM_XX_257_2_2 | Multiple Usage: Non-Critical Activity (IS-HER-CM-AD, ASAP 257) |
| Customizing Activity | CM_XX_REGW04 | BAdI: Overriding of Message Types |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | HRPIQ00TTMSGCNTL |
Use
This business add-in (BAdI) is used in the Campus Management Administration (IS-HER-CM-AD) component.
The BAdI enables you to determine which users are allowed to change the message type of specific messages in message control. You can use it to define authorizations for overriding of rules, and to query defined filter values. You can define filter values for this BAdI in the IMG activity Define Filter Values for Message Control.
The message control functions of Campus Management enable specific users to reduce the level of certain message types. You can create a message override authorization per user in the Message Control infotype (1749) of the respective rule container (object type RC). Here, you can also assign the defined filter values for each user in the BAdI Filter field.
When you assign a rule container to a callup point, you activate the functions for message control. You can use this filter-dependent BAdI, which is part of message type determination, for customer enhancements. The system calls this BAdI for a message if the BAdI Filter field in infotype 1749 contains an entry for the current message.
Example
You want to configure your system so that advisors may override the message types of certain messages for the students assigned to them. For example, you want to allow advisors to book a module for a student even if the maximum capacity of this module has already been reached or exceeded.
Requirements
Standard settings
The BAdI is filter-dependent. You define the filter values in the IMG activity Define Filter Values for Message Control.
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 | 20050420 |
| SAP Release Created in | 600 |
