A number of Business Add-Ins (BAdIs) are available to enable you to make enhancements without having to perform a modification.
This method is used to determine the expiry date of an alert. It is provided with the alert category as filter value.
The method is called if the application does not pass any expiry date in the container.
Parameter |
Meaning |
FLT_VAL |
Filter value of BAdI (alert category in this case) |
II_CONTAINER |
Container with parameters passed by the application |
IP_LOGHANDLE |
Current log (you can add your own messages) |
RP_EXP_DATE |
Desired expiry date as time stamp |
For an example implementation with an expiry time of one day (86,400 seconds), see the BAdI ALERT_EXP_1DAY.
This method is called immediately before an alert is deleted, and enables the application to react at this point in time.
Parameter |
Meaning |
FLT_VAL |
Filter value of BAdI (alert category in this case) |
IO_ALERT |
Alert to be deleted |
IP_LOGHANDLE |
Current log (you can add your own messages) |
This method enables the application to react after an alert has been confirmed.
Parameter |
Meaning |
FLT_VAL |
Filter value of BAdI (alert category in this case) |
IO_ALERT |
Alert that was confirmed |
IP_UNAME |
User who confirmed the alert (optional) |
IP_LOGHANDLE |
Current log (you can add your own messages) |
This method enables the application to change the content of the long text after it has been created.
Parameter |
Meaning |
FLT_VAL |
Filter value of BAdI (alert category in this case) |
IO_ALERT |
Current alert |
IP_LANGU |
Current language |
IP_LOGHANDLE |
Current log (you can add your own messages) |
CT_LONG_TEXT |
Text |
This method enables the application to override the standard implementation for time-dependent delivery (personalization).
Parameter |
Meaning |
IO_ALERT |
Alert |
IS_PERS |
Personalization data |
IP_UNAME |
User name |
IP_PROTOCOL |
Log handle |
PE_PAG |
Dispatch by SMS |
PE_INT |
Dispatch by Internet mail |
PE_FAX |
Dispatch by fax |