3713388 - Handling External ID Mappings After System Copy or System Refresh

• You have requested a Tenant Copy or Tenant Refresh and received the new tenant's details.
• External IDs for all Master Data will be pointing to the communication system from source/old tenant.
• You want to integrate the new tenant with an S/4HANA tenant (either the same S/4HANA tenant used before the copy/refresh or a different one).

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental." 

• SAP Sales & Service Cloud V2 Integration with SAP S4HANA
• SAP Sales & Service Cloud V2 Integration with SAP ERP
• SAP Sales & Service Cloud V2 Integration with SAP S4HANA Cloud

1. Unlike Sales & Service Cloud Version 1, all External IDs in Sales & Service Cloud V2 are stored in the respective entity rather than a separate structure. Every External ID is linked to Communication System Technical ID(technical id).
2. The technical ID is present in the communication system copied from the source system
3. In the new tenant received, create a new communication system with the System ID in a specified format (SIDCLNT111) and choose the same technical id from old communication system.
4. Delete the old communication system.
5. Create communication configuration with new communication system.
6. Do data load from S4HANA system and all the ID mappings will be auto updated with new communication system.

post-copy activities, tenant migration, communication system remapping, technical ID reassignment, initial load, re-synchronization, integration reconfiguration, cross-tenant integration, master data mapping, decommission old communication system, source system cleanup, landscape change, object ID mapping, re-point external identifiers, V2 external ID storage , KBA , CEC-CRM-INT , Integration for SAP Sales/Service Cloud , CEC-CRM-DC , Data Connector for SAP Sales/Service Cloud , Problem

SAP Sales Cloud and SAP Service Cloud Version 2 1.0