Skip to Content
Technical Articles

Standalone Retrofit SAP Solution Manager 7.2 – Configuration

Hello All,

In this blog we will discuss the configuration of Standalone Retrofit for SAP Solution Manager 7.2.

Introduction

I work as an SAP Basis consultant and have quite insight for SOLMAN 7.2 as well.

Recently I implemented Standalone retrofit.

Let me briefly describe the same with the help of  diagram.

All customers who have Dual SAP System Landscape (Maintenance landscape & Implementation Landscape) have the challenge to ensure that they synchronize the maintenance changes from Maintenance Landscape with the implementation landscape.

 

So our retrofit will work between Maintenance and Project DEV systems.

 

Configuration

Now lets start-up with configuration of standalone retrofit.

Login to Solution Manager and complete below activities.

SOLMAN_SETUP -> Change Control Management -> Change Request Management > Step Perform Basic Setup (all activities of all sub-steps)

SOLMAN_SETUP -> Change Control Management ->Change Request Management > Step Set Up Downgrade Protection and Retrofit (all activities of all sub-steps): Configure CSOL for the development system of the implementation landscape

Complete all the above steps with guided procedure as described.

 

Activate standalone retrofit parameter in your Solution Manager 7.2

SM30 -> /TMWFLOW/RCONFIG

 

Activate BAdI in both DEV’s ( Maintenance and project Landscape )

1.In the managed system, call transaction SE19.

2.In the Edit Implementation screen area, choose option Classic BAdI.

3.Enter implementation name RETRO_STANDALONE.

4.Choose Change.

5.On the Change Implementation screen, choose the Activate icon

 

 

 Configure Solution Landscape for our maintenance environment.

Activities

  1. Login to Solution Manager – Tcode SLAN
  2. Choose Create Solution.
  3. Enter the required information.
  4. Assign the relevant data to your solution.
  5. Save your entries.

It will look something like above.

Create Domain Link

Create domain link between DEV of Maintenance and DEV of project Landscape so that both can communicate.

  1. Log on to one of the two domain controller systems.
  2. Call transaction STMS.
  3. Choose Overview  Systems . The system overview appears.
  4. Choose SAP System   Create  Domain Link .

 

 Create a Phase Cycle for retrofit configuration.

  1. Login to solution manager
  2. Run crm_ui
  3. Select create Cycle
  4. Now select Create Phase Cycle

Fill all the details and click on save.

 

Now Create Task for Phase Cycle

While creating tasks chose your transport track and include your retrofit system in the track.

It will look something like below:

 

Conclusion:

All the configurations are now completed.

You can access your retrofit tasks and cycle directly from SOLUTION Manager.

Login into SOLMAN – > Run tcode solman_workcenter -> Select
Change Management -> Administration

 

 

Please do let me know how you find this blog.

All questions are welcome I will try to assist as soon as possible.

Thanks 😊

13 Comments
You must be Logged on to comment or reply to a post.
  • hi Rishi,

    What is standalone in this case how it is different then other classical CHARM configuration? it means after implementing this scenario  we can now parallely transfer the same transport to project track once we release it from maintenance track.

     

     

    • Hello Sumit,

      Standalone Retrofit only use some of the CHARM configuration such as creation of Phase cycle and transport track. Yes you can transfer same transport to project track with the help of SOLMAN as being in middle to help you transfer the objects.

      Hope it helps !

  • Hi Rishi,

     

    Nice Blog. Very informative.

     

    I have got a few questions to be asked. Your answer will be highly appreciated.

    We are using Charm and QGM in both landscape Maintainance/DeV. However, 1 project team does not want to use either Charm/ QGM. So we decided to implement Standalone Retrofit so that we can capture the DEv team changes in Solman by CSOL, which they are not using charm/QGM.

    – Our both Dev clients are part of the same domain controller and it’s in 1 box with the same production client. So I believe we don’t have to create Domain Link?

    -Since the Maintenance team is using Charm. I don’t have to implement BAdi in Maintenance DEv client rite?

    – You have not mentioned the Step to connect your DEV CTS project to the Charm Cycle?

     

     

    • Hello

      – Our both Dev clients are part of the same domain controller and it’s in 1 box with the same production client. So I believe we don’t have to create Domain Link?
      Yes you won’t need to create Domain links.
      -Since the Maintenance team is using Charm. I don’t have to implement BAdi in Maintenance DEv client rite?
      check for relevant BAdi for Retrofit in case of CHARM. It should already be activated.

      – You have not mentioned the Step to connect your DEV CTS project to the Charm Cycle?

      TR is directly created in SOLMAN retrofit menu and then it is worked upon in respective DEV system. for this you have to use Phase cycle.

      I hope information is helpful.
      Regards
      Rishi
      • RIshi Singh ,

        Thanks, Rishi for your valuable input.

        Regarding the last point, I wanted to check if the team wants to create TRs from Se01, we need to map the CTS project of the dev team to Charm Cycle so that CSOL entries will be registered in Solman System and later we can do the retrofit from the task list.

        However, The mapping between the CTS IMG project and the CHARM IMG project can be done using a report that can be found in SOLMAN_SETUP under Change Request Management – Managed SAP system configuration,

        A report exists for either side (maintenance & project) to be able to register released transport requests + their CTS IMG project into a table for use in this scenario. Once the mapping is in place, we can then just create transport requests ( via se01, release them via se01 as well) and the retro􀉼t picks them up automatically.

        This is really what standalone retro􀉼t is about in fact. A developer can create transport in SE01, using his / her known “CTS IMG project” as they are used to do (without CHARM) and this automatically gets “dropped” into the Retro􀉼t scenario upon release.

         

        Anyway thanks for your blogs, it’s really useful.

         

        Regards,

        Sultan

         

  • Hello Rishi,

    Nicely placed Blog !

    I have a question to you, we are trying to run Project (1) in our maintenance track and Project (2) in our project track due to time constraints to finish both projects in time.

    While we checked the possibility to run two projects parallel which uses same objects, we thought of Solman Retrofit, but the documentation for SAP Solman Retrofit always showed single directional retrofit possible from maintenance Dev to Project Dev and never a retrofit possible vice versa.

    Your blog was the first documentation which showed a bi-directional retrofit, is it possible to synchronize the changed objects from Project Dev back to Maintenance Dev as shown in your diagram.

    The diagram which I have attached is the only possibility I saw till now for fitting the changes from Proj Dev to Mnt Dev, could you please clarify whether a reverse retrofit is possible.

    Thanks in Advance !

    Best Regards,

    KiranSAP_Solman_Retrofit

    SAP_Solman_Retrofit

    /
    SAP_Solman_Retrofit
  • Hey RIshi Singh

    Good explanation, got to know about the other version of Retrofit Setup.

    Have few queries,

    • What are the additional features that we can leverage in ‘Stand Alone’ retrofit, than from ‘Enhanced Retrofit’? We had this big query in front of us when we were planning for Retrofit between two different versioned S4- SAP systems.
    • How do you advise for ATC Setup here? if at all, planned to keep it in place to verify the source changes are eligible for upper versioned SAP systems.
    • What exactly the Core-Technicality that makes this setup as StandAlone Retrofit(Other than the parameter – SM30 -> /TMWFLOW/RCONFIG)

    Thanks
    Regards
    Vinayak Budapanahalli

     

  • Hi RIshi,

    Very nice blog.

    A question for you, what is your suggestion for the project DEV system after a project is completed?  We have project DEV–>Virtual as a project landscape, can we move all project related transports back to maintenance DEV and remove project DEV?

    Thanks

     

    • Hello Jing,

      We usually refresh Maintenance Dev with production by selecting Customizing option after the project Go-live.

      By doing so project changes are copied in Maintenance Dev.

      Regards,

      Sultan