Skip to Content
SAP Cloud Applications Studio

How to handle common Merge issues.

Dear All,

This document helps you to explain the common issues, which occurs while performing Project Merge activities.

  1. Issue occurring due to Key User solution.

  Error - Solution YXXXXXXXX_ is missing on productive tenant.

Cause:

If a user creates a Custom Business Object 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:


  • Login to Cloud Application Studio.
  • Open the Respective Key User Solution.
  • Right Click delete is not enabled.

For now right click and delete option is disabled in Cloud Application Studio, hence you need to raise an incident to SAP to delete this from backend.

NOTE - This might be taken into consideration in one of the future releases.

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 - Patch versions of solution YXXXXXX_MAIN are different in test tenant and productive.

Cause:

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.

Resolution:

  • 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.

Above error while merge should not occur.

3. Issue occurring due to incorrect enabling the solution.

Error : Patch versions of solution YXXXXXX_BC are different in test tenant and productive.



Cause:

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.

Resolution:

  • 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.

Points to consider :

1. If you perform any Life cycle activities ( Deletion/Upload/ Activate/Enable) in Cloud Application Activities, then you should wait for 24 hrs before you trigger  Merge activity as the status will take some time to sync in the back end. ( We are working on a  fix to reduce the delay caused in process of auto sync in backend).

2. If you face any error in the merge related to Addon, kindly check the Source and Target Add on status/Versions before raising an incident.

Regard
Anant

No comments