REX: Sending Alerts from Backend System
Program Report for Sending Alerts from Backend System:
In transaction code SE38, execute the report /MAC/RSFM_ALERT_GEN (shown in the
following diagram). Refer to the administrator’s guide for SAP Retail Execution for detailed documentation of
Important Notes for the alerts report:
Priority: Rex maps the alert priority (for example, High, Very High) with a priority ID and sends the priority ID to SMP. However,
the priority of alert is not displayed in the device.
Category: Two category types of alerts (namely Emergency and Info), are supported for Retail Execution. Rex sends the category ID to SMP.
Validity Period: Note that validity period should always be set for a future date. Though alerts with a past validity date will be displayed in the device, from a business perspective, the validity period should always be set for a future date.
Territory: If a territory is specified in the report, the alerts will be sent to all the business partners in the territory. Therefore, all device users who are ‘Employee Responsible’ for these business partners will see the alerts in their device.
It is also possible to restrict alerts based on a combination of territory and user where the alerts can be sent only to a specific user and not all users in the territory.
Customer Hierarchy: If a customer hierarchy is specified in the report, the alerts will be sent to all business partners that are assigned to the customer hierarchy node. In this case again, all users who are ‘Employee Responsible’ for the Customers will receive the alerts in their device. It is also possible to restrict alerts to a specific user by specifying a combination of customer hierarchy and user.
Target Group: For a specified target group, alerts will be sent to all business partners in that target group. All users who are ‘Employee Responsible’ for the customers in the target group will receive the alerts in their device. It is possible to restrict alerts to a specific user by specifying a combination of target group and user.
Display of Alerts in Device
All alerts will be displayed in the ‘Alerts’ section in the device. The business partner name and ID is displayed against each alert. If more than one
business partner is associated, the list of business partner name and ID’s will be displayed.
In the device, for Customer, alerts are also displayed in the alerts section for ‘Customer’. Therefore, whenever a user performs a sync, the alerts for a customer will be displayed in the Alerts section (along with BP name and ID) as well as in the Customer alerts.
Settings in SMP
The following settings must be maintained in SAP Mobile Platform.
Note: Synchronization cache clean-up is required to remove from the device, all the alerts whose validity period has expired.
1. Enable ‘Synchronization cache cleanup’ in SMP (as shown in the following diagram)
2. In the alert sync group in SMP, maintain the duration for cache interval. This will determine when the alert must be pushed from SMP to the device.
Result: You can now receive alerts from the backend system.
After maintaining the settings in SMP, if you still see issues in sending push alerts to the device, then you must verify the values maintained in the push alert report. For example, check Customizing for sales org, territory or if the device user does exist in the sales organization.
Error: No relevant data found for selection
Reason : This message appears in the backend while running the alerts report if the user is not assigned to a valid sales organization.