3715871 - Clarifying The Use Data Transfer Tool And Party Roles

This document aims to clarify some doubts regarding DTT tool & Party Roles.

SAP Cloud for Customer

In general party roles are NOT migrated because in V2 different party role categories are allowed than in V1. Therefore users have to create the party role from scratch.

To use a custom-defined party role, e.g. z1 “Project Lead”, defined in SAP Sales Cloud V1 with flag “Responsibilities”, a respective party role in SAP Sales Cloud V2 has to be created as follows:

1. Check in admin settings for business partner relationship the name of the respective relationship category. The relationship should have been migrated, e.g. Y100 “Project Lead Relationship”. See SAP help Transition Guide BuPa Relationships
2. Create in admin settings for party roles a new custom-defined party role with the same code value, e.g. z1 “Project Lead”, choose the correct party role category and assign the correct direction of the migrated relationship Y100 “Project Lead Relationship”, e.g. “has Project Lead” and the source party, e.g. account.

To use the new party role in transactions, for example opportunities or quotes, assign it the respective party scheme.

Other custom-defined party roles with or without assigned relationships, flag for responsibilities, etc. have to be migrated the same way.

Also, keep in mind a few observations: 

• Custom-defined party roles are not migrated from V1 to V2. They have to be created manually in V2 because the concept is different. 
• The DT tool itself does not delete the custom-defined party roles. 
• To transfer the Sales Team from C4C to V2 create the needed custom-defined party roles manually in V2 and assign the relationships used in business partner master data.

Migrate; V1; V2; Data; Transfer; Tool; Party Roles. , KBA , CEC-CRM-PAP , Party Processing for SAP Sales/Service Cloud , How To

SAP Sales Cloud and SAP Service Cloud Version 2 1.0