Copy Solution Profile – Handling PDI Add-On Conflicts
A solution profile is a collection of scoping decisions and business configuration settings for the SAP solution throughout its entire life cycle. With this function, you can copy your existing solution profile from one tenant to another tenant. The copy of the solution profile includes scoping and fine tuning.
A very common issue that occurs during the Copy Solution Profile is the Add-on conflict errors. This happens if you have PDI solutions implemented in the tenants but the namespace/ versions of the solutions in both the tenants are not in sync.
This blog will help you to understand the pre-cautions you must take before requesting for a Copy Solution Profile if you have add-ons in your tenants.
Copy not allowed; source and target system have different add on versions
Copy not allowed; source and target system having different versions.
Pre-requisites for Copy Solution Profile:
- The source and target tenant’s must be in the same release version, as it is not allowed to copy a solution profile during the upgrade window.
- You need to login to SDK of both the source and target tenant.
- Compare the solutions in both the tenants. You need to verify the Namespace of the solutions, Status(Deployed, Disable e.t.c) and the Patch Versions.
- Deploy/ Enable/ Scope the missing solution in the source/ target tenant in comparison with the other tenant.
- Ensure the version of the solution in both the tenants are the same. If not, you should download and upload the correct version to the other tenant so that the solution version is in sync in both the tenants.
- Disable all the patch solutions in the target tenant and enable Original Solutions as there will be no patch namespaces present in the Production tenant(Source).
- Delete(or Disable)/ Upload the Solutions which are not available in the source/target tenant.
Now the source and target tenant should be in sync in terms of Add on solution namespace, version and status, you will be able to proceed with the copy solution profile. Once the solution profile copy is successful you can enable the patch namespaces and continue with your developments.
Key User Solutions:
In case you have any Key User Solutions(Solutions created via Custom Object Builder in the UI) in your tenant, then the above mentioned points are applicable here as well.
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 -> Delete Solutions.
Note: If you disable/ enable any solutions, the scoping in the business configuration will also be disabled. So for your functionalities implemented via SDK to work you will have to again scope the solution in the project.
I hope this blog post gives you some insights about how you can successfully copy a solution profile.