In the last blog we looked at the design considerations for supporting integration, after a test tenant for a SAP Hybris Cloud for Customer system is created by coping a productive tenant. Now let’s look at how to adjust the data post the tenant copy. I will limit the steps to Cloud for Customer system only and will talk about adjustments on SAP Business suite system and middleware (HCI/PI) system in a separate blog to keep the content short.
Before we can use the utility/tool to adjust the content post the tenant copy, let us first look at some of the prerequisites that should be meet.
- We only support Test tenant creation without change project functionality. Please see the wiki page Important Tips for Requesting Test Tenants (After Go-Live)
- It is recommended to have close consideration on the timing of the request for the new C4C tenant with the creation of new on premise (CRM/ERP) test system so as to maximize data parity between the two systems. Data discrepancies due to timing issues of the two test systems could prevent subsequent master and transnational data from replicating successfully. Hence, no data should be created in either system and replicated back and forth. Just to explain this : Let’s assume the test tenant was copied from a productive tenant on a given date. And after 3 days the SAP Business suite system was copied. Now the data that ware created in these 3 days is not available in the C4C test tenant, as the tenant was copied before these data existed in the system.
- We need to create a new communication system and corresponding communication arrangements. Even though a full copy of tenant would copy the communication systems and the communication arrangements, we don’t support adjusting the existing communication system details as of now.
How to perform the integration content adjustment post tenant copy
Navigate to Adapt Integration Content for New Tenant OWL using WOC Administrator-> General Settings-> Integration
Using Quick Create (New Adaptation), provide the Old and New Communication system details and execute
It is advisable to first run the tool in test mode to verify the how many objects are going to be adjusted.
Unchecking the Test Mode button above, would result in actual run.
The execute action triggers a background job and the status is updated in the OWL. Each job creates an application log.
The application log ID captures the result of the job run. Here we can see the no of ID mapping and BTD references adjusted for various BO in the test tenant.
That’s it on the SAP Hybris Cloud for Customer side. In the next blog we will see what needs to be done on SAP Business suite and middleware system to make the integration work end to end post the tenant copy.