SAP SXMB_MONI Basic Overview and troubleshooting for SAP Functional Consultants (Non-BASIS)

In this post, we will discuss the basic overview and troubleshooting of SXMB_MONI for Non-BASIS SAP Functional Consultants. We will also cover transaction codes such as SMQ1 and SMQ2.

Overview

• What is SXMB_MONI?
• High Level Process Flow
• Accessing and Monitoring SXMB_MONI
• Downloading Files from SXMB_MONI
• Troubleshooting Queues
• Summary

What is SXMB_MONI?

SXMB_MONI is a transaction code used to access the Monitor for Processed XML Messages screen in SAP. Refer to the screenshot below. This is usually utilized when XML related interfaces are involved. This type of interface is mostly encountered when dealing with Non-SAP or 3^rd party applications that are “linked” to SAP.

It is in this screen or transaction code that we can check / monitor the XML messages going to and from SAP.

For those of you who have background in SAP IDocs, it follows the same concept where you can view the IDoc errors, status, content, etc. in WE02 or WE10 for example.

Some questions that can be answered through SXMB_MONI are the following:

1. Were the messages passed to SAP?
2. Were the messages processed in SAP?
3. Was an error encountered during message processing in SAP?
4. Was SAP able to send messages?
5. What is the status of a certain message in SAP?
6. Are the message flows active and running?
7. Etc.

…but what is an XML?

To keep it simple, think of XML as a formatted message that we send from one system to another. Both systems involved will be able to understand that format because it is in their “language”.

We don’t need to do a deep dive on what an XML is but if you are interested in knowing the technicalities of it, you can read this post.

Key Takeaway: Think of it as a message that follows a certain format. It is how systems can communicate and understand one another.

High Level Process Flow

Earlier we mentioned 3^rd party systems or Non-SAP systems. In the image below, you will notice how both systems involved are able to “communicate” and “send messages” to one another.

We are looking at 2 types of data flow:

1. Inbound SAP : Non-SAP System > SAP PO / PI > SAP
2. Outbound SAP : Non-SAP System < SAP PO / PI < SAP

Accessing and Monitoring SXMB_MONI

Go to transaction code SXMB_MONI, and select “Monitor for Processed XML Messages”.

You will immediately notice 3 Tabs: Standard Selection Criteria, Advanced Selection Criteria, and User-Defined Selection Criteria.

• Standard Selection Criteria

• Advanced Selection Criteria

• User-Defined Selection Criteria      

For this tutorial, we will focus on Standard Selection Criteria because it is the first tab you see by default and it is straightforward to use for those who have no background in BASIS related concepts / functionalities.

Standard Selection Criteria

Focusing on this tab, you will see multiple fields available for your use. The idea here (similar to most SAP screens), is to enter the necessary details to view the data you are looking for. For example, it is a given to enter the dates you are concerned with as well as other key information.

It is okay to enter the dates and immediately click on the Execute button to generate results. If you want to narrow down the search to specific details you need, then it is best to enter related information to filter out the results.

Tip: If you do not know the interface namespace or any other related detail, you may click on the field and click on the “selection” button (encircled in green) to see the available selections.

Receiver vs Sender

We will now focus on 2 areas of this tab: Receiver and Sender. Let us start by understanding the words. Ideally, when we say “Receiver”, it would mean SAP is Receiving Data. On the other hand, “Sender” would mean SAP is Sending Data.

Sender	SAP is Sending Data
Receiver	SAP is Receiving Data

If we add the High-Level Process flow we discussed a while ago, it would follow the table below.

Sender	SAP is Sending Data	Outbound SAP
Receiver	SAP is Receiving Data	Inbound SAP

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.

Overall, the concept just plays around between the 2 key phrases above.

Our Scenario

For a more organized discussion, let us visualize that there is a 3^rd Party System called Finance Exp. It sends expense details to SAP and flows through SAP PO. Once the expense details reach SAP, processing will happen.

Let us say that the processing in SAP will trigger some checks and will post an accounting document. After checks and processing are complete, SAP will send details back to Finance Exp so the system is aware of what happened.

Both Interface Namespace will be “http: // company.com / system / application / finance_exp”.

Let us start with the “Receiver” because we expect Finance Exp to send SAP some expense details. It is the trigger point.

Additional Info: It is possible to have some mapping logic or other processing needs in the SAP PO / PI system. It is also possible that there is no extra processing , mapping, or logic being done in the SAP PO / PI system. As such, it is best to clarify if there are any extra processing on SAP PO / PI system aside from conversion of file or simply “sending” the data to the target SAP system. In our example, we can say that there is no extra processing or logic in SAP PO / PI for simplicity purposes.

Receiver

Check on Inbound Finance Exp XML to SAP ECC

1. Check SXMB_MONI > Monitor for Processed XML Messages
2. Narrow down date and time (Example Dec 13, 2020 – Present Date + 1)
3. Enter Receiver Interface Namespace: http : // company.com / system / application / finance_exp
4. Execute
5. Double click on the highlighted line item under the Namespace column to see the file
6. Click on Inbound Message > Payloads > Select file in concern (Example: MainDocument)

Sender

Check on SAP ECC response back to Finance Exp.

1. Check SXMB_MONI > Monitor for Processed XML Messages
2. Narrow down date and time (Example Dec 13, 2020 – Present Date + 1)
3. Enter Sender Interface Namespace: http: // company.com / system / application / finance_exp
4. Execute
5. Double click on the highlighted line item under the Namespace column to see the file
6. Click on Inbound Message > Payloads > Select file in concern (Example: MainDocument)

General Search can be done in SXMB_MONI by specifying the dates only then Execute.

Downloading Files from SXMB_MONI

In some cases, you may want to download files from SXMB_MONI to help you analyze some errors or data flows. After selecting the file in concern (under Payloads folder), click XML Message > Download Window 2 > SAVE in local PC

You have several options to choose from:

• Download Window 1
• Download Window 2
• Save Entire Message Version

Once downloaded to your machine, you can view the XML document. Another option would be to “Open with Internet Explorer”.

Troubleshooting Queues

You might encounter instances wherein the status would be in “Error”, “Scheduled”, or any other status that is not “Processed Successfully”. If that is the case, you may want to check the queue and see if there are logs for analysis.

You can highlight / select the line you are concerned with and go to Path: Goto > qRFC Monitor. This will bring you to the queue monitor screen.

If you want to directly view inbound / outbound queues, you can go the transaction codes SMQ1 and SMQ2.

SMQ1 – Outbound Queue

SMQ2 – Inbound Queue

Summary

• What is SXMB_MONI? Monitor XML Messages in SAP
• High Level Process Flow – Non-SAP System to SAP PO / PI to SAP (vice versa)
• 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
• Troubleshooting Queues – From SXMB_MONI, Go to SMQ1, or Go to SMQ2

I hope this helps. Good luck! 😊