Kontakt

Ansicht
Dokumentation

CRM_MKT_MODIFY_ORDER - BAdI: Enhanced Creation of Business Transactions

CRM_MKT_MODIFY_ORDER - BAdI: Enhanced Creation of Business Transactions

General Material Data   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.
SAP E-Book

This Business Add-In (BAdI) permits the modification of business transactions to be created during campaign execution. The default data provided for business transactions is written in internal tables (for example, priorities, partners from determination, short text and so on). These internal tables were previously used directly for generating business transactions. The methods are now switched on before calling up the generation API for business transactions. This means that the tables can be changed in the BAdI methods and this in turn influences the generation of business transactions.

  • To enhance the creation of business transactions Contact/Task, you can implement and activate the method MODIFY_ACTIVITY_OBJ.
  • To enhance the creation of business transaction Lead, you should implement and activate the method MODIFY_LEAD_OBJ.
  • To enhance the creation of business transaction Sales Order, you should implement and activate the method MODIFY_SALES_ORDER_OBJ.
  • You can find more detailed information in the documentation for the methods:

If further context information needs to be read for a campaign or trade promotion, you can use the method PARTNER_ASSIGN_READ from class CL_CRM_MKTPL_APPL_BASE (read assigned partner functions) and the function module MKT_ELEMENT_READ (further context data).

The key for the trade promotion/campaign is contained in the method parameter 'is_project_info-guid' and the key for campaign or trade promotion elements is contained in the parameter 'is_task_info-guid'.

If templates are assigned to the campaign/trade promotion (or their elements), bear in mind that the data in the BAdI method overwrites the corresponding data in the template. First, the template data listed below is copied to the new business process and then the data that was entered in the generation module is copied. It is precisely this data that can be changed in the methods.

The following data is set in the standard and entered in the methods and later in the generation modules. If no changes are made to internal tables in the methods, then the following data is copied to the new business process:

Priority:Always copied from the campaign / trade promotion (or from the elements):

  • Activity (of type contact/task) (a mapping exists here: Prio campaign/trade promotion <-> activity):
  • If priority given by element -> Element priority

  • If priority given by campaign/trade promotion -> Campaign/trade promotion priority

  • If one of the two cases occurs and no mapping is defined in Customizing for priority between marketing object<->activity , then the default priority is copied to the business transaction from the transaction type.

  • If no priority is specified for the element of the higher-level object, and also a template is assigned for execution, the priority is copied from the template.

  • Lead:
  • Priority is not adopted

Activity partner/prospect/contact person: is copied exclusively from the target group or from campaign execution (with partner determination in campaign execution)

  • B2C Scenario: The person is adopted as both the activity partner (or the prospect for LEADS) as well as the contact person
  • B2B Scenario (without partner determination in campaign execution): The organization is entered as the activity partner. The partner determination for business transactions uses the relevant access sequence rules to determine additional partners.
  • B2B Scenario (with partner determination in campaign execution): For every determination the organization is adopted for the activity partner/prospect function and the person is adopted for the contact person.

Employee responsible:

  • If the process started from an element, then the employee responsible for the element is adopted for the corresponding partner function for the business process.
  • If the process started from an element and there is no employee responsible for that element, then the employee responsible for a higher-level object (campaign/trade promotion) is adopted.

Short text:

  • If a template is specified, then the text is adopted from the template. Otherwise, the name of the marketing object is adopted
  • If an element is involved, then the name of the element is adopted. If this is empty, the name of the higher-level object is not used.

Time/date:

  • If templates exist, the assigned times in the templates are used as planned dates for the business process.
  • Otherwise, the times for the element of the higher-level marketing object are used.






ROGBILLS - Synchronize billing plans   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 6062 Date: 20240523 Time: 182851     sap01-206 ( 50 ms )