ECC6 shutdown : CIF deactivation and CIF reactivation ?

[Farid]

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

[babu_kilari4 · Accepted solution]

Hello Raoul,

Deactivation and Activation of the IM jobs is definitely required from APO perspective. However, I am not sure of the actual question from Basis perspective.

Babu Kilari

[Farid · Accepted solution]

Hi Babu,

My question is :

Do you need to deactivate and reactivate CIF whenever you stop the ECC6 system ?

Thansk and Regards

[Former Member · Accepted solution]

HI Raoul,

No need to activate and de activate CIF when ever you stop ECC system.

Reason is you will send data to APO only When ECC is not available i.e., RFCs not working then you will set up the connections and do data transfers.

Check any data transfer is happening by directly/batch. Postpone those activities..

Prior to shut down ECC/SCM send remainders to users that the systems will not be available.

Use these 2 programs from SCM side when you have stopped ECC.

RSTRFCQ1 : Stop Outbound Queue

RSTRFCQ3 : Restart Outbound Queue.

In our project we have to postpone/stop the jobs for data transfers between ECC and APO.

However you will be having daily CIF jobs to make ECC and APO in synch. So, once you re start your ECC regular CIF jobs will activate new objects(master and trnasaction data) and will deactivate lod data.

Thanks,

Bala.

[babu_kilari4 · Accepted solution]

Hello Raoul,

I second Bala's comments here. From Shutdown perspective, Deactivating an IM and re-activating it from scratch it takes lots of time and the most important thing is it CIFs all the product location combinations. I am sure all you need is to get the CIF happen for the delta products. So, why deactivate for this specific case.

Otherwise, for a normal business to be running. Running RIMODGEN and RIMODAC2 would get the Reactivation done for the delta products. It is like deactivating the old IM and activating a new one.

Hope this helps

Babu Kilari