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 😮
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.