Skip to Content

Patch Creation on Wrong System (C4C)

Hi all,

We have a problem with our TEST tenant because we created a patch solution by accident. We did not perform any changes to the solution.

our cloud landscape looks like: PROD <-- TEST <-- DEV

In the TEST-system there should not be a patch, only in the DEV. Now the dev is behind in terms of the version.

Does anybody know if this will this cause any problems when deploying a new version from DEV system to TEST tenant?

Can we even create a new patch on the DEV system as long as the patch on TEST is present?

How to solve this issue? Can we simply assemble the patch on TEST and create a new patch on DEV and continue development as usual?

Thank you,

Kind Regards,


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Best Answer
    May 03, 2017 at 08:07 AM

    Although I already had a ticket, it took about 6 week to resolve this issue. SAP forced us to delete patch first in TEST and then in DEV manually. But we were still not able to create a new patch. Finally, SAP had to delete some references in the backend.

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Thomas,

      After you deleted the Patch in Dev while creating new 1 , what issues you faced?

      We are having similar issue now , We created a patch in test tenant and now In my dev and test versions are mismatched!

      Oh this is pathetic , SAP should handle this scenario in a better way.



  • Mar 14, 2017 at 12:42 AM

    Dear Thomas,

    We faced the same situation a couple of months ago.

    You need to raise an incident to SAP.

    Best Regards,


    Add comment
    10|10000 characters needed characters exceeded

  • Mar 14, 2017 at 01:42 AM

    Dear Thomas,

    In your case if the ( DEV and TEST ) system are hosted on same system, then it will cause a problem for your future development and testing activity.

    Auto distribution takes place in case of higher version of the patch solution if exist in the same physical system. Most of the time cleanup of the patch is required as the development of patch has to be done in ONE system.( DEV).

    Nevertheless to analyze the current situation and the landscape of your system, we would need an incident. Please raise an incident to SAP will all relevant details.

    Please refer -

    : Basic landscape activities of the Add-on life Cycle Management



    Add comment
    10|10000 characters needed characters exceeded

    • Dear Anant (@anant.acharya)

      thank you for your reply.

      I already created a ticket for this issue but was redirected to Help-Forum, PartnerEdge etc.

      Can you have a look into this Issue?

      Or can you tell me what I should add to my incident that SAP continues processing?