Ansicht
Dokumentation

CRM_MKTCCM_NOTIF - BAdI: Partner Campaign Notification

RFUMSV00 - Advance Return for Tax on Sales/Purchases   CPI1466 during Backup  
This documentation is copyright by SAP AG.

At any time during a collaborative campaign you can send notifications to partners involved in the campaign from the Partner List Overview assignment block. When doing so, you do not select the recipients of the notification by name but by status. For example, you can send a notification to all partners who have declined to participate in the campaign or whose enrollment has been placed on hold.

By specifying a mail form, you can control a number of options, for example the communication medium used to send the notification (e-mail, fax, or SMS). For changes that exceed the capabilities of the mail form, you can use this business add-in (BAdI).

This BAdI is called before each notification is processed so you can easily personalize your notifications as required.

There is no standard implementation for this BAdI.

All methods (with the exception of the method BEFORE_ALERT) apply to UI-based as well as event-based notifications. The following methods are available:

GET_RECEIVER

With this method you can override the determination of the recipient of the notification and the communication medium (e-mail, fax, SMS).

By default, the system determines the recipient of the notification from the partner campaign (campaign type PCPG). The determination takes place using the partner function in the partner profile and the partner determination procedure Partner Campaign (CCM_PCPG).

By default, the system uses the following logic to determine the recipient of the notification (partner determination):

1. Partner function with the partner function category 0049 Mail Recipient TO

In the standard delivery, this is the partner function 804 Mail Recipient TO.

You can find the definition of the partner functions in Customizing for Customer Relationship Management under Basic Functions-> Partner Processing -> Define Partner Functions.

1. Employee Responsible at Partner from the header data of the partner campaign
2. Main contact person at partner

The main contact person is listed in the Standard column in the Contactsassignment block in the corporate account of the partner.

In the standard delivery, the system determines the communication medium for the notification using the mail form you specify when sending the notification.

GET_SENDER

With this method you can override the sender of the notification.

In the standard delivery, the system enters the Employee Responsible (at the brand owner) from the header data of the campaign.

GET_REPLY_TO

With this method you can determine a person and the e-mail address to which the recipient of the notification can respond. This is only possible for the communication medium e-mail.

In the standard delivery, the system does not enter an e-mail address for replies to notifications.

FILL_CONTEXT

If you have defined your own fields in your mail form, you can fill these fields using this method.

BEFORE_SEND

With this method you can automatically add information to or change notifications after they have been generated but before they are sent. The following changes could be made, for example:

• The partners in a particular region receive a special attachment

• The partners in a particular region see a special picture in the notification

• The URL specified is changed for partners in a particular region

BEFORE_LOGGIN

In the standard delivery, the notifications are sent with the help of activities of the transaction type Outgoing E-Mail(0005). With this method you can specify additional information for the activities, for example a different transaction type, a different activity category, or additional activity partners.

If you do not require the activities to be logged, you can prevent the creation of activities by filling the parameter EV_SKIP_LOGGING with the value "X".

BEFORE_ALERT

This method is only relevant for event-based notifications.

If an event-based notification is triggered and the processing fails - for example, because the system cannot determine an e-mail address - you can use the alert category Campaign Notification Errors(CRM_CAMPAIGN_NOTIF_ERROR) to trigger an alert and send it to the employee responsible for the campaign.

With this method, you can influence how the alert is triggered and, for example, change the following data in advance:

• Recipient of the alert

• Priority of the alert, for example, sending as express mail

• Text change with additional variables

For more information about the alert category Campaign Notification Errors (CRM_CAMPAIGN_NOTIF_ERROR), see Customizing of Customer Relationship Management under Basic Functions-> Alert Management-> Define Alert Categories.

There is no standard implementation for this BAdI.

rdisp/max_wprun_time - Maximum work process run time   General Data in Customer Master  
This documentation is copyright by SAP AG.

Length: 6125 Date: 20240523 Time: 154510     sap01-206 ( 93 ms )