Development Madness during Upgrade

[#1]

Hello World,

please hear me out before demanding to drive a stake through my heart.

Because I know very well that latest during step "Preprocessing" of the upgrade process (EHP5ERP6 -> EHP7ERP6) *no* development should take place, except absolute emergencies.

Problem was, when we designed the upgrade strategy for our systems 4-6 weeks ago, I "forgot" to narrow down the definition of "emergency" to our developers to the bare essentials - believing the term "emergency" was self-explanatory 😞

Now they come to me almost twice a day with another "let's push this one one in quickly, too ..."

By now the system is done with Preprocessing and we await the maintenance window for step "Execution" - which unfortunately is still two days in the making.

And guess what...they'd like for me to import one more "emergency transport" into the system.

Its a 'Y' report, so the logic goes, "its in the customer name space, so what could possibly happen?"

My big worry is, that *if* something happens, the Production system will be down!

No SE38, no STMS, no SE80 and worst of all, no Prod system and the whole factory is waiting for this thing to come back online - and yes, ours is a 24x7 operation.

Has anyone got any experience with pushing in transports, within the customer namespace, so late in the upgrade process?

PS: I know this whole procedure is a "no, no", but I am one Basis guy here, being outnumbered 5 to 1 by the developer team 😮

[Former Member]

"but they forced me (yes they have ways to do that here), to perform the upgrade of DEV and PRD in parallell" <----

What ? What happens if there is a problem on production ?

You won't be able to fix anything ?

This has disaster written all over it.

Something SERIOUS will likely go wrong as you will be importing different SAP component versions.

EHP7 has a different code base to EHP5/6.

Bringing transports though across differing versions WILL break things.

Your doing development work on a non upgraded QA system - a production system ?

This is going to potentially have serious probably catastrophic consequences.

I 

[Former Member]

Nope, the QUA upgrade was the last of the successful test runs.

So that box is already EhP7-ERP6

[Former Member]

So QA is upgraded but not Dev or Live ?

This will make dev inconsistent now.

Whats going to happen is that the versions of programs on dev will be different to QA / Production.

You won't be able to get the developers to do their changes again once dev is upgraded.

This means than when Dev is available, you will have old reports in dev being transported over newer reports, then then "old" version potentially ending up in production and breaking things.