on 09-06-2012 8:29 AM
Hi Experts,
An Important Bank transaction message is strucked in a Queue and it is not able to restart and can't delete it.How can I process it.Any Help would be appreciated.
Thanks,
Shaik
Hi Shaik,
Please check the status of the queue, it may be stopped.
The XML messages stuck up in the queue are freed by unlocking queues. Please find the step by step procedure to check the message which is stucked in a queue and unlock it.
Step 1: Run t-code: SXMB_MONI
Run t-code ‘SXMB_MONI’ in the R/3 system, which sends data to PI to get the following screen.
Step 2: After executing the above screen as shown above, we arrive at the
Monitoring screen for XML messages to be sent to PI. The message with ‘Green’ colored flag shows the messages are in the queue and are thus scheduled for further processing. Also you can ‘Refresh’ or ‘Restart’ messages as shown in Red Color.
Step 3: If we scroll to the right for a row, then we find the Queue ID as shown below.
Step 4: Click on the Queue ID to take you to following screen.
Step 5: Again drill down to Queue Name – XBTS0005 to take you to following screen .Our main objective is to unlock the queue for the XML messages.
Here, click on the Unlock Button (RED Square) in the above picture to free the XML message stuck up in the queue.
Step 6: Now you can see the change in the status of the XML messages again in the SXMB_MONI.
It’s changed to Checkered Flag.
Please Check the queues using transactions SMQ1 (outbound)/SMQ2 (inbound). Resolve the displayed errors. You can cancel the messages from SXMB_MONI. Execute LUW if necessary and avoid deleting entries manually.
Best Regards,
Sagarika
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sagarika,
The above post is helpful in case of scheduled messages. I have a FEH stuck message which was marked as Complete from /sappo/ppo2 tcode. Now we are not able to take any action on that and it is not allowing me to open the queue id as suggested by you in step 4. Due to this all the subsequent messages for that particular SRM document are getting stuck in scheduled and will not get processed unless the first FEH stuck entry is either discarded or removed.
Please let me know incase there is any way to solve this.
Best Regards,
Mayur
User | Count |
---|---|
83 | |
9 | |
9 | |
8 | |
7 | |
7 | |
6 | |
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.