Ansicht
Dokumentation

SRP_BASIC_6A - Business Add-In: Alert Delivery

rdisp/max_wprun_time - Maximum work process run time   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

In this IMG activity you view implementations of the Alert Delivery Business Add-In (BAdI). The BAdI may be implemented through the standard procedure for implementing a BAdI in the system.

The Alert Delivery BAdI allows clients of WFD Server Alerts to specify alert recipients based on recipient attributes. The WFD Server defines alert conditions, and can trigger alerts via background processes. Once you define alert recipients using this BAdI, alerts are delivered to those recipients through the Central Alert Framework.

The BAdI definition defines only the method GET_RECIPIENTS. This method imports parameters that define the alert category and business objects, and exports a table of the users in whose inbox the alert should appear.

The alert category parameter IV_ALERT_CAT is a 30-character string that matches one of the alert category definitions for WFD Server defined through the standard transaction ALRTCATDEF.

The method also imports attributes for ASSIGNMENT, DEMAND, and RESOURCE business objects. There are three attributes for each business object: its 32 character external key (suffix _KEY), the application type of the client (_AWTYP), and the logical system of the client (_LOGSYS).

Since the BAdI is of type multiple use,the parameter C_ALERT_RECIPIENT_TAB is of type changing. This means that anyone implementing the BAdI must not alter rows imported in this parameter, but only add to them.

The alert categories 'ASSIGNMENT_WHEN_UNAVAILABLE' and 'QUALIFICATION_MISMATCH' are defined as part of the default configuration.

There is a default implementation provided by the Service WFD for the Alert Delivery BAdI. Refer to the IMG documentation in Service Resource Planning for details of this implementation.

Removing the default implementation without specifying at least one default recipient in the replacement implementation will cause alerts to vanish invisibly, which will negatively impact the integrity of the system.

Fill RESBD Structure from EBP Component Structure   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 2223 Date: 20240523 Time: 161207     sap01-206 ( 46 ms )