Correct setting for "for identification" for EMAIL origin

[vervinckt_joyca]

Hi,

With 1905, the Origin setting "shareable" has been renamed to "for identification".

Instead of just true/false, there are now multiple options:

https://help.sap.com/viewer/ac1eab4c66bc490da7ac2c378c46b0e7/1905.500/en-US/e95d047447dc4f67a5ac2982...

I am wondering about the correct setting for EMAIL in the following case.

It used to be "not shareable".

So you would think the correct setting is then "blank" which means "yes: A source system ID that can be used to identify a potential match, typically because the ID cannot be shared by other contacts." (this is also the current setting after the upgrade, so "not shareable" seems to be translated to "blank" by default.)

However there is also the value "A"

Which means "Yes (Additional ID): An additional ID that is considered a reliable means of identifying an existing matching contact or for triggering a merge."

as EMAIL is mostly an additional ID, I think the correct setting in this case then might be "A" ...

What's the difference in processing between "blank" and "A" in the case of the EMAIL origin?

Kr

Joyca

[nicolae_ciumac]

Hi Joyca,

again, you've got intuitively yourself right 🙂

All these changes are compatible; actually - we can't even change the pre-delivered content in this sense; as you say - it would make sense to set origins like PHONE/MOBILE/EMAIL to "A", but for compatibility reasons they're kept as blank. Only the customers themselves can do such changes.

The logic for the match and merge process is the same for A and blank.

Best regards,

Nico

[nicolae_ciumac]

Hi Joyca,

you have intuitively got it right - in your case, as to my understanding, the Email should be set to For Identification = 'A', since you're using it only as an additional ID and you don't want it to be shared by multiple contacts.

The difference between blank and A is, that blank should be used for origins which act as main identifiers in a given source system (so if you get contact data from a web shop for example, then the origin used for the web shop SAP_HYBRIS_CONSUMER should be set to For Identification = '<blank>').

These changes were made as a preparation for a redesigned app for the configuration activity for defining origins of contact IDs (the app will be released with 1908).

Best regards,

Nico

[vervinckt_joyca]

nicolae.ciumac ,

but currently I don't see any Origin that has the "A" value in the SAP Standard origins, also e.g. Mobile Phone is currently just blank...

IF the EMAIL origin does remain on "blank", does that mean our current match&merge process is going wrong, or is there in 1905 still a "safeguard" mechanism that still handles additional id's like EMAIL with a "blank" value as it would "non-shareable" origins from before? Otherwise there hasn't been enough fuzz an warnings about this change!

Kr

Joyca

[maik_bosch]

Very good question 🙂

Indeed it would be nice to see updates of the following blogs:

https://blogs.sap.com/2016/08/26/contacts-in-sap-hybris-marketing-understanding-the-concept-of-golde...

https://blogs.sap.com/2016/10/17/main-id-origin-customizing-settings-contacts-sap-s4hana-marketing-s...

[Former Member]

Hi shounak.deshpande , can you take this one? Thanks, Anton