Create Marketing Permissions for Custom Communication Media via OData

[SCHNEIDERT]

Dear Experts,

when replicating Marketing Permissions from C4C to SAP Marketing Cloud still the OData Service CUAN_IMPORT_SRV is used in CPI by default (really don't know why...).

When we trigger the replication, only the permissions for the standard communication media EMAIL & PHONE are created/updated in SAP Marketing Cloud (for PHONE we first had to add the phone-number to the golden record via BAdI).

We have three custom channel permissions in C4C (Z01 to Z03) which are also mapped in the iFlow to custom communication media of the Marketing Cloud (e.g. Z03 = POST).

But the permissions of those channels are not written/created/changed in SAP Marketing Cloud even if the Payload seems fine. I also tried it manually via Postman and have the same problem there.

https://my123456.s4hana.ondemand.com/sap/opu/odata/sap/CUAN_IMPORT_SRV/ImportHeaders

That's the Body I used for the creation of the E-Mail Permission (as recommended in SAP Help: https://help.sap.com/viewer/0f9408e4921e4ba3bb4a7a1f75f837a7/1905.500/en-US/59602623ea794608982c4a6e...😞

If I replace only EMAIL with a custom communication media (e.g. POST) nothing happens.

When I import the permission via CSV it works as expected.

Does anybody have an idea of what I'm doing wrong? How can I import the permission for my own communication media via that OData Service CUAN_IMPORT_SRV?

mayaboleto any ideas on this?

BR Tobias

[danny_lipkovski2]

Hi Tobias,

I came across your post because we have exactly the same requirement.
We will go for your solution with additional ID.
May i ask which data do you store in the additional ID of the IC? Dou you store C4C-ID in SAP_C4C_BUPA and in the additional Id or do you use any other value? Because I suppose that we need to have an ID for the additional ID.

Regards

Danny

[former_member196553 · Accepted solution]

Hello Tobias,

The design is specific marketing permissions upload via CUAN_IMPORT_SRV with ID origin SAP_C4C_BUPA - for uploading permissions via the SAP_C4C_BUPA ID there is the following design:

During the upload system determines all depending IDs for the "OutboundCommunicationMedium". That means for communication medium EMAIL, system retrieves the depending EMAIL ID for main ID SAP_C4C_BUPA, for communication medium SMS, system retrieves the depending MOBILE ID for main ID SAP_C4C_BUPA.

The communication medium POST has ID origin SAP_C4C_BUPA mapped - the point is that SAP_C4C_BUPA exists as main ID only, but this is not a depending ID. For using CUAN_IMPORT_SRV via ID origin SAP_C4C_BUPA you can update permissions for depending IDs only.

As suggested you can either map any different ID origin to communication medium POST, then the permission upload will still work via CUAN_IMPORT_SRV or alternatively you can use the Public OData API API_MKT_CONTACT for uploading the POST permissions - this will work for ID origin SAP_C4C_BUPA as well.

You will find all required information in the online help.

best regards,

Johannes

[SCHNEIDERT · Accepted solution]

Hi Johannes,

I already thought about the second approach. I think it would be better if the standard iFlow for permission integration would also use that one instead of the CUAN_IMPORT_SRV.

But how can I create an ID Origin as depending one (like for example EMAIL for SAP_C4C_BUPA)? There's nothing in the configuration where I can say that it is a depending one, isn't it?

Best Regards

Tobias

[SCHNEIDERT]

Hello johannes.voglsam,

do you know if it is possible to integrate the newly created communication medium in a Form, so that a contact is able to grant permission for it on a landing page?

I could create a permission field for the new communication medium (in our case Z_POST) but I think a new contact must also fill any input field for it, right?

For existing contacts it also doesn't update the originally Permission for Z_POST that came from C4C.

Any ideas how I can achieve this?

BR Tobias

[mayaboleto]

Hi Tobias,

did you maintain configuration in SAP Marketing Cloud for origin ID and Communication Media.

Please review this image and let me know.

This is required e.g. to say email for Facebook or for Email and this drives marketing permissions in SAP Marketing Cloud.

Best,

Maya

[SCHNEIDERT]

Hi Maya,

thanks for your answer. Yes I did. We solved the problem as proposed by Johannes.

So I created another ID Origin (instead of SAP_C4C_BUPA) and used it for the custom communication medium.

BR Tobias

[Former Member]

Hi Tobias,
if you think that the CUAN_IMPORT_SRV does not behave correctly for your permission payload (which seems the case here), you should open a ticket on CEC-MKT-DM-PER together with a description + the payload you used. best regards, Sophie.

[SCHNEIDERT]

Hi Sophie,

thanks for your answer, I will create a ticket for that and let you know if it helped.

BR Tobias