SAP C4C : Patch created in Test Teanat

[dhruv_mehta]

Hello Experts,

As you can see in the question header , We accidentally created a Patch in Test tenant ,while a Patch in Development tenant was already there.

So my main solution is for example ABC123_ is at same version on my Dev and Quality , but in Dev the patch of mail solution ABC123_ is XYZ123_ which is on version 10 in Dev and in Quality version is 11(Which we created accidentally). Now due to this I am getting a warning message in Dev system that Current version is not up to date ( coz Q tenant is on 11 ) , So can we delete the Patch in Quality and let the Dev system be on version 10 , i change solution from the requirment on D and upload the same in Q.

Meanwhile I have raised an incident to SAP , however it would be really helpful if someone can guide us for the same.

Regards,

Dhruvin

[anant_acharya · Accepted solution]

Dear Dhruvin,

Yes deletion can be performed provided Dev and Quality systems are not hosted on same Server.

If yes then you have to delete it from all the systems where the patch exist and its in same landscape server. ( in this case DEV & Quality).

As best practice, we should always use one system as development system and patch solutions has to be created on same system.

Coming back to the reported incident - 3101067353, I see that you have triggered the deletion and there are some left over objects in the backend and hence status of solution is partly deleted.

Once cleanup is done, you can proceed with creation of patch in Dev system.

Please refer the below blogs for more information on landscape.

https://blogs.sap.com/2015/08/27/sap-cloud-applications-studio-deployment-landscape-basics/

Hope that clarifies your question.

Regard
Anant

[dhruv_mehta · Accepted solution]

Hi Anant,

Thanks for the answer , It provided me a lot of information. However I have few doubts.

"Yes deletion can be performed provided Dev and Quality systems are not hosted on same Server." , How do we determine if both are on same server? & even if they are, they should be different instances right and shouldn't impact each other for deletion activity.

"we should always use one system as development system and patch solutions has to be created on same system." I agree 100% with you , but I think a validation mechanism can be built if the patch is created for a main solution and then another tenant should not create patch and throw some error about already existing InDevelopment status Patch.

For incident "3101067353" :, We are awaiting feedback and ready to create patch as soon as we get this issue sorted!

Thanks a lot for amazing support!

Regards,

Dhruvin

[dhruv_mehta · Accepted solution]

Hi Ananat,

After deletion of left over objects , I was able to create a patch in my dev system , However while activation of the patch got failed now. So Patch is created but its in Deployment failed status hence we are still not able to move our patch to production.

Shall we try to activate manually?

[anant_acharya · Accepted solution]

Dear Dhruvin,

Determining of servers ( System IDs),is currently not exposed to the external world. However i guess while creation of patch is gives a warning message. Thanks for your feedback, we will share it to our product management team.

About - 3101067353, kindly re trigger activation and check if its solves the issue.

If not, kindly report an incident and share the error log file from studio. We need check and analyze it further.

Regard

Anant

[dhruv_mehta · Accepted solution]

Its all solved , actually it got solved on the same day , I forgot to update in SCN. Thanks a lot for amazing support from SAP!