Skip to Content

Use case of unique/shareable container

Dear Colleagues,

Studying Data Management Implementation of Hybris Marketing, I am not so clear about facet container concepts. I can see overall process of creating unique/shareable containers, but the purpose of creating a container is not clear. Also, I cannot understand the notations (e.g. * ,1 , 2) used in the diagrams of the attached images. In the shareable container example, why IA is assigned to IC*(shareable container) with dotted line?

To sum up, I need your answers for the following questions:

- What's the meaning of the notations in the attached diagrams?

- What's the meaning of the dotted line with which IA is assigned to IC*?

- What's the use case of creating unique/ shareable containers? Why do we need to save the obsolete data (e.g. Two different contacts are created with the same ID which is unchecked for shareable facet field, so it cannot be shared nor matched to neither of the Interaction Contacts) by creating a container instead of getting rid of it?

Thank you,

Dara Hea

unique-facet-container-example.jpgshareable-facet-container-example.jpg

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • May 24, 2017 at 11:11 AM

    Hi,

    Have you read this blog?

    I think the images in it correspond with the images you have posted, but more detailed.

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

    Anyway take care when using the terms "facet" and "container". Related to that, this blog is also a good read: https://blogs.sap.com/2016/08/26/contacts-in-sap-hybris-marketing-understanding-the-concept-of-golden-records/#

    A facet is related to your contact and is used to identify and match/merge information to your contact.

    A container is something else, I can't correctly explain it myself but it's a sort of technical solution for when two contacts should be merged based on a matching facet, but cannot be merged due to another facet that is set as "only one per contact" and would receive a second one due to the merge. In any case, since version 1702 this behavior has been changed, it is explained in the first blog I mentioned. Now instead of creating this container contact, an exception is made to your settings of shareable/one-per-contact settings. Anyway the blog explains is way better :)

    I'm glad 1702 provided this update as I was having some issues with container contacts being created; and honestly I didn't understand why this was done; the new update seems more logical to me.

    Kr,

    Joyca

    Add comment
    10|10000 characters needed characters exceeded

  • May 24, 2017 at 01:27 PM

    As of release 1702, the logic for creating containers has been simplified a lot.

    A container is only created, if a certain interaction cannot be assigned to a given contact (except those interactions which are not associated with a contact at all, like clicks on a web-site identified by an IP address only). So for example, if the id used for interaction is too vague and there are two or more contacts that could be involved, and there's no additional logic to decide which contact exactly should be considered, then a container is created.

    Add comment
    10|10000 characters needed characters exceeded

  • May 27, 2017 at 01:28 PM

    Hi Dara,

    At my first reading, this topic sounded really complicated to me, too. However, after you get the hold of terms "Facet", "Origin ID" etc and ponder on the use cases one by one, it begins to be more clearer and comprehensive. So I suggest you to evaluate the use cases one by one considering how the origin ID's are customized (especially the two important check boxes: One per contact and Shareable)

    • One per contact: This is checked for the main facets. This means an interaction contact cannot have more than one facet with this origin ID. Examples: SAP CRM, SAP ERP, Web Shop etc And of course this is not checked for additional facets where interaction contacts can have more than one facet with this origin ID. Examples: Mobile number, E-mail etc.
    • Shareable: This is checked for the facets whose ID's can be shared among several interaction contacts. Examples: E-mail phone number, fax number etc. And of course this is not checked for the facets whose ID's have to belong to only one interaction contact. Examples: Mobile number, social network account.

    The screenshots you have shared are taken from SAP Hybris Marketing Data Management EKT document. I think the explanations are already well said in that presentation, but to be more precise, I can elaborate those use cases like below:

    Unique Facet Container

    - Customizing

    In the customizing, both origin ID's SAP_CRM_BUPA and MOBILE are marked as "non-shareable" (meaning Shareable is not checked). One per contact for SAP_CRM_BUPA is checked (meaning an interaction contact can only have one business partner number) and One per contact for MOBILE is not checked (meaning an interaction contact can have more than one mobile numbers as long as they're not shared by another interaction contact)

    - Use Case

    Interaction contact IC2 holds main facet A2 (SAP_CRM_BUPA) whose ID is 123 and IC2 also holds an additional facet C (MOBILE) whose ID is +905211117767.

    There's an interaction contact being imported to Hybris Marketing. And this interaction contact holds main facet A1 (SAP_CRM_BUPA) whose ID 324 and this interaction contact also holds an additional facet C (MOBILE) whose ID is +905211117767

    - Result

    Definitely there will be two interaction contacts since they have different SAP_CRM_BUPA ID's (123 and 324). However, since mobile number is the same (+905211117767), they won't have this mobile number as it's configured as unique in the customizing. Hence a container is created holding this mobile number

    Sharable Facet Container

    - Customizing

    In the customizing, the origin ID SAP_ERP_BUPA is marked as "non-shareable" (meaning Shareable is not checked) and One per contact is checked (meaning an interaction contact can only have one ERP customer number)

    The origin ID EMAIL is marked as "Shareable" (meaning Shareable is checked) and One per contact is not checked (meaning an interaction contact can have more than one e-mail addresses).

    - Use Case

    Interaction contact IC1 holds main facet A1 (SAP_ERP_BUPA) whose ID is 10000876 and IC1 also holds an additional facet B (EMAIL) whose ID is abc@hotmail.com Interaction contact IC2 holds main facet A2 (SAP_ERP_BUPA) whose ID is 20000123 and IC2 holds an additional facet B (EMAIL) whose ID is abc@hotmail.com.

    Note that e-mail address is the same and this is possible as EMAIL is marked as shareable in the customizing.

    An interaction is coming with origin ID EMAIL and its ID is abc@hotmail.com.

    - Result

    The interaction cannot decide which contact it should be assigned to because they both hold same EMAIL facets whose ID is abc@hotmail.com. Hence a container with the same e-mail address is created along with this interaction.

    I hope this helps

    Best Regards,

    Add comment
    10|10000 characters needed characters exceeded

    • thank you for your detailed explanation! it helped me a lot to understand the EKT document, especially the images I attached here! thank you again and have a nice day :)