cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Segmentation based on Account Team

danny_lipkovski2
Participant
0 Likes
1,609

Hi,

in SAP Marketing Cloud we have the requirement to create segments based on the Account Team members of coreporate accounts.
We will replicate account team from C4C.
It is possible to include Account Team Members e.g. Sales Rep in Content Studio.

But in addition to that we need to have Account Team Members as attributes available in the segmentation.
For that we can create additional view based on table "CUAND_CE_IC_TM". This table contains link between Company and UserID of e.g. SalesRep. For the users it will be hardly possible to build segments based on UserIDs. So we need a solution to have at least First and Lastname of Users/SalesRep in the segmentation.

Any suggestions are welcome.

Regards

Danny

Accepted Solutions (1)

Accepted Solutions (1)

hakan_kose
Contributor
0 Likes

Hi Danny,

I bet you're referring to business partner concept for on-premise system while you're saying "it's so easy to import sales reps as employees in on-premise system". Because if you stick to interaction contact concept, there's no difference actually.

On the other hand, I think employees (Employee Master Data) should be really taken into account for a long term solution. I believe they should have their own business object and API's and we are also able to send out e-mails to them via SAP Marketing standard channels - e-mail, text messages etc. This is getting more and more important as you have to include more sales reps in SAP Marketing. Of course, they natually should have a linkage to account team information as well (relationship can be achieved with employee ID's as CUAND_CE_IC_TM has already that information).

Until mentioned scenario happens, all we can do is to ponder on workarounds - just like my previous reply.

For HANA data source creation part, actually you should be fine if you successfully pass this part. The latter parts (Part-1 and Part-2 respectively) are just as easy as on-premise (if we don't take attribute and analytical view types limitation into consideration).

Best Regards,

Hakan

Answers (4)

Answers (4)

hakan_kose
Contributor

Hi danny.lipkovski2 ,

Last time I checked, there's no out-of-box integration for account teams between SAP C4C and SAP Marketing Cloud (There's even an improvement request for that - IR: 206088). But if you're going to build a custom integration flow using OData services in SAP Cloud Platform Integration, of course you'll be fine. But if you want to do that, you should use new OData service API_MKT_CORPORATE_ACCOUNT_SRV instead of OData service CUAN_BUSINESS_PARTNER_IMP_SRV that's used for standard integration between SAP C4C and SAP Marketing Cloud. Because OData service CUAN_BUSINESS_PARTNER_IMP_SRV doesn't have a data entity for "AccountTeamMembers".

If you're going to use API_MKT_CORPORATE_ACCOUNT_SRV, you should be able to pass "Employee ID" value as well in addition to user ID (aka TeamMemberId). In this case, you would have a more reliable ID, that is Employee ID, than an User ID.

After the integration setup, there are two approaches I can suggest for the data management and segmentation part:

1) Having your sales rep data in SAP Marketing Cloud as interaction contacts

You could upload your sales representatives as interaction contacts with a simple custom field (let's say a boolean field named IS_EMPLOYEE) to differentiate them easily and with a specific Origin ID so that you can pass their employee ID's as origin ID's while you're uploading them to SAP Marketing Cloud. Later you would be able to create an additional join for your current data source to match origin ID's with the employee ID's in account team member table that you shared (CUAND_CE_IC_TM).

2) Having your sales rep data in SAP Marketing Cloud as custom business objects

Another option could be that you could create a custom business objects for your sales representatives. You could later upload them easily and use them in segmentation again based on their employee ID's again. With custom business objects, you wouldn't need to worry about your interaction contacts data like option #1 as they'll always represent your customers in this option. All you need to do is to make a simple join for your data source to match the ID field of custom business objects with the employee ID's in account team member table that you shared (CUAND_CE_IC_TM).

I hope this helps,

Kind Regards,

Hakan

PraveenT1
Participant
0 Likes

Hi Hakan,

I am looking into OPtion#2.

We were able to create custom business object for Sales reps with their data. I understood to join the account team member with the Employee table. I tried to import the view into SMC but it fails with an error

Unable to upload file. See details for more information. Key field DB_KEY of CUAND_CE_IC_ROOT, INTERACTIONCONTACTUUID, PARENT_KEY of CUAND_CE_IC_FCET or CUAND_CE_IC_RE, CONTACT_KEY of CUAND_CE_IA_RT, ROOT_KEY of CUAND_CE_IC_FT_D is not part of the view;Import not possible,chec

Thanks

Praveen

andreina27_
Explorer
0 Likes

Dear experts,

I have some dudes for the following cases, If I have integrated the B2B Out of the Box "Account Team":

  1. Can I use the additional view "CUAND_CE_IC_TM" from the table to relate the employees to the Accounts in the Segmentation App and send emails to those employees?
  2. With this view, If the same employee has many Accounts, is it possible to relate it and send emails to employees segmenting before the accounts?

Best Regards,

aminavloeberghs
Explorer
0 Likes

Dear danny.lipkovski2,

Did you manage to get the account team into the segmentation, with above described approach? We would like to set up the same work-around, but want to be sure that we can add account team members to segmentation in order to be worth the effort of a custom integration.

Many thanks in advance for the feedback!

Kind regards,

Amina

danny_lipkovski2
Participant

Hi Armina,

yes we managed to enable account-team data for segmentation.
We have adapted Integration in CPI to fill account-team. Additionally we have created CBO that stores all relevant employee-data. This CBO is updated manually as there aren't that many changes to employee data.

Finally we created HANA-view for segmentation.

Regards

Danny

aminavloeberghs
Explorer
0 Likes

Dear Danny,

We are currently struggling to make our custom view in segmentation view available for account team. We have already check our custom view multiple times and cannot find anything that is missing.

Our use case is merging two datasources (CUAND_CE_IC_TM and our CBO YY1_****) we have identified our join attribute (EmployeeID) and joined both datasources. We use a left-outer and have already tried 1.1 and n.m cardinality.


Our overall view looks as followed:

However when we enable it for segmentation the attributes remain empty. However if we create a CDS view we can see that the values are filled up and should be joined based on the employee ID.

Any recommendations on what we should check?

danny_lipkovski2
Participant
0 Likes

Thank you Hakan,

alternative two is similar to that apporach we also thought about.

But I'm wondering why this functionality is not available in standard already.
In an onPremise system it is easily possible to import the Sales Reps as employees and build HANA-View based on CUAND_CE_IC_TM and Employee Masterdata. But unfortunatelly this is not available in Cloud Scenario.

Regards

Danny