SXMB_MONI SAP tcode for – Integration Engine – Monitoring. Here we would like to draw your attention to SXMB_MONI transaction code in SAP.As we know it is being used in the SAP BC-XI (Exchange Infrastructure in Basis) component which is coming under BC module (BASIS).SXMB_MONI is a transaction code used for Integration Engine – Monitoring in SAP.
Execute SXMB_MONI tcode and give filter values as below (Depends on your requirement) Click on Save. Give the Variant Name and Desc. Only for Background Processing :If you select this check box then variant can only be executed in the background .Otherwise,it can be run both in the background and dialog mode. Protect Variant :If you select this ...
Note: This how I have encountered the concept / behavior of SXMB_MONI across different clients throughout my career. If a different approach was implemented in the SAP system you are concerned with, it would be best to personally analyze between the two, so you get the right analogy for your work / task.
I am new to SAP-XI. I am working in XI-Production.My job is monitor the XML Messages in production system with SXMB_MONI. I have some doubts. 1) How to put the job on hold in tidal production. Why we have to put job in hold. 2) What will be happend if any XML messages are in INBOUND QUEUE (SMQ2) and what we have to do. what is inbound queue.
SAP-TCodes.org web site content is based on our knowledge of SAP system, and it is constantly reviewed to avoid errors; well we cannot warrant full correctness of all content.
From SAP Note 742324 – New authorization concept. we can learn that in order to use authorization concept for XI message monitoring we should use S_XMB_MONI authorization object instead of S_XMB_DSP . As a start we can copy standard role SAP_XI_MONITOR_ABAP for displaying XML messages (TCODE – PFCG):
SXMB_MONI – Integration Engine: Monitoring Posted by ITsiti — March 31, 2019 in SAP BASIS — Leave a reply Transaction code SXMB_MONI is used to monitor the processing of XML messages, as well as to track message errors and statutes.
For latest accurate dates and times, please check out the referenced, and non-referenced information available from SAP. Update: With SAP Notes 3101750 and 3101780 also the sender interface name is introduced. The purpose and usage is analogues to the receiver (e.g. instead of receivernametable use sendernametable) interface name.