Defining mailing distribution
Go to AEB Cockpit: Customizing – Mailing distribution.
In the mailing distribution you can determine at which point of time mails shall be sent via a mailing list.
Assignment may be controlled based on the following criteria:
- Product
- Module (can be selected using the F4 help)
- Priority (Critical, Error, Warning, Info, Debug)
- Event
- Organizational unit
An entry is only valid when the fields from left to right are maintained without "gaps".
Example of a completely maintained mailing distribution for Trade Compliance Management:
Product | Module | Priority | Event | Org. unit | Mailing list |
|---|---|---|---|---|---|
CMP |
|
|
|
| Distribution list_1 |
CMP | EC |
|
|
| Distribution list_2 |
CMP | CS | CRITICAL |
|
| Distribution list_3 |
CMP | CS | CRITICAL | CHK |
| Distribution list_4 |
CMP | CS | CRITICAL | VDR_CHK |
| Distribution list_5 |
CMP | CS | CRITICAL | CHK | 1000 | Distribution list_6 |
CMP | CS | CRITICAL | VDR_CHK | 2000 | Distribution list_7 |
Example for an incorrectly maintained mailing distribution:
Product | Module | Priority | Event | Org. unit | Mailing list |
|---|---|---|---|---|---|
| EC |
|
|
| Distribution list_2 |
CMP |
| CRITICAL |
|
| Distribution list_3 |
CMP |
| CRITICAL | CHK |
| Distribution list_4 |
CMP |
|
| VDR_CHK |
| Distribution list_5 |
CMP | CS |
| CHK | 1000 | Distribution list_6 |
CMP | CS |
|
| 2000 | Distribution list_7 |
In the input help (F4) you can find all possible events. The values displayed in the input help are based on the context of the values maintained in the Product, Module and Priority fields. Therefore, the input help can only define values for the Event field if the three fields have been completely maintained for one row.
Notes on configuring the sending of e-mails
The settings for mailing distribution are defined as "Current setting" and can also be changed in production systems.
Mailings are always sent in the communication language that has been entered in the SAP® user of the e-mail recipient.
For sending e-mails, a job must be scheduled that periodically runs the /AEB/01_JE_WORKER program. This job can be scheduled for all products, that is, without using a variant.
Notes on cases in which no e-mails are sent
Independently of the defined settings, no e-mail is generally sent to the SAP® user who triggered an event. This also applies, for example, if the person who created the batch job for a compliance screening wants to be informed of the event by e-mail. In this case, the batch job should be created with a separate batch user.
In the context of the compliance check, no e-mail is sent if the compliance status of the business object has not changed.
Example: A business object already has the compliance status "Critical". If this status remains the same, no e-mail is sent during a new check.
No e-mails are sent for technical errors during a batch check.