Note 176492 – Automatic email when an alert occurs (RZ20)

Note 176492 – Automatic email when an alert occurs (RZ20)
Reason and Prerequisites

The CCMS monitor architecture (transaction RZ20) allows you to define auto-reaction methods (reports, function modules) that are executed automatically when alerts occur.
As of R/3 Release 4.6A, technical basic requirements have been provided for sending SAPOffice documents from CCMS monitor architecture. As of this release, a predefined CCMS_OnAlert_Email auto-reaction method has also been delivered. Consequently, when an alert occurs, emails with alert information are automatically sent from a SAP system (called C11 below) to

1. a SAPoffice user in client 000 in the same system.
2. a SAPoffice user of another client or another system.
3. a shared distribution list or an external mail address.

Constraints:

– The method dispatcher is automatically executed every 5 minutes (rdisp/autoabaptime is 300) on each application server for short, automatic methods of the monitor architecture to be executed. This dispatcher is processed under the SAPSYS system login name in client 000.
Therefore, the sender of the alert documents must always be a dialog user in client 000.
Users who are defined in different clients of the R/3 System cannot be used ‘directly’ as recipients in SAPoffice they are considered to be external recipients (see examples).

– The time stamps in the mail are specified as UTC time and partially as system time of the system where the alert occurred. The time stamp can also be converted into a specified time zone (described in note 511697).

– The mail document is created between 0 and 5 minutes after an alert has occurred, however, depending on the SAPconnect setting, there may be a delay in the document actually being sent to external addresses (that is, addresses that are not in the client or system). Configure the SAPConnect send process accordingly (see the SAPconnect documentation for more information).

Solution

To ensure that emails can be sent from the Alert Monitor, you must carry out the following configuration steps.
IN THE SYSTEM WHERE THE ALERT OCCURS (C11):

1. 4.6A ONLY: Due to a program error, the RECIPIENT-TYPEID is always set to <> or ‘B’ in Release 4.6A. This has been corrected in the attached Support Package. In addition, the SALO_EMAIL_IN_CASE_OF_ALERT module must be changed in accordance with the attached correction instructions. The 4.6A Support Package alone is not sufficient.
AS OF 4.6B:
To ensure that the SALO_EMAIL_IN_CASE_OF_ALERT module works correctly, the Support Package specified below must be active for the corresponding release in the C11 system. As an ALTERNATIVE, however, you can also implement the correction instructions.
2. In RZ21-> Method definitions, you must set the parameters for the CCMS_OnAlert_Email method.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Use a valid user name in client 0 in the following examples for . Do not specify a system ID or client.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Example 1:
Parameter name Parameter value
1. SENDER (in client 000)
2. RECIPIENT OPERATOR1 (in client 000)
3. RECIPIENT-TYPEID B
4. TIME_ZONE

Example 2:
Parameter name Parameter value
1. SENDER (in client 000)
2. RECIPIENT ABC:007:OPERATOR1
3. RECIPIENT-TYPEID R
4. TIME_ZONE

Example 3:
Parameter name Parameter value
1. SENDER (in client 000)
2. RECIPIENT DistributionListIn000
3. RECIPIENT-TYPEID C
4. TIME_ZONE

where DistributionListIn000 is a shared distribution list in client 000 (important: The SAPSYS can only find the distribute list here) which, in turn, can contain any number of ‘remote address’ entries.

A distribution list also has the advantage of enabling you to select attributes such as ‘express’, for example, for each recipient. Moreover, pagers and so on can be addressed.
Example 4:
Parameter name Parameter value
1. SENDER (in client 000)
2. RECIPIENT
3. RECIPIENT-TYPEID U
4. TIME_ZONE

Note: If you want to define different recipients for different alerts, you should copy the complete method definition from CCMS_OnAlert_Email to RZ21. Parameters are then assigned to the new method in transaction RZ21 -> Method definitions and assigned to the appropriate node in the alert tree.
———————————————————————–
SAPConnect must be configured in C11 in such a way that mails can be sent to other clients, R/3 Systems or to an Internet mail address if these types of users are meant to be the recipients of the alert mails.
If SAPConnect is not yet configured in your system, you need to carry out the following steps in the C11 system:

3. For the SENDER user entered in RZ21, ( in the examples above), in transaction SU01 you must enter aRML address under ‘Other communication…’.
If you want to send mails to an Internet address, you must enter an Internet address in SU01.
4. In transaction SM59, you must configure an RFC connection from the source system (C11) to the target client/target system of the user who is meant to receive the mail. Make sure that you are logged on to the 000 client when you are creating this destination.
With Internet mails, you must define a TCP/IP destination for the computer, on which the SAP Internet Mail Gateway is installed.
5. C11: In transaction SCOT, you must create RML nodes (mail in other clients/other R/3 System) or INT nodes (mail to Internet address).
Make sure that you are logged on to the 000 client when you are creating nodes in transaction SCOT.
6. Schedule a send process (report RSCONN01) as a periodic background job in the target client or target system.
(SCOT -> View -> Jobs).
7. You must create a CPIC user with a S_A.SCON profile in the target client/target system. This is required for the SAPConnect communication.
The SAPConnect documentation contains more detailed information about these points.
Refer to note 511697 for information on how to specify your own time zone for the auto-reaction method.

More from SAPBC.RU

Your Message To SAP Basis Expert

Leave Reply
Your email address will not be published.