Technology Blogs by SAP
Learn how to extend and personalize SAP applications. Follow the SAP technology blog for insights into SAP BTP, ABAP, SAP Analytics Cloud, SAP HANA, and more.
cancel
Showing results for 
Search instead for 
Did you mean: 
Ulrike_Hormann
Explorer

Note: This blog has been updated on May 31 2023 to reflect changes in the behaviour of the application.


Initial Situation


Larger customers with service contracts often have separate contracts for several customer numbers. Since the SAP Cloud ALM entitlement is tied to the customer number, these customers are entitled to have several Cloud ALM tenants.

The replication of service data used to be tied to the customer number as well. This means that service information for a customer number was only transferred to the Cloud ALM tenant that was linked to the same customer number. If a customer had several customer numbers, they needed to have several customer Cloud ALM tenants to get access to all their service information.


In the above example, customer IDES has 3 customer numbers. In the past, that meant that they needed 3 Cloud ALM tenants to get access to the service delivery information for all 3 customer numbers.

This was not very convenient for large customers. Therefore, the behaviour of data transfer has been changed.

Inside SAP, the customer numbers belonging to the same enterprise are grouped. Based on that grouping, customers now have the option to maintain their own mapping which service information should go into which Cloud ALM tenant.


In the example above, customer IDES has the customer numbers 0001, 0002, 0003 and 0004. They have two Cloud ALM tenants, one for customer number 0001 and one for customer number 0002. They can now choose to have the following setup when sending service information to their Cloud ALM tenants:

  • Service deliveries for customer number 0001 are sent to the Cloud ALM tenant for customer number 0001

  • Service deliveries for customer numbers 0002 and 0003 are sent to Cloud ALM tenant for customer number 0002

  • Service deliveries for customer number 0004 are not sent to any Cloud ALM tenant.


When mapping the customer numbers to the Cloud ALM tenants, the service information for one customer number can go only to one Cloud ALM tenant. So when maintaining the mapping, make sure that you have a clear idea which service information should go into which of your Cloud ALM tenants.

How to maintain the mapping of customer numbers for transfer of service data



  1. To maintain the tenant mapping, access the Service Delivery Center of the tenant that should receive the service information.

  2. Select card “Maintain Tenant Mapping”.

    This card only shows up for users that have the Service Administrator role assigned.

  3. Once you have entered the tenant mapping, check the name of your parent company and which customer numbers are already mapped to your Cloud ALM tenant (i.e. for these customer numbers the service information are already sent to your Cloud ALM tenant).

  4. If you want to add additional customer numbers to your tenant, select “Add Company”.

    This will open a popup with the customer numbers belonging to your parent company that have not yet been mapped to any of your Cloud ALM tenants. Select the customer numbers for which the service information should also be sent to this Cloud ALM tenant.

    Confirm your selection.

  5. Verify that the newly mapped customer numbers appears in the list of mapped companies:


What happens after you have mapped a customer number to the Cloud ALM tenant


After you have mapped a customer number to your Cloud ALM tenant, new service information for that customer number is transferred from SAP to this Cloud ALM tenant. Services that will be delivered for this customer number now also appear in the Service Delivery Center of this Cloud ALM tenant.

Only new services are transferred by default. You can request to have older services (including their service results and corresponding issues and actions) pushed into your Cloud ALM tenant via an SAP incident on component SV-CLM-SD-SDW.

Removing the mapping for a customer number


In case you want to stop the data transfer for a customer number to your Cloud ALM tenant, access the tenant mapping as described above. In the list of mapped companies, remove the customer numbers for which the data transfer to this Cloud ALM tenant should be stopped.


Note:
You cannot remove the customer number belonging to the Cloud ALM tenant you are on. This customer number is marked as “Main” in the list. To remove this customer number, you have to open an SAP incident on component SV-CLM-SD to request the deactivation of the data transfer.

What happens after you have removed a customer number from the mapping


After you have removed a mapped customer number, the data transfer for this customer number between SAP and your Cloud ALM tenant is stopped. Data that was already transferred is still available in your Cloud ALM tenant, but it now becomes “READ ONLY” and is only visible for users with the Service Administrator role.

Further Information


Please check the blog Data Transfer for Cloud ALM for Service for details concerning the data transferred between SAP and the Cloud ALM tenant and blog How to get your Cloud ALM tenant ready for Service Deliveries for details about which roles are required for users in Cloud ALM for Service.
2 Comments