Ansicht
Dokumentation
RIST_NLM_WFM_CREATE_ALERT_SLA - Create Alerts for Orders That Violate the SLA
rdisp/max_wprun_time - Maximum work process run time ABAP Short ReferenceThis documentation is copyright by SAP AG.
Purpose
Create Alerts for PM Orders That Violate the Service Level Agreement (SLA)
A SLA violation for an order occurs in the following cases:
- If the actual date is later than the order end date defined by the SLA, and the order has yet to be confirmed.
- If the actual date and the scheduled order end date are the same, but the actual time is later than the order end time, and the order has yet to be confirmed.
The selection fields mean that you can also create an alert for orders that will violate a service level agreement in an hour if the order is not confirmed by that point. This means that you can take appropriate measures before a SLA violation occurs.
Integration
Alerts are displayed in the Workforce Managerrole in the UI Building Block (user interface module) Alert Monitor in the portal.
Prerequisites
You have recorded an alert category for orders that violate the service level agreement in Customizing. Define the alert categories using the ALRTCATDEF transaction. You also specify the recipient of the alert. This can for example be a recipient of an e-mail or text message.
You should also record the alert category for SLA violations in the SAP Telecommunications Customizing settings in the Assign Alert Categories to Telecommunications-Specific Usage Types activity (table ISTNLMALERTCA).
Features
If you want to use the alert function for SLA violations, you should schedule the report periodically in the background.
You can control whether the system is only to determine the number of orders, or whether it is also to create the alerts. Defining the number of orders, which violate the service level agreements, is primarily intended for test purposes.
You can create user-specific and client-dependent variants for the fields that the system is to display in the list.
If an error occurs during generation of an alert (for instance if the system does not find any recipient for the alert), the program terminates processing with a short dump. You can view the cause of the dump using transaction ST22.
Selection
The following fields can be used to select orders that violate a SLA:
- Order: Specifies the order number of the order to be checked
- Notification: Specifies the notification number which has been created for checking whether an order violates a SLA.
- Work center: Specifies the work center in the order to be checked
- SLA violates from date: Specifies the scheduled end date in the order, from which an alert is to be created for the order if it has not been confirmed.
- SLA violates to date: Specifies the scheduled end date in the order, up to which an alert is to be created for the order if it has not been confirmed.
- SLA violates from time: Specifies the scheduled end time in the order, from which an alert is to be created for the order if it has not been confirmed.
- SLA violates to time: Specifies the scheduled end time in the order, up to which an alert is to be created for the order if it has not been confirmed.
Standard Variants
Output
The system displays a list of all orders for which an alert has been created.
Activities
Example
ABAP Short Reference CPI1466 during Backup
This documentation is copyright by SAP AG.
Length: 4162 Date: 20240531 Time: 233723 sap01-206 ( 101 ms )
