Skip to Content

Best Practice: Migrating transports to Prod (system down etc.)

Hi all


This is more of a process and governance question as opposed to a ChaRM question.

We use ChaRM to migrate transports to Production systems. For example, we have a Minor BAU Release (every 2 weeks), a Minor Initiative Release (every 4 weeks) and a Major Release (every 3 months).

We realise that some of the major releases may require SAP to be taken offline. But what is SAP Best practice for ANY release into Production? i.e. for our Minor BAU Release we never shut down any Production systems, never stop batch jobs, never lock users etc.

What does SAP recommend when migrating transports to Prod?

Thanks

Shaun

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

2 Answers

  • Sep 21, 2014 at 11:36 PM

    Bump 😊

    Add comment
    10|10000 characters needed characters exceeded

  • Sep 22, 2014 at 09:19 PM

    Have you checked out the "Two Value Releases Per Year" whitepaper for SAP recommendations? Section 6 is applicable.

    Lifetime Support by SAP » Two Value Releases per Year

    The "real-world" answer is going to depend on how risk-adverse versus downtime adverse your company is. I think most companies would choose to keep the systems running except when SAP forces an outage or there is a real risk of data corruption (some data conversions and data loads, for example).

    Specific to your minor BAU releases, it may be wise to make a process whereby anything that requires a production shutdown, stopped batch jobs, locked users, etc. needs to be in a different release type. But if you don't have the kind of control, your process will need to allow for these things to happen with those releases.

    Also, with regards to stopping batch jobs in the real world, you always need to balance the desire to take full advantage of the available systems versus the pain of managing the variations. If your batch schedule is full, how are you going to make sure the critical jobs complete on time when you do need to take the system down? If it isn't full, why do you need that time? Can you make sure only non-critical batch jobs run during those times? Do you have a good method of implementing an alternate batch schedule when need be?

    Add comment
    10|10000 characters needed characters exceeded