Skip to Content
avatar image
Former Member

Retrofit functionality

Hi

We are using Retrofit functionality which is as follows:

  1. MAINT(DEV) à MAINT (TEST) à PROD

  1. Retrofit to IMPL (DEV) à IMPL (TEST) à PROD after this all changes including retrofit are again brought back to MAINT(DEV).

PROD is only single production server using dual maintenance.

So basically urgent changes are retrofitted in release cycle which is mostly quarterly release.

We are again putting the retrofitted changes back to PROD server from where they have originated.

This creates a risk of putting old changes back to production after new ones if CHARM/Transport sequence is  not followed correctly.

Then I read this old blog:

http://scn.sap.com/people/hannes.kerber/blog/2013/06/13/do-i-need-charm-to-use-retrofit

This blog says that retrofit functionality can be used without CHARM but with only task list.

Could you please throw some light on this.

We don’t want to include retrofit in release cycle but keep it away so as to minimize the risk for taking back the retrofits again to PROD.

Any documentation on this would be of help.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    Oct 26, 2015 at 04:19 PM

    Hi Siddharth,

    As you know, during the retrofit we have three options - Auto Import, Semi automatic and Manual changes.

    From my perspective, only the Auto- import requests go to Production again, but there is a possibility that these objects may also get changed in the Impl dev after retrofitted as part of project.

    For Semi automatic and Manual changes - the object has already modified in Implementation dev system and these modified objects go to Production.

    Regards,

    Vijay

    Add comment
    10|10000 characters needed characters exceeded

  • Oct 27, 2015 at 10:05 AM

    Hi Siddharth

    I believe "enhanced retrofit" cannot be used without CHARM (at least non in standard) so that's probably an old blog post.

    You can use CHARM on the maintenance landscape, create retrofit transports in implementation landscape, retrofit changes and then manage transports in the implementation landscape without CHARM if you want. It's not obligated to manage those retrofit transports in CHARM.

    Best regards

    Tom

    Add comment
    10|10000 characters needed characters exceeded