Skip to Content

Multiple releases in a year

Hello experts

Environment

I am in a project where Customer is implementing CRM, ECC

Customer has Development, ST (QA), SIT (Integration Test System), Pre-Production and Production systems

All systems has same base release across landscape i.e SAP CRM EHP3 and ECC EHP6

Requirement: Customer is planning to roll out multiple builds in a year. There could be maximum 4 builds released in a year. Along with build release they may go for version upgrade also e.g. from EHP 3 SP02 to SP05 or EHP 3 to EHP4.

Assumptions to implement any solution:

  1. Proper governance will be in place
  2. Solution manager is the only tool planned
  3. Functionalities planned CSOL, ChaRM, CCLM, DGP, Retrofit etc.

One Option which has evolved during discussion with customer is that to have multiple development system and should have one global development system where all release developments are synchronized. But since this is not SAP recommended approach and there are lots of challenges hence not proposing the same.

Another option which is SAP recommended is to propose Maintenance landscape and project landscape where from Mnt. Dev system to Proj Dev system retrofit can be used and ensure object synchronization. Here we can maintain only 2 versions (where as customer want to maintain 4 versions) and still not able to close the following point.

Query :

In a project where multiple releases planned and moved across landscape i.e. Pre-Production on Ver.1 QA on Ver.2 and Dev on Ver 3 in this case if there is some bug fix required for specific object which is available in development system with version 3 then how can we move change only specific to ver 1 across landscape which is on multiple versions?

Is there any better choice available?

Appreciate your feed back.

Thanks and Regards

Shriraj

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Dec 07, 2013 at 10:46 AM

    Hi,

    Requirement: Customer is planning to roll out multiple builds in a year. There could be maximum 4 builds released in a year. Along with build release they may go for version upgrade also e.g. from EHP 3 SP02 to SP05 or EHP 3 to EHP4

    That is good but first you need to get the release calender and then check which of the release are going to over lap and what can be the impact.

    In a project where multiple releases planned and moved across landscape i.e. Pre-Production on Ver.1 QA on Ver.2 and Dev on Ver 3 in this case if there is some bug fix required for specific object which is available in development system with version 3 then how can we move change only specific to ver 1 across landscape which is on multiple versions?

    This is some strange situation . Why it is difficult as when Version 1 was release from dev it might have another object also in the request and if you reimport that all the other object will be over written.

    how can we move change only specific to ver 1 across

    If you have only this object in that request that was released earlier when ver 1 was cerated than you can use that transport.

    As mentioned you need to have two landscape one for production support and one for the development project.If you have any urgent fix for the production support then your production support landscape would be able to fix it.

    If you think that in the development landscape you have two project having same deployment dates so you have create one dev system and then two quality system like (Pre-Production on Ver.1 QA on Ver.2) . As a best approach is to first work on the release calendar.

    The only drawback with two landscape is to get production support changes sync in development landscape.

    Thanks

    Rishi Abrol

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.