Duplication of contacts between C4C and CSV in MKT

[former_member654580]

Hello experts

Currently I have an integration between C4C and MKT, the system brings the contacts with the Origin ID (SAP_C4C_BUPA) .that are identified with the ID of that source system (C4C)

On the other hand, the same contacts are uploaded to MKT but with a number of new attributes to be used in the segmentation but with a different Origin ID than the identifier in C4C, but they are the same contacts already intertwined between MKT and C4C.

In conclusion, the contacts are doubled.

In the Origin ID SAP C4C configuration: Business partner was marked as One by Contact.

In the upload file in the ID column the contact carries a different identifier than the one brought in by that contact from C4C, but in that Excel CSV file in another column the contact has the ID that it has in C4C.

As in MKT it is configured that the contact that is being loaded is the same one that already arrives via integration from C4C?

the ID_Origin used in the upload file is: SAP_HYBRIS_CONSUMER.

Thanks Elio C

[JoycaVervinckt · Accepted solution]

Hi eliocentenob

A random custom field in a csv file, is not recognized as an "Origin" (aka Facet) for identification.

A custom field could also just be "shoe size" which is completely irrelevant for identification.

To make SAP Marketing Cloud understand that a specific custom field should be considered for identification, you can use Custom Logic "Review Imported Interaction Contact Data".

There is example code on this custom logic:

*    Example to add a facet with the consumer account ID
    DATA ls_add_facet LIKE LINE OF additional_facet.
    IF contact_data-consumer_account_id IS NOT INITIAL.
      ls_add_facet-id        = contact_data-consumer_account_id.
      ls_add_facet-id_origin = 'Z_CONS_ACC_ID'. " in SAP Marketing configuration you would create Z_CONS_ACC_ID as an own 'Origin of ID'.
      APPEND ls_add_facet TO additional_facet.
    ENDIF.

just replace contact_data-consumer_account_id with contact_data-yy1_yourcustomfieldname_xxx

and Z_CONS_ACC_ID with the origin that you want to use, SAP_C4C_BUPA.

Then the content of that custom field, will be taken over into an origin+id and matching can be done based on that.

Kr,

Joyca

[former_member654580]

Hello Joyca

Thank you for your response

About your questions:

"The one on the right is the one uploaded by csv, right?"

-Correct.

"But, on the right (csv) contact you should already see the C4C origin appearing, if your code was written (and published) correctly."

- Yes, the code was published successfully.

Continued to work on the subject, cordially Elio

[JoycaVervinckt]

Hi, I see in your screenshot that you missed this part from my instructions:

just replace contact_data-consumer_account_id with contact_data-yy1_yourcustomfieldname_xxx

So both in the part "if (field) is not initial"

as in "ls_add_facet-id = (field)"

you need to put in (field) the name of the field that you use in your csv file. Should start with yy1_something, it wasn't on your screenshot completely. YY1_IDCUENTADECONT...

[former_member654580]

Hello vervinckt.joyca

I hope you are well!

I applied a new custom logic, following your valuable support.

I think it's going a long way.

As an example of a Liz contact case, before there was one for each data source ID.

Now only two, one for the data source from C4C and one that groups all the ones I have uploaded by CSV.

I will continue to review, if you answer my comments, perfect, otherwise grateful and well taken care of by you.

And I will gladly click on Accept for your answer, just schneidert your suggestion I take into account.

[JoycaVervinckt]

Hi Elio,

Where did that third origin for SAP ERP suddenly come from?

The one on the right is the one uploaded by csv, right?

Normally, if the custom logic was written correctly, the csv contact should get a SAP_C4C_BUPA ID added in the cloud of origins.

The Merge process is separated from the upload process, so it can take a few minutes before the merge job runs and combines the left and the right contact together.

But, on the right (csv) contact you should already see the C4C origin appearing, if your code was written (and published) correctly.

PS, did you already see these video's? https://youtu.be/3tQbup_oqyM and https://youtu.be/-bJWb9D_Ce8

Kr

Joyca

[former_member654580]

Thanks Tobias and Joyca for your help

Your vervinckt.joyca answer seems interesting to me, but I can't find that application or option in the settings (Imported interaction contact data), what is the route?

Thanks

Elio C.

[JoycaVervinckt]

In the Extensibility group, you should find the Custom Fields and Logic app.

The third tab in that app is for Custom Logic.

See also https://help.sap.com/viewer/13d84c47bb6749a188fd53915c256516/latest/en-US/988eb12f5ff74b1e941fd6476a...

[SCHNEIDERT]

Hi eliocentenob ,

which "configuration" are you talking about?

You have to configure SAP Marketing Cloud by creating the communication arrangements and also have to configure CPI and deploy the integration package. Then you can configure CPI to "fetch" the data from an SFTP server for example. So it also works if you need to upload data more than once.

BR Tobias

[former_member654580]

Hello schneidert

It would be great if it were for CPI, but it plays obliged by CSV.

I'm going to check your file-based data load link

A question, this new configuration would have to be done from CPI?

Another doubt, that CSV load is to be done many times a year, not once, does it apply in this way?

Best regards

Elio C.

[SCHNEIDERT]

Hi Elio,

is it necessary to import the csv file manually? Or would it also be possible for you to use OData?

e.g. in the OData Service CUAN_BUSINESS_PARTNER_IMPORT_SRV you have the fields MATCH_ID_ORIGIN and MATCH_ID which I think you could use for your purpose.

So maybe the file-based data load using CPI is an option.

BR Tobias