Ansicht
Dokumentation
CRM_MKTHV_EXE_OUTBND - BAdI: Define Outbounds for High-Volume Campaign Execution
SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3upThis documentation is copyright by SAP AG.
This Business Add-In allows you to manipulate the result of high-volume campaign execution at different times of execution. You do this to, for example, define the output of the files that you send to a letter shop.
You can define different BAdI implementations for different combinations of communication medium - communication method using the following filters:
- COMM_METHOD,,Communication Method
- COMM_CHANNEL,,Communication Medium
Refer to Define Communication Medium in order to get the possible values for the filters.
Note: You can choose an empty COMM_CHANNEL filter for communication medium-independent implementations.
The BAdI contains the following methods:
- GET_PROJECT_PATH: This method is called from the execution infrastructure after reading the logical path from Customizing. Here the customer can change the logical path and/or the directory which will be created according to his business process. The logical path must be customized in transaction FILE and has the following parameters:
Parameter | Associated Type | Description |
---|---|---|
IV_TASK_GUID | CRM_MKTHV_TASK_GUID | High-Volume Campaign Parallel Task GUID |
IR_PROPERTIES | CL_CRM_MKTHV_JOB_PROPERTIES | High-Volume Campaign Job Properties |
CV_LOGICAL_PATH | PATHINTERN | Logical path name |
CV_DIRECTORY | STRING | Directory name |
- START: Stores the (optional) binary data and the XML files for control and for the marketing project in the project directory. The method has the following parameters:
Parameter | Associated Type | Description |
---|---|---|
IV_TASK_GUID | CRM_MKTHV_TASK_GUID | High-Volume Campaign Parallel Task GUID |
IR_PROPERTIES | CL_CRM_MKTHV_JOB_PROPERTIES | High-Volume Campaign Job Properties |
- PACKAGE_COMPLETE:This method is called after a core execution task has been finished. As soon as it is called, the contact information is available for this certain package. For the high-volume e-mail campaign the package can immediately be processed from the e-mail generator tool. For the high-volume letter campaign the package is copied to the project directory which was created in method start().The method has the following parameters:
Parameter | Associated Type | Description |
---|---|---|
IV_TASK_GUID | CRM_MKTHV_TASK_GUID | High-Volume Campaign Parallel Task GUID |
IR_PROPERTIES | CL_CRM_MKTHV_JOB_PROPERTIES | High-Volume Campaign Job Properties |
- COMPLETE: This method is called after all packages are processed from core execution to enable the customer to do some final tasks. It is not relevant for the two implementations that will be delivered. The method has the following parameters:
Parameter | Associated Type | Description |
---|---|---|
IV_TASK_GUID | CRM_MKTHV_TASK_GUID | High-Volume Campaign Parallel Task GUID |
IR_PROPERTIES | CL_CRM_MKTHV_JOB_PROPERTIES | High-Volume Campaign Job Properties |
All methods have the following exceptions:
- CX_CRM_MKTHV_EXE_TASK_FAILS
- CX_CRM_MKTHV_EXE_PROC_FAILS
There are two default implementations delivered:
- CRM_MKTHV_EXE_OUTBOUND_EMAIL: To enable issue of output for a high-volume e-mail campaign, the csv files created by core execution can be handled by the e-mail generator separately. See documentation of implementation for further details.
- CRM_MKTHV_EXE_OUTBOUND_FEC: To enable processing of output for a high-volume letter campaign, the csv files created by core execution will be stored in a consolidated folder, the project folder. See documentation of implementation for further details.
PERFORM Short Reference ROGBILLS - Synchronize billing plans
This documentation is copyright by SAP AG.
Length: 5983 Date: 20240523 Time: 160903 sap01-206 ( 70 ms )