Customizing merge process

[rafa_pyxis]

Hi everybody.

I would like to implement some custom login with ABAP Code to customize SAP Marketing merging process when a contact is imported.

Days ago I asked SAP Support about that. We would like to implement this algorithm for example:

if new_contact.origin == 'CONSULTANT_*' and

already_exists_contact(new_contact.originID, new_contact.email, new_contact.mobile)

//this function already_exists_contact searches if exists a contact with origin 'CONSULTANT_*',

//the same originID and (the same email or mobile number) as the contact which is being imported

contacts = get_already_existent_contacts(new_contact.originID, new_contact.email, new_contact.mobile)

make_merge_between_all_those_contacts(new_contact, contacts)
else
create_new_contact(new_contact)
endif

SAP support answer was:

Cause

This is more a consulting query to judge if particular case can be achieved.

In this "Merge interaction contact" badi, the Changing Parameters IDENTIFIED_DUPLICATE is used to determine contacts to be merged.

If you want to do partly merge, you need to loop the wanted merge candidate keys into this table. Please check the in-app badi document and sample code for more details.

Solution

So your requirement on partly merge can be achieved, and you need to develop custom code to achieve it. Since this is more consulting query, I would like to help however it falls out of the support scope of SAP Product Support. On the other hand, SAP Consulting team can provide you better service on such topics, please reach out to them if needed.

So, please, can somebody help me to implement such custom logic in ABAP code ?

Thanks in advance!

Regards,

Rafa.

From SAP support

[JohannesPfalzgr · Accepted solution]

Hi Rafa,

if I understand your post correctly, you are trying to do the following:

1. You are loading contact information with the ID-origin "Consultant_*", including email address and phone number as additional facets.

2. You send a second data set with a contact having the same Consultant_* ID --> this would result in an update of the golden record per standard behavior, when the ID Origin "Consultant_* is configured as "For Identification = Yes".

3. You send another data set with a contact having a different Consultant_* ID, but same email-address or mobile number as the already existing contact. Now you want to make sure that the contacts are merged. --> This can be achieved by configuring both the ID-origins "Email" and "Mobile" as "Additional Origins" and setting them as "For Identification = Yes".

For more details please see the following Help - Moving Origins and CX Works article on Match & Merge

Best regards,

Johannes