on 07-01-2009 8:16 AM
Hi,
For a few inbound interfaces for which PI is the middleware, we have found that the messages are stuck in queue in PI. We have also found that the messages are stuck in the queue in PI because one message which has an RFC error (It does a RFC lookup from PI into R/3).
Is there any way in which we can trigger the RFC lookup manually for the failed message in the queue in PI?
If this is not the right forum, please let me know the correct forum.
Thanks in advance.
Mick
We have also found that the messages are stuck in the queue in PI because one message which has an RFC error (It does a RFC lookup from PI into R/3
Check if you can Restart the failed message.....click on the processing entry (in SXMB_MONI)for the message and then click on the Restart option available on the top.....then if the cause of error has been solved your message will be processed...or you can even cancel the message processing (click on the symbol with a pencil and a green tick mark on top of it)...
Not all failed messsages can be restarted in this manner.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Mick
depending on the exact reason for the failure you can go into and edit the message content within the RWB - Message Monitoring - select failed message - and you can edit the message content to then restart the failed message.
http://help.sap.com/saphelp_nwpi71/helpdata/en/45/c9c6c57e745708e10000000a114a6b/frameset.htm
Thanks everyone. The issue is resolved.
The issue was with RFC function modules in R/3. PI makes and RFC calls to these RFC FM in R/3. These RFC function modules were modified and therefore the messages in PI were in error and stuck in the queue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
We can prevent this problem through standard SAP program RSQIWKEX. This program need to execute background. Whenever any message stuck in queue automatically this problem will restart error message automatically. If you want to delete error message from queue (due to this error message remaining messages are in hold stage. for remaining message execution we need to delete error message from queue) we need to change one function in this probem.
Existing function TRFC_QIN_RESET_LUW , this function only can restart error message.
Need to add function TRFC_QIN_DELETE_LUW , this function delete error message from queue.
For this program execution we need to mentioned queue name(mandatory), find message stucking queue name and give same name to program in variant.
I hope now clear
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
83 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.