CL_EXM_IM_CRM_MKT_BP_DETERMINE - Example Implementation for BAdI Definition CRM_MKT_BP_DETE

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

Functionality

In the method DETERMINATION_BY_DEDUP_METHOD, deduplication objects are determined for the business partnerin accordance with the deduplication method chosen by the user (import parameter 'IV_DEDUP_CODE'').Using these objects, duplicates are removed from the segment. The method is called for the deduplication of profiles, target groups, and profile sets.

Business partners can also be replaced with this method. If business partner 'B' should be in the targetgroup instead of business partner 'A', you must set the deletion indicator 'DELETE_FLAG' for businesspartner 'A' to 'X' in the change table CT_BP_LIST. Conversely, you must set the indicator 'ADD_FLAG'to 'X' for business partner 'B'. During the replacement, target group GUID 'TG_GUID' and priority 'PRIORITY' of business partner 'A' are copied to the added business partner 'B'.

If no deduplication method is defined in the segment properties or if there is no active implementation of the defined method, deduplication occurs according to the business partner key (standard delivery).

Relationships

Example

One example of defining deduplication objects is the determination of a household ID for each businesspartner in a target group. This is necessary when each household in a target group should only be contacted once as part of a campaign. The duplicate households are then removed during deduplication.

It can also be necessary to have a replacement process for legal reasons. If the target group containsunder-age business partners that cannot be contacted in the campaign, these business partners can be replaced with the father or head of the household.

Notes

In the CASE statement an error message must be generated in the case of ' WHEN OTHERS', which informs the user that there is no active implementation of the chosen deduplication method (see example implementation).

Performance: In the standard code, the selected method of reading relationship data using the organizationalmodel with business partner APIs is performance-intensive. It is recommended that you use direct table access here.

In the BAdI the deduplication object must be read for each business partner and entered in the field 'DEDUP_OBJECT'. If no deduplication object is determined, the business partner will not be deduplicated.

Exceptions:

  • Explicitly deleted business partners.
  • Added business partners: duplicates are identified by the business partner key 'BP_GUID'.

The business partners added or deleted during deduplication are marked as follows in the target group item list (table CRMD_MKTTG_TG_I):

  1. Deduplication of Target Group
  • Added business partners: BP_ORG = '05'

  • Deleted business partners: BP_ORG = '05' and BP_DEL = 'X'

  1. Deduplication by Profile Set
  • Added business partners: BP_ORG = '06'

  • Deleted business partners: BP_ORG = '06' and BP_DEL = 'X'

Further information



Vendor Master (General Section)   PERFORM Short Reference  
This documentation is copyright by SAP AG.


Length: 3321 Date: 20120526 Time: 121032     triton ( 139 ms )