What MKT field is used to store permissions, C4C-MKT integration

[former_member654580]

Hello Experts

Currently, you want to bring the permissions (Habeas Data) by means of SCPI from C4C .

In C4C they configured some fields to capture the permissions

S-Yes,

N=NO,

and P=Pending.

My question is which field in MKT would that permit be stored to?

Considering that in MKT you must have permissions for Email,phone, Etc.

And so it was set to C4C the P option does not apply to MKT, I understand.

Marketing Permission Settings are configured In and Out and contact ID sources were assigned to media.

Thanks

Elio C

Image C4C

Image MKT

[SCHNEIDERT · Accepted solution]

Hi eliocentenob,

by default actually CPI still uses the CUAN_IMPORT_SRV for replicating Marketing Permissions from C4C to SAP Marketing Cloud.

Here the values S, N, P (which have the code 1, 2, 3) are mapped to the Opt-In field (by default 1 = Y, 2 = N, 3 = N).

The CommunicationMediumTypeCodes in C4C (TEL, INT, ...) are mapped to the OutboundCommunicationMedium in Marketing Cloud (PHONE, EMAIL, ....).

I think/hope the CUAN_IMPORT_SRV will be replaced in 2005 or 2008 release because of its deprecation.

Hope that helps.

BR Tobias

[former_member226]

Hi,

You can use communication arrangment SAP_COM_0003 and SAP_COM_0004 to configure communication user setting.

BR
Saurabh

[SCHNEIDERT]

Hi,

SAP_COM_0082 which is used for Commerce Integration is also possible.

But I would prefer one of the two which Saurabh already mentioned.

BR Tobias

[former_member654580]

Thank you Tobias and Saurabh.

I understand that a communication agreement must be activated to integrate permissions between C4C and MKT.

What communication agreement should be activated for bringing permissions to MKT?

Thanks

[former_member226]

To further add to what Tobias has already mentioned, SAP already provides a standard iflow "Replicate Marketing Permission to SAP Marketing" which takes care of everything for you from mapping point of view. You just need to configure iflow endpoints and thats all!