SAP Cloud for Customer Add ins offers Migration Workbench and Data Workbench (DWB).
Migration Workbench is the legacy tool, whereas DWB is an advanced tool built on OData framework. While DWB is intuitive, it also enables you to smoothly perform both data migration and maintenance activities.
This blog helps you to explain some common use cases or issues raised by Custom Add-on's while performing Project Merge activities.
Note - Usually happens if the namespace/ versions of the solutions in both the tenants are not in sync however below are some mentioned known errors and use cases :
1. Issue occurring due to Key User solution (KUT).
Error "Solution YXXXXXXXX_ is missing on productive tenant".
Explanation:
If a user creates a Custom Object Builder from Administrator Work Center, a back-end entry is created for the Specific Customer ID and with a specific name space with description Key User Solution.
As this has automatically created in source system and not present in the target system, system throws an error message Solution YXXXXXXXX_ is missing on productive tenant.
Resolution:
If the mismatch occurs due to the KUT solutions then you will have to delete it as there is no option to Disable a KUT solution.
You can delete it from the Administrator work center -> Custom Object Builder view -> Choose option Delete Solution.
OR
You can download the Zip file from source system and upload it to the target system, based on your business requirement.
2. Issue occurring due to Version mismatch in the Source and Target System.
Error - Sync/merge is not possible
Solution YXXXXXXX_ missing in target tenant
Solution YZZZZZZZ_ missing in test tenant
Pls ask your partner to upload missing solution(s) and retry afterwards
Resolution:
This is the most common error this happens, as the source and Target system does not have same Add- on Version.
For example, source system may have lower version of Add-on than target system OR Target system might have the higher Version that source system.
- Login to Cloud Application Studio in source.
- Open the required solution.
- Go to Implementation Manger and check the latest Add-on Version.
- You should be having the same zip file of the Add-on Solution as a backup.
- Login to Cloud Application Studio in respective Target system.
- Upload the same latest zip file, which is similar to source system.
- Click Activate on the uploaded Solution in the implementation Manager.
- Once this is done, Add-on Versions should be same.
3. Issue occurring due to incorrect enabling the solution.
Error : Patch versions of solution YXXXXXX_BC are different in test tenant and productive.
Resolution:
This happens, as the source and Target system does not have same Add- on namespace.
Example – In the test system, you might have enabled the Patch Name space, but in production system, Original namespace solution is enabled.
- Login to Cloud Application Studio in source.
- Open the required solution.
- Go to Implementation Manger and check the Add-on Name space.
- Enable the Original namespace if patch is enabled in source system.
4. Merge is failed While Merging Moving project solution profile to production tenant
An exception was raised
Source sys rep is different from target sys. Source: Target: /BY00XXYZ/BC .
Source sys rep is different from target sys. Source: Target: /BY00ZABC/BC .
Skip check withSPA/GPA Param BCT_IMPORT_NO_CHECK in the target tenant
An exception was raised.
The cause for the issue is that the add-on composition of the test and production system is not the same. The mentioned add-ons XYZ and ABC might be missing on either the test or production systems.
Resolution :
The issue can be over come by taking necessary action to bring the add-on composition of the two systems to the same.
NOTE - If you face any error in the merge related to Add -on, kindly first check these point and make sure Source and Target Add on status/Versions before raising an incident. If you cannot fix this issue after syncing the add on then please report an incident to SAP.
Cheers
Anant
