on ‎2019 Jan 29 11:44 AM
Hello all,
sometimes happens that CIF queue get blocked due to locked object in target system. It's ok, but in some cases the queue is not reprocessed automatically. It must be done manually.
Any suggestions?
thanks.
Request clarification before answering.
Hello,
You can scheduled the job for report /SAPAPO/RCIFRESTART on Hourly basis.
Or use program RSQIWKEX Queue Name = *
Apart from this use program /SAPAPO/RCIFQUEUECHECK to trigger an email if the queues are blocked.
Best Regards,
R.Brahmankar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
what about if the queue is in 'waiting status'? I scheduled the report /SAPAPO/RCIFRESTART but this does not reprocess the queue. Moreover report /SAPAPO/RCIFQUEUECHECK does not send email for queue in this status?
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI
Please check SMQR for Inbound
Check the Pause value for CF* Queue name , it is the processing time between two intervals .please decrease this value and if required also register the CF* entry again
Thanks
Sunil scM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hello Ayan,
thanks for the answer. there is any way to reprocess the queue automatically with any background job? i found reports RSQOWKEX & RSQIWKEX but i do not think thery works properly...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Matteo
The instance of CIF queues not getting processed automatically is quite a common phenomena. Their could be various reason as to why a particular queue didn't get processed automatically, but all of this are quite normal
1) As you said the object in the target system in locked.
2) A queue may be waiting to be processed as it is dependent on different queue to be processed first. But their is a certain mainframe after which it expires and never gets re triggered automatically.
3) A queue might get blocked and may not get processed automatically, if the RFC destination during the tie of transfer is down or unreachable.
4) Similar behavior can be observed when you get a CPIC error while a CIF queue is getting processed.
All the above are quite commonly occurring phenomena, so it is better to keep a tab using SMQ1 / SMQ2 for both inbound and outbound queues. From APO you can use the tcode /N/SAPAPO/CQ to monitor and re trigger those queues.
Let me know if this clarifies your query
regards
Ayan Bishnu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 12 | |
| 7 | |
| 4 | |
| 3 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.