Child pages
  • BBP_ALERTING - Alerts, Messages and Events in SRM Alert Management
Skip to end of metadata
Go to start of metadata

Purpose

This page has the purpose of help the SRM community to understand and configure the SRM Alert Management

Overview

In this page you will find an explanation about all options available related to BAdIs and how to configure each one.

BBP_ALERTING - Alerts/Messages and Events in SRM Alert Management

Using BAdI BBP_ALERTING you can define your own events for SRM Alert Management and you can override existing (delivered) events. You can also override the standard alert categories and change the links (URLs) that the recipient uses to get to the relevant business object (document). In addition, you can use the document data to determine your own recipients.

Supplier Relationship Management → SRM Server → Cross-Application Basic Settings → Event and Event Schema for Alert Management.

The following methods are available:

  • BBP_EVENTS_ANALYZE: Change the standard events and define your own events
  • BBP_EVENTS_CATEGORIZE : Change the standard alert categories
  • BBP_EVENTS_DET_RECIPIENTS : Change the standard recipient
  • BBP_EVENTS_DET_FOLLOW_UP_URL : Change the links contained in the alerts/in the messages, for example, for the link to the affected document
  • BBP_EVENTS_DET_CLASS_NAME : Define the message class that is used for sending notifications

In order to receive detailed information on documents, document status, and document items, we recommend that you use the following function modules (the document GUID is available as an import parameter in the individual methods):

  • BBP_PD_ALL_GET_DIFF
  • BBP_PRODOC_GETDETAIL

This BAdI is not active in the standard delivery.  If the BAdI is activated without being changed, there are no changes in the system behavior.

 IF_EX_BBP_ALERTING_BADI BBP_EVENTS_ANALYZE - Events Process

Functionality: Method BBP_EVENTS_ANALYZE of BAdI BBP_ALERTING enables you to define your own new events and to override the standard events.

You can use the function module BBP_PD_ALL_GET_DIFF for detailed analysis of SRM documents, and to evaluate document and status changes for the event definitions.

Parameters :

  • IV_OBJECT_TYPE : Business transaction category (object type of the document)
  • IV_OBJECT_GUID : Document GUID
  • IT_OLD_STATUS : Table with old document status (before event)
  • IT_NEW_STATUS : Table with current document status (after event)
  • CT_EVENTS : Table with events
  • CT_MESSAGES : Error messages for the method

IF_EX_BBP_ALERTING_BADI BBP_EVENTS_CATEGORIZE - Change Categories from Events

Functionality: The method BBP_EVENTS_CATEGORIZE of BAdI BBP_ALERTING enables you to replace standard event categories. This way you can override the Customizing settings and define for example, that in the case of a specific event, a message rather than an alert is sent.

 Parameters :

  • IV_OBJECT_TYPE: Business transaction category (object type of the document)
  • IV_OBJECT_GUID: Document GUID
  • IT_OLD_STATUS: Table with old document status (before event)
  • IT_NEW_STATUS:  Table with current document status (after event)
  • CT_EVENTS: Table with event categories
  • CT_MESSAGES: Error messages for the method

IF_EX_BBP_ALERTING_BADI BBP_EVENTS_DET_RECIPIENTS - Define Recipient of Events

Functionality: Method BBP_EVENTS_DET_RECIPIENTS of BAdI BBP_ALERTING enables you, for each event, to change the standard recipient for alerts/messages and to add your own.

 Parameters:

  • IV_OBJECT_TYPE: Business transaction category (object type of document)
  • IV_OBJECT_GUID: Document GUID
  • IS_EVENT: Event
  • CT_RECIPIENTS : Alert/message recipient

IF_EX_BBP_ALERTING_BADI BBP_EVENTS_DET_FOLLOW_UP_URL - Determine URLs for Follow-up Processes

Functionality: Method BBP_EVENTS_DET_FOLLOW_UP_URL of BAdI BBP_ALERTING enables you, for each event, to change the standard link and to include your own links in the alerts/messages.

 Parameters:

  • IV_OBJECT_TYPE: Business transaction category (object type of document)
  • IV_OBJECT_GUID: Document GUID
  • IS_EVENT: Event
  • CT_FOLLOW_UP_URL: Table of links

IF_EX_BBP_ALERTING_BADI BBP_EVENTS_DET_CLASS_NAME - Define Message Class

Functionality: You can use this BAdI method to define the message class that is used for sending notifications. The default message class is CL_BBP_MESSAGE_CREATE.

 Parameters:

  • IV_OBJECT_TYPE: BOR object type for item and header
  • IS_EVENT: Structure for events and exceptions
  • CV_CLASS_NAME

SRM Alert Management (RELNEBP_55_ALERTING)

 As of SAP SRM 5.0, functionality is available that provides users with alerts and messages to inform them about predefined or critical statuses or events (exceptions) in the business process. Besides the information itself, the alerts enable the recipient to react directly to the underlying situation and to process it immediately. This effectively reduces the time gap between the occurrence and solving of critical statuses.

In order to send alerts, SRM Alert Management technically uses the Alert Framework.

Alerts reach the appropriate recipient per alert entry (in the Launch Pad: Alerts). (If SRM is running on an ERP platform, then in the Portal the central work list (UWL) is used for receiving and processing the alerts.) The recipient receives a link with a direct link to the relevant business object (for example, to an SRM document) - a direct reaction is expected from the recipient.

Messages are sent by mail to the recipient and only inform about the event that has occurred without expecting an immediate reaction. (The link contained here is only for information purposes.)

Tasks, as a third variant, are sent by workflow (WS14500051) so that the recipient has to carry out the relevant work item. SRM delivers a standard recipient determination for most events.

Alternatively you can define the recipient determination in the respective alert categories of the classification SRM Alerts (SAP Web Application Server → SAP Web Application Server → Generic Business Tools → Alert Management → Define Alert Categories) or by implementing the BAdI BBP_ALERTING.
The texts for the individual alert categories (changeable) are stored here (Message title: Subject line of alert/message, short and long text: consist of the event text and the message text generated by the application or by a system report).

You can define your own alert categories or modify the delivered ones.

The Smart Form BBP_OUT_EXCEPTION controls the layout, the displayed text and its elements, the logic etc. of the notification e-mail.

Details:

SRM delivers predefined events for the majority of the business objects, for example, (z.B. BUS2000113 - purchase contract_)_ (IMG: Supplier Relationship Management -> SRM Server -> Cross-Application Basic Settings -> Event and Event Schema for Alert Management → Define Events).

In event schemas these events are linked with the alert category (IMG: Supplier Relationship Management -> SRM Server -> Cross-Application Basic Settings -> Event and Event Schema for Alert Management → Define Event Schema).

Using the event schema, you can define the following:

  • Whether an alert, a task, or a message is to be sent for this event (Event category)
  • The alert category (subcategory of the event)
  • How many hours after the occurrence of an event the appropriate alert or message is to be sent.

Effects on Customizing

  • You make the settings for SRM Alert Management in the IMG:

Supplier Relationship Management -> SRM Server -> Cross-Application Basic Settings -> Event and Event Schema for Alert Management → ...

  • Using BAdI BBP_ALERTING(Alerts/Messages and Events in SRM Alert Management), you can make the following settings at variance with the SRM standard:
    • Alert Categories
    • Events and Alerts/ Messages
    • Recipient Control
    • URLs for the jump to the relevant documents
  • In the IMG under Supplier Relationship Management → SRM Server → Cross-Application Basic Settings → Define Transaction Types you can assign an event schema of a business object to a transaction type and thus make event control even more detailed.  Only when an event schema is also assigned to a transaction type, is the Alert function for this also activated!
  • As a technical prerequisite for triggering alerts and notifications, the report on deadline monitoring must be scheduled as a background job:

IMG: Supplier Relationship Management → SRM Server → Cross-Application Basic Settings → SAP Business Workflow → Maintain Standard Settings for SAP Business Workflow → Maintain Runtime Environment → Schedule Background Job for Deadline Monitoring