Standard email notifications

ActiveControl can be configured to send automated e-mails notifications to relevant stakeholders in numerous scenarios, such as:

• Notify approvers when changes are waiting to be approved (provided the changes are associated with one or more tasks).
• Notify team members that their changes have been imported successfully or with errors. It is possible to additionally notify administrators when a transport is imported with errors.
• In the case of branched development systems, notify team members if their changes should not be imported because of conflicts with changes already made in the project development system.
• Notify team members when changes are waiting to be tested by them (provided that the changes are associated with one or more tasks).
• Notify administrators when a serious error occurs that prevents changes from being imported or an import error occurs. Non administrator users can also be informed of these issues for specific transport paths by maintaining entries in table /BTI/TE_NOTIFUSR.

A matrix of all of the Standard email notifications, along with a description of their purpose and audience is available in this online FAQ article.

In order to send e-mail notifications, report /BTI/TE_RNOTIFICATION_ENGINE must be scheduled to run periodically in the ActiveControl domain controller. This report allows you to filter those target SAP systems that various types of notifications should be sent for, as sometimes you may not want each type of notification to be sent for each target SAP system.

Standard RSCONN01 program must also be running within the ActiveControl Domain Controller for the emails to be sent.

ActiveControl provides out-of-the-box HTML templates for each of the standard email notifications. These are stored in the Web Repository (transaction SMW0), for each type of notification. These templates can be copied and adapted if desired.

Before sending a notification e-mail, ActiveControl attempts to determine the recipient’s Internet e-mail address from their SAP user ID. If an Internet address is not specified then the e-mail is sent to the SAP user ID and must be viewed using the SAPoffice Business Workplace (transaction SBWP).

In order to send e-mails to Internet e-mail addresses, a connection to an external e-mail server must have been configured for the ActiveControl domain controller. In systems running on SAP’s Web Application Server 6.20 and higher, this is easily done using SAPconnect’s built-in SMTP connection.

*Email notifications where an action is required include an URL link to the Web UI. For Single Sign-On (SSO), please configure main.html instead of index.html at the end of the Web UI HTML Path parameter in /BTI/TE_RNOTIFICATION_ENGINE, this will bypass the login screen and use the current user logon ticket instead.

*To mark certain users to not receive any email notifications they can be maintained in table /BTI/TE_EMAILIGN. These users can then be excluded via user exit 0510 and removed from the list of recipients.