How to Update ID Mapping After a Tenant Refresh in SAP Sales / Service Cloud V2

Introduction

A tenant refresh (also known as a tenant copy) is a routine operation in SAP Sales and Service Cloud V2 environments. It involves copying data from a production tenant to a test or quality tenant to enable realistic testing scenarios. However, after a tenant refresh, the ID mappings used by communication systems and integration scenarios still reference the source (production) tenant's external system identifiers. If left unchanged, integrations on the refreshed tenant will attempt to communicate with the wrong endpoints or use stale references, leading to data inconsistencies or failed transactions.

This blog walks through the steps required to update ID mappings after a tenant refresh in SAP Sales / Service Cloud V2, ensuring your integrations function correctly on the target tenant.

Prerequisites

Before you begin, ensure you have:

– Administrator access to the target (refreshed) tenant in SAP Sales / Service Cloud V2

– Knowledge of the Communication Systems and Communication Arrangements configured on the tenant

– Access credentials for the connected external systems (e.g., SAP S/4HANA, SAP BTP, middleware)

– A list of the correct endpoint URLs and system IDs for the target landscape (test/quality)

Understanding the Problem

When a production tenant is copied to a test tenant:

1. Communication Systems retain the production system's host names and technical IDs.
2. Communication Arrangements (which link communication scenarios to systems) still reference production credentials and endpoints.
3. ID Mappings — the internal-to-external identifier relationships used for business partner replication, product synchronization, and other integration flows — still point to production GUIDs and external IDs.

If these are not corrected, the test tenant may inadvertently push or pull data to/from the production landscape.

Step-by-Step: Updating ID Mapping Post Tenant Refresh

Step 1: Review Communication Systems

1. Log in to the refreshed target tenant as an administrator.
2. Navigate to Settings > Communication Systems.
3. Review each communication system entry. You will see they still reference production hostnames and system IDs.
4. For each system:

   – Update the Host Name to the corresponding test/quality system URL.

   – Update the System ID if it differs between production and test landscapes.

   – Verify and update the Business System ID which is critical for ID mapping resolution.

 Step 2: Update Communication Arrangements

1. Navigate to Settings > Communication Arrangements.
2. For each arrangement linked to an external system:

   – Open the arrangement and verify the assigned Communication System is now pointing to the correct (non-production) target.

   – Update authentication credentials (user/password or OAuth tokens) for the target system.

   – Update the Service URL path if the test system uses a different service endpoint.

1. Save the changes.

 Step 3: Update ID Mapping via Data Import and Export

This is the core step and represents a key difference from V1. In SAP Sales / Service Cloud V2, ID mapping is managed through the Data Import and Export area rather than a direct Excel upload of external IDs and systems as was possible in V1.

3.1 Navigate to the ID Mapping Configuration

1. Go to System Settings > All Settings.
2. Search for “import” in the search bar.
3. Under Data Import and Export, select ID Mapping.

You will see two tabs: Configuration and ID Mapping.

3.2 Enable ID Mapping for Relevant Entities

1. Select the Configuration tab.
2. You will see a list of entities (Account, Competitor, Competitor Product, Contact, Employee, Individual Customer, Organizational Unit, Product, etc.) each with an Enable ID Mapping toggle.
3. Enable the toggle for every entity that participates in your integration scenario and requires external ID resolution after the refresh.

-> Important:  Once you activate ID mapping for an entity, the external keys used in the “Import + Create” mode file for that entity are retained and can be reused instead of Technical IDs, to make subsequent updates using the “Import + Update” mode.

3.3 Create ID Mapping Records (Upload Technical Mapping and External ID)

1. Switch to the ID Mapping tab.
2. Click Download Template to obtain the Excel template for the entity you need to map.
3. The template contains two columns:

– External_Key (Column A) — The external identifier from the connected ERP system (e.g., `EXT_PROD`, a business partner number, or material number).

– ID (Column B) — The Technical ID (UUID) of the corresponding record in SAP Sales / Service Cloud V2.

1. Populate the template with the correct External Key and Technical ID pairs for the refreshed tenant.
2. Click Import > Create Records to upload the mapping file and establish new ID mapping entries.

If you need to correct existing mappings rather than create new ones, use Import > Update Records instead.

> Tip: You can also use the Export function to download current ID mapping entries, review them in Excel, make corrections, and re-import using “Update Records.”

3.4 Run the Data Replication from ERP

After the ID mapping records have been uploaded:

1. Trigger a data run (initial load or delta replication) from the connected ERP system (e.g., SAP S/4HANA).
2. The system will automatically resolve and map the external IDs uploaded in the previous step against the technical entities in Sales / Service Cloud V2.
3. This establishes the correct end-to-end mapping between the ERP records and the Sales/Service Cloud V2 records on the refreshed tenant.

This automated resolution is what makes the V2 approach different — you supply the technical mapping and external IDs upfront, and the ERP data run binds them together.

Step 4: Validate the Updated Mappings

After updating, validate the configuration:

1. Test connectivity by navigating to the Communication System and using the “Check Connection” function (if available).
2. Trigger a sample integration — for example, replicate a single business partner or create a test sales order — and verify the data flows to the correct test system.
3. Review error logs under Settings > Communication Monitoring or the Integration Message Monitoring to confirm no cross-environment contamination. 

 Common Pitfalls

– Forgetting middleware configuration: Even if the Sales/Service Cloud V2 tenant is updated, your integration middleware may still route messages to production. Always update both ends.

– Stale OAuth tokens: Tokens issued for the production system will not authenticate against a test system. Regenerate them.

– Partial updates: Updating the Communication System hostname but not the Business System ID can lead to ID mapping lookup failures.

– Not disabling event notifications first: Before updating, temporarily disable outbound event notifications to prevent unintended messages from being sent to production endpoints during the transition window.

Best Practices

1. Document your integration landscape before the refresh, including all Communication Systems, Arrangements, and their associated credentials.
2. Create a post-refresh checklist specific to your organization that covers all affected integrations.
3. Use environment-specific naming conventions for Communication Systems (e.g., `S4H_PROD`, `S4H_TEST`) to quickly identify what needs updating.
4. Automate where possible using scripts or CI/CD pipelines that can toggle configuration between environments.
5. Refer to official SAP guidance — SAP provides a “Product Guidance for Tenant Setup and Refresh (V2) with SAP Sales and Service Cloud” document that covers the full scope of pre- and post-refresh activities.

Conclusion

Updating ID mappings after a tenant refresh is a critical post-refresh activity that safeguards the integrity of your integration landscape. In SAP Sales / Service Cloud V2, the process has evolved from V1's direct Excel upload approach to a two-phase method: first uploading the Technical ID-to-External Key mapping via Data Import and Export > ID Mapping, then triggering an ERP data run to automatically bind the external IDs to the correct technical entities.

By systematically reviewing Communication Systems, updating Communication Arrangements, enabling ID Mapping per entity, uploading the mapping file, and running the ERP replication, you ensure that your refreshed tenant operates independently and does not interfere with production data flows.

Taking the time to establish a repeatable post-refresh process will save significant troubleshooting effort and prevent potential data leakage between environments.

Have questions or additional tips? Share your experiences in the comments below.*

Source link