cancel
Showing results for 
Search instead for 
Did you mean: 

lock development during EHP Update

0 Kudos

Hello all,

we are doing a EHP6 update on our ERP System.

We have upgraded our development system already.

Now we are going to update our quality system. Now my question.

We are in the phase "preprocessing". Now the SUM asks for lock the development enviroment.

Does this mean, that we are not able to make emergency transports to the quality system and also later to the production system when it is in this phase ?

Thanks for your help.

Jens

Accepted Solutions (1)

Accepted Solutions (1)

anandkarthik_raja
Active Participant
0 Kudos

Hello Jen,

To answer your question with reference from SUM guide.

  

______________________________________________________________

Be aware that at the beginning of the 

Preprocessing

roadmap step, the ABAP Workbench has to be locked. This has an impact on the development system as you can no longer provide corrections. The production system is also affected as no emergency corrections can be implemented in the system.

__________________________________________________________________________________

Regards,

Anand.

Answers (3)

Answers (3)

Reagan
Advisor
Advisor
0 Kudos

Hello

We are in the phase "preprocessing". Now the SUM asks for lock the development enviroment.

Does this mean, that we are not able to make emergency transports to the quality system and also later to the production system when it is in this phase ?

The quick answer is NO.

No changes to the development objects (ABAP Workbench) is allowed into the system.

Cheers

RB

Former Member
0 Kudos

Hi Jens,

If you have chosen downtime minimized, the upgrade program asks you to lock the ABAP Development Workbench  in phase REPACHK2. This lock is needed to prevent development objects (for example, ABAP reports, table definitions, and so on) from being changed during the upgrade, since these modifications would be lost.

This phase displays all the repairs and corrections that are not released and writes them to the REPACHK2.LOG file.Before you continue, you must release and confirm all the open repairs; otherwise, the objects in them are locked.

Hence after this point no changes are allowed to be transported.

 

Thanks,

Manas

former_member182307
Contributor
0 Kudos

Hello Jens,

Yes. You must not allow any modification to be done.

Best regards,

Steve.