Vous êtes sur la page 1sur 2

SALRT, SALRTCNT (Alert Management)

Alert Management (ALM) comes into play when business-critical problems occur.
Within ALM, conditions for
critical situations are predefined. When a situation occurs that meets these
conditions, an alert is triggered
and responsible or interested parties are determined and informed immediately.
Examples of critical
situations are an important customer terminating a contract or a budget being
exceeded.
The alerts can be found in the universal worklist (UWL) of the SAP Enterprise
Portal, application-specific
display programs, or the alert inbox. These display programs can be personalized to
the user’s needs. In
addition, the users can receive alerts as e-mail, SMS, and fax if these external
methods of communication are
configured in SAPconnect. End users can personalize their alert notifications, for
example, create notification
variants, or determine a substitute.
Alert Management helps prevent delays in the processing of critical situations
because the time between
discovering and responding to such situations is reduced considerably.
5.1.21.1 Avoidance
Alerts of a particular category must be triggered by an application at runtime.
This can be done in various
ways, such as using a function module, an event linkage, or the Post Processing
Framework (PPF).
To avoid certain alerts in the future, you can either remove the responsible
triggers within the different
applications directly or adjust the general alert processing in a way that no
“final” alert is created within the
central alert system.
For more information about the different possibilities to trigger an alert please
see the SAP
Library for SAP NetWeaver: SAP NetWeaver by Key Capability  Application Platform
by Key
Capability  Business Services  Business Communication Services  Alert
Management
(BC-SRV-GBT-ALM).
5.1.21.2 Deletion
If you use the local Alert Framework to generate alerts, for example, by using
message-based alerting, you
also have to consider deletion of alerts in your system. Otherwise, tables SALRT
and SALRTCNT can grow
significantly. To delete alerts, report RSALERTPROC has to be scheduled regularly.
In the top fields on the selection screen, you can enter the alert classifications
and alert categories for which
you want the report to become active. You can then choose if alerts are deleted
after their expiry time.
Alternatively to triggering the deletion based on the expiry time, it is also
possible to delete old alerts or old
logs and enter the number of days after which they are to be deleted. In the case
of deleting old alerts, you
can also choose to have only confirmed alerts deleted.
Please be aware that depending on the chosen selection criteria, report RSALERTPROC
is not a pure
deletion report but can also be used to trigger the escalation or repeated delivery
of alerts.
Note: Report RSALERTCONS can also be used if the containers (stored within table
SALRTCNT) of the
alerts have not been deleted and remain in the system after running report
RSALERTPROC. Please see SAP
Note 940619 (SAP_BASIS 620 – 700).

Vous aimerez peut-être aussi