Hierarchy

⤷

⤷

IMG Activity
ID | /MRSS/ALERT_FUNCTION | BAdI: User functions for alerts |
Transaction Code | /MRSS/35000045 | IMG activity: /MRSS/ALERT_FUNCTION |
Created on | 20061016 | |
Customizing Attributes | /MRSS/ALERT_FUNCTION | BAdI: User functions for alerts |
Customizing Activity | /MRSS/ALERT_FUNCTION | BAdI: User functions for alerts |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | /MRSS/ALERT_FUNCTION |
Use
You use this BAdI to update user functions for alerts.
Standard settings
There are two ways to do this:
- BUTTON_PROPERTIES
You use this method to define the attributes of a button that is used to call the user function. An icon, quick info, and button text can all be returned as parameters. If there is no BAdI implementation or if the values are initial, the system does not display a button.
- EXECUTE
This method is called if an alert has been selected in the resource planning board and the button that triggers the user function is pressed. As parameters, the method contains a structure with alert data:
- Alert type (MSGID, MSGTY, ALERT_TYPE_DISPL; MSGNR): This data is used to identify whether a user function is defined for this alert.
- Alert data (VAR1, VAR2, VAR3, VAR4): Variables that were determined in the check class of the alert are transferred here.
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.
Example
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 |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | /MRSS/ALERT_FUNCTION | 0 | HLB0009110 | Cross-Application Components |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20090903 |
SAP Release Created in | 195 |