cancel
Showing results for 
Search instead for 
Did you mean: 

Blocking CIF queues

former_member928177
Participant
0 Kudos

Dear All,

We are running SNP optimizer for the period of two years, we are facing problem of incorrest plannig results by optimizer since when optimizer runs therer are lot of activities happening in R/3.

So we are thinking of blocking the queues before we schedule optmizer run and then starting again when optimizer finishes.

Yes, CIF queues can be stopped from OM17 or program RSTRFCI1 but dont know the proper steps for doing that.

Please guide how to proceed ?

1) What the things we should check first ?

2) If we are blocking the queues will queues will be in waiting status or sysfail ?

Regards,

Amol

Accepted Solutions (0)

Answers (5)

Answers (5)

Former Member
0 Kudos

Hi Amol,

Is your query resolved?

former_member928177
Participant
0 Kudos

Dear Satyajit, Ramesh and Senthil,

Thank you very much for your quick reply.

Yes we are executing process chain but before adding step in PC we will test this in our Q system and then in in production.

Thank you very much for your reply.

Amol Chavan

Former Member
0 Kudos

Hi Amol,

1) What the things we should check first ?

a) Check inbound and outbound queues and clear all

b) Check all sysfails and clear all

c) Inform master data planners not to carry out any maintenance during this period of SNP job

d) The recommended practice is that cif blocking and reopening can be done during night times where the end users will be very less

e) During CIF blocking time, ensure no major planning runs are getting executed in background

f) Block the CIF queues

g) Carry out SNP optimiser run

h) Once run is completed, open up the queues

i) Clear all inbound and outbound queues

j) Check all sysfails and clear it

k) Inform master data planners and end users to start carrying out transactions.

2) If we are blocking the queues will queues will be in waiting status or sysfail ?

a) Queues will be with status STOP and WAIT during blocking.

Regards

R. Senthil Mareeswaran.

sumaghosh
Participant
0 Kudos

Hi Senthil,

The stopped queues in /n/sapapo/cq should be deleted or not before running the job /SAPAPO/CIFSTARTQUEUES.

If we delete them what will be the consequences?

Please help.

Thanks.

aparna_ranganathan
Active Contributor
0 Kudos

Amol ,

Here are the answers to your questions

1) What the things we should check first ?

Before blocking the queue you have to make sure all the master and transaction data CIF jobs are complete. You can put the stop queue job after the master and transaction data CIF boxes , but before the SNP planning box. When this is done only the transaction data that gets created in ECC when SNP planning is running , will get blocked in ECC . After the SNP planning box you can put a job to remove the stop status (RSTRFCQ3) . Once you remove the stop status the waiting queues (the status will be stop) will get pushed to APO automatically

2) If we are blocking the queues will queues will be in waiting status or sysfail ?

When you execute program RSTRFCQ1 , a queue entry will be created with status "STOP" . All other queue entries that are created after this will also have the status "STOP" .

Thanks

Saradha

Former Member
0 Kudos

Hi Amol,

Please schedule CIF block job (/SAPAPO/CIFSTOPQUEUES) in se38 before optimizer run and after optimizer run got finished you unlock queues by (/SAPAPO/CIFSTARTQUEUES).

If you are using job schedular then keep cif block job before optimizer job and cif unlock job after optimizer job. Or you can use process chain also.

We use to do the same thing (one of My previous project)

There are many reason for sysfail ..but It was very effective ...

Thanks,

Satyajit