ECC6 shutdown : CIF deactivation and CIF reactivation ?

Hello,

We are running SAP ECC6 EHP5 and SAP SCM 7.02/Live Cache 7.9.

I am a sap basis guy, and it is quite difficult to perform any maintenance on ECC6 which would require a shutdown ( parameter change, kernel update, memory adjustment, ...) because of the impact it has on the CIF

I just wanted to share with you our current procedure just to determine if it is indeed a common practice.

I understand that similar issues have already been discussed on sap scn threads, but most of them concern SCM/APO shutdown, like here :

I could not find any note, best practice regarding ECC6 shutdown

So, whenever we stop the ECC6 ssytem , we need to run a CIF-DEACTIVATION job, which consists of the following steps :

No. Program name/command Prog. type Parameters

1 RIMODAC2 ABAP DEA_ATP_CHECK

2 RIMODAC2 ABAP DEA_ATP_BATCH

3 RIMODAC2 ABAP DEA_ATP_STOCK

4 RIMODAC2 ABAP DEA_ATP_SALESO

5 RIMODAC2 ABAP DEA_ATP_PURCH

6 RIMODAC2 ABAP DEA_ATP_MATERI

7 RIMODAC2 ABAP DEA_ATP_PLANTS

This usually takes one hour.

And then after ECC6 system is restarted , we run the CIF-REACTIVATION job which consist of the following steps :

No. Program name/command Prog. type Parameters

1 RIMODGEN ABAP ATP_PLANTS

2 RIMODGEN ABAP ATP_MATERIALS

3 RIMODGEN ABAP ATP_PURCH_ORDS

4 RIMODGEN ABAP ATP_SALESORDER

5 RIMODGEN ABAP ATP_STOCK

6 RIMODGEN ABAP ATP_BATCHES

7 RIMODGEN ABAP ATP_CHECK

8 RIMODAC2 ABAP ATP_PLANTS

9 RIMODAC2 ABAP ATP_MATERIALS

10 RIMODAC2 ABAP ATP_PURCH_ORDS

11 RIMODAC2 ABAP ATP_SALESORDER

12 RIMODAC2 ABAP ATP_STOCK

13 RIMODAC2 ABAP ATP_BATCHES

14 RIMODAC2 ABAP ATP_CHECK

15 RIMODDEL ABAP ATP_ALL

16 RAPOKZFX ABAP ATP_GATP

17 RCIFIMAX ABAP ATP_GATP

18 RDELALOG ABAP ATP_GATP

This takes 7 hours !!!

I am starting to suspect that we might not be doing the "right thing", but I am definitely not an APO expert.

Could you please kindly share your practices, thoughts ?

Thanks and Regards