Notification System - Features

Feature list

  • Send SMS/Email notifications, alerts from SAP
  • Send SMS and email from SAP systemsSend reports, queries and forms in PDF or Excel format as email attachments
  • Broad integration (Workflow, CCMS, BI, SapOffice)
  • Simple content management wizard
  • Handling of incoming messages, send notifications as a response
  • Flexible error handling and logging
  • Easy implenentation
  • Additional communication channels (fax, SAPOffice), can be customer defined
  • Attaching SAP Shortcuts to emails

 

 How does it work?

Only a few steps are required to create a notification. First the text of the notification has to be defined, in which the user can place any number of placeholders. The second step is to define the data source of the placeholders, which will be filled when constructing the notification. There are three options for this:

  • Actual values of a data container: so called data containers can be defined (like "amount" or "exchange rate"), which supply the value to be placed in the notification at the time of construction of the notification. Data has to be collected into a table which is the taskof the customer. This central table will be used to supply the data for the notifications.
  • Function Module: the function module defined for the placeholder will be executed and that will supply the data to replace the placeholder in the notification.
  • Runtime information: like current date and time, user name or system identifier.

Optionally the user can define what should happen if not all data is available.

  • The notification should be sent partially filled (missing data can be substituted with any text like "N/A", "None" or "-")
  • The notification should not be sent
  • An error message should be sent (freely defined text)

The last step of creating a notificaion is to define the list of recipients and define which communication channels should be used (SMS/Email etc.). This is tightly integrated with SAPOffice which is part of the Netweaver platform, so it’s included in every SAP system. Standard distribution lists and SAPOffice recipients can be assigned to the notification.

It is possible to send SMS messages either by using a webservice or an email2sms gateway. Fax messages can be also sent with an email2fax gateway, or notifications can be sent to SAP users (to the SAP Business Workplace).

Multiple files can be attached to emails. Results of reports, SAP Queries or form printouts (Sapscript, SmartForm or Adobe Form) can be attached as PDF or Excel files. Even the job log of a previous job can be attached, which makes troubleshooting quicker. All the attachments can be compressed to reduce network traffic.

When the notification is complete, it has to be scheduled, which has many options:

  • Job scheduling (SM36): one special report has to be scheduled with the identifier of the notification as parameter. This makes scheduling a notification periodically very easy. It is possible to make the job dependant on previous jobs, so it is easy to create alerts on failed jobs.
  • Sending from ABAP code: it’s easy to send a notification from a user exit. This is a very simple way to send notifications when certain business events happen (for ex.. an order is placed, goods are received, maintenance order is created etc..). The same can be implemented in any report. Programmers don’t have to program this manually, since only one function module call is needed to send a notification.
  • CCMS alert: the Hovitaga Notification System can be easily connected to the standard SAP monitoring tool (CCMS). Any CCMS event can trigger sending a notification. For example the IT staff can be notified if a resource is low (disk, memory etc.) or a job has aborted. If connectied with CCMS BI monitors, notifications can be sent if a BI process chain fails or if a certain KPI falls below a limit.
  • Business Object event: simply assign a notification to an event of a business object to notify the people responsible. An example could be if a high-value order (business object) is cancelled (event).
  • Workflow: any workflow step can trigger a notification, like an approval step . One advantage compared to the built in email sending feture of workflow is that the notification contents can be dynamic
  • Response to an incoming message: users can send emails (or sms in case of using an sms2email gateway) to a specified address (or number) containing the notification identifier and the system will send the notification back as a reply. This way it’s easy to request data from SAP systems in an ad-hoc manner.
See Hovitaga's facebook page See Hovitaga's youtube channel