Deletion of APO Inbound and Outbound queues

[emani_raghavendra]

Hi All,

We want to delete the APO Inbound queue and Outbound queues on weekly basis in Background , so that the job can be scheduled.

I know that there are 2 programs for this purpose :

RSTRFCIDS-delete inbound queues

RSTRFCQDS-delete outbound queues

But the issue with these programs, they are not taking GENERIC QUEUES ( Like we can't give * or C* in Queue name ). We hae many queues and its not possible to give all the queue names and scheule thousands of background jobs . ( One job for each queue name ) . So , is there any other solution where the program do accept generic queue names ?

Thanks a lot for your support !!!

Regards,

Venkata Emani

[Former Member · Accepted solution]

Hi Venkata

As suggested by other experts, deletion of queue is not advisable. If you are getting too many failed entries, then whole CIF design should be re-looked. Please also make sure that you have implemented housekeeping activities e.g. Delta report followed by manual correction of delta, CIF Monitoring and CIF postprocessing. A combination of these activities should minimize failed entries. Saving a queue is a better option than deletion so that you can analyze it later. If you still want to delete, probably its better to do it after reviewing the entries and using TCode SMQ1 or SMQ2.

Thanks,

Prasun

[emani_raghavendra · Accepted solution]

Hi All,

As part of our APO Performance, we are deleting teh queues. We haven't analyzed queues till now but we are deleting them from manually SMQ1 and SMQ2 on weekly basis. We are in the process to analyze the queue and process it so that it should not appear next week. I have few questions here , if anyone would help me --->

> I have some queues showing error that " Material status does not allow a planned independent requirement ". I understand that this might be due to the setting in R/3 Plat Sp. Matl Status. But how do i know for which material this error is showing ?? I mean , what was the material under this Queue ..? I have clicked on the queue name and then again on the user , but i didnt find any details.

> We are using only Demand Planning in APO. So could CIF Reports like Reconcilition / CIF Post Processing help me to anayze the differences in APO and R/3 system ?

>  Last Doubt, Suppose a Queue Fails .... What happens to the queus after teh failed queue ? Will all other also fail ??

Thanks.

Regards,

Venkata Emani

[babu_kilari4 · Accepted solution]

Hello Emani,

I mean , what was the material under this Queue ..? I have clicked on the queue name and then again on the user , but i didnt find any details.

If you need to know what is the material for which you're getting this error, you need to display the contents of the queue. Simply double click on the CIF queue to the lowest possible level of LUW and double click again on the queue name and you will be able to see the content of the queue.

We are using only Demand Planning in APO. So could CIF Reports like Reconcilition / CIF Post Processing help me to anayze the differences in APO and R/3 system ?

This completely depends on the type of the error you're actually seeing in the system. As a generic and regular practice scheduling these jobs will highly reduce the inconsistencies. There could still be some errors which cannot be fixed by running these reports. Those errors could be due to incorrect maintenance of master data in the system and system should have been setup properly as per the business need.

 Last Doubt, Suppose a Queue Fails .... What happens to the queus after teh failed queue ? Will all other also fail ??

This totally depends on the CIF Configuration that you would have made initially during the CIF setup. If all the queues fall into one logical unit of work and if there is an error, I guess the dependent queues would not proceed further unless the errored out queue is fixed or saved.

But, please note that one should never delete the queues in SMQ1 and SMQ2. More the no. of queues that you delete, more the no. of inconsistencies between ECC and APO. Save the queues by getting to the lowest possible LUW level and identify the root cause.

Hope this helps.

Babu Kilari

[rupesh_brahmankar3 · Accepted solution]

Hi Emani,

In SAP APO you have the SCM Queue Manager in transaction /N/SAPAPO/CQ  execute the transaction you will get the queues with error message  Material status does not allow a planned independent requirement.

Select the queue and click display queue(last button) in side you can get the material number.

In the R/3 and APO SAP systems, you can analyze the application log using the following transactions:

SAP R/3 transaction CFG1 and SAP APO transaction /N/SAPAPO/C3

You can use the Report /SAPAPO/CCR here by select Planned Ind Requirement you will get the products having issue to CIF to ECC.

The Deltareport has not been designed to reconcile inconsistencies for Planned Independent Requirements. It only displays the inconsistencies found for PIR.

CIF error handling is not implemented for transferring planned independent requirements between SAP APO and SAP R/3 this means that processing errors in the receiving system still result in incorrect queue entries.

Please refer below link CIF best practices.

https://websmp202.sap-ag.de/~sapidb/011000358700000715082008E

Regards,

R.Brahmankar

[Former Member · Accepted solution]

Hi Venkata

You have reported that you are using only Demand Planning. So what are Master and Transaction data are you using for CIF? Are you trying to transfer forecast from APO DP to ECC as PIR?

I belive your question on display of queue and queue failure is already answered by other experts. Delta report or postprocessing would help to reconcile data. However, if there is large number of errors, root cause might be inaccurate configuration or wrong Master data set-up. With only Demand Planning, I would not expect too many issues in CIF (I am assuming you are transferring very few transactional data).

Thanks,

Prasun

[satish_waghmare3]

Hello Venkata

Data Consistency is the ultimate aim of CIF.  As mentioned by other experts,  Deletion of queues leads to data inconsistencies.

If there are in any unwanted queues getting created, then you should rather validate the integration models which is trying to transfer this unwanted data to APO. This should reduce number of such queues to some manageable number.

For your requirement I think Tcode. /SAPAPO/CQ - SCM Queue Manager is more appropriate, where you can verify the Error Text and then based on that multiple queues can be deleted with a single click. Yes, this is requires a manual action.(not possible to do it bkgrd).

Please let us know, reason for your requirement - why you are deleting CIF queues in such a high number.

Thank you

Satish Waghmare

[Former Member]

Hi Venkata,

In a well-designed ERP/APO system, every queue is important and should be processed. Deletion of queues leads to system inconsistencies. I'm curious as to why you are deleting queues.

Best regards,

Mike

[rupesh_brahmankar3]

Hi Emani,

By entering TID = *, all LUWs are deleted in all queues, and the entry under 'Delete queue' is no longer taken into account.

Now delete the inconsistent TID directly from the delta queue SMQ1. Also see note 760113 and 763255 for the deletion.

Queue name - This parameter is mandatory for performance reasons. The queue name designates the queue, in which the LUW to be deleted is located, which must be fully specified.

Note: If a LUW is located in several queues, the specification of a single queue is sufficient, and the LUW is then also deleted from all of the other queues.

Regards,

R.Brahmankar