Hi Everyone, have a message stuck in scheduled status in sxmb_moni in ECC. But i cannot view the same message's queue in smq2 or smq3(message is received by ECC).
Go to SXMB_MONI Find the scheduled XML and click on the "Queue Name" This will bring you to the SMQ2 transaction (inbound queue monitor) Now it is time to find why the queue which has the scheduled XML is stopped! Click on the queue name again In this case, the queue has status SYSFAIL, meaning something is impeding the queue to be processed.
The case is at ERP side running transaction SXMB_MONI, some XML messages from XI to ERP are found in "Scheduled" status. Around the same time, siimilar messages using same receiver interface are processed successfully. When we manual restart the "Scheduled" message, there will be an entry in READY status at inbound queue and we have to unlock the queue.
It is not possible to restart a XML message in Scheduled status from SXMB_MONI. It is occurring because the queue was deleted and it turned the document inconsistent. It is possible to see by the option qRFC Monitor. When you try to process the document pressing the button "Restart", the message "Restart no longer possible" is displayed. Read more...
Accessing and Monitoring SXMB_MONI – Go to the transaction code SXMB_MONI, Select “Monitor for Processed XML Messages”, Enter key details you need to view the messages in concern, and then Execute. Downloading Files from SXMB_MONI – Select the file in concern, click XML Message > Download Window 2 > SAVE in local PC
Message Scheduled for Outbound Processing. Sometimes for asynchronous interfaces in sender side, in SXI_MONITOR, your message remains in status Scheduled and is marked with green flag. This always needs to be investigated and a common reason is that the message is stuck in a queue. In such case the queue has to be unlocked which can be achieved following below steps.
SXMB_MONI – Integration Engine: Monitoring. Transaction code SXMB_MONI is used to monitor the processing of XML messages, as well as to track message errors and statutes. Message throughput can also be monitored. Monitoring initially helps the system administrator to monitor their system and at the same time it is used by the application as a ...
The message is scheduled as well as released for processing. Additionally, ABAP monitoring differentiates whether the database Commit has already been issued or not. Depending on this, the status is temporary or final. ABAP monitoring: "Message scheduled (commit follows)", "Message scheduled (commit missing)".