Monitoring Messages Across All Systems

The initial contact with the Data Replication Framework log happens during manual data replication using transaction DRFOUT. After transmission, the log shows which filter criteria were used and which objects were identified as a result.

The previous screenshot displays the different views of the log.

1. The overview screen in the upper left appears after data is sent. The marked row (A) lets you see more details.
2. The details screen on the right provides insights about the considered filters, affected objects (B), and, in some outbound implementations, even the messages that were created (C). Selecting the View Details button for such entries takes you to the web service message monitor (SRT_MONI).
3. This screen contains details of selected objects.

The Data Replication Framework log can also be accessed directly through the transaction DRFLOG. This transaction provides details on replications initiated by automatic replication, meaning due to the creation or modification of data. This can help you verify if filter settings (transaction DRFF) function correctly and assists in identifying potential issues.

For inbound messages, the application log, accessible with transaction code SLG1, can help analyze errors that occur during processing at the application level.

You can monitor web service-based communication using transaction SRT_UTIL. From this transaction, you can access the Error Log or the Message Monitor, and even initiate more advanced features, such as payload or functional traces.

The message monitor can also be accessed directly via transaction SRT_MONI and the error log using transaction SRT_ELOG. Although the message monitor displays messages in the states successful, processing, and error, some kinds of errors only appear in the error log. Therefore, if you‘re having trouble finding a message, you should always check both logs.

The previous screenshots display the monitoring capabilities for web service messages:

1. Web Service Utilities (SRT_UTIL) with buttons to access the Error Log and the Message Monitor.
2. Message Monitor (SRT_MONI) displays messages that have been processed or are currently being processed.
3. The toolbar at the top allows you to view the XML payload of a message, see error details, restart messages with errors, cancel messages that are in processing state, and much more.
4. Details view of a message that can display additional error information or the payload.

Several transactions with different features are available for monitoring IDoc-based communication. With transaction WE02, you can list IDocs of all processing states based on their direction (inbound or outbound) and type. You can also view the payload (look into the IDoc) by double-clicking on the respective row. The following screenshot shows that.

Alternatively, you can use transaction BD87 to access another monitor where you can select IDocs based on their processing status. This transaction also allows you to process IDocs that have not yet been processed. Without transaction BD87, you need to use a program to select and process IDocs.

Processing and monitoring are one of the main tasks of a middleware. In Cloud Integration, you can access the message processing log through the navigation menu under Monitor→Integrations and APIs.

The overview screen, partly shown in the following screenshot, consists of several tiles that display the number of processed messages matching different criteria, such as completed, failed, retried, etc., messages during different time frames, such as within the past hour, within the past 24 hours, and so on. You can customize the tiles or add new ones.

Selecting a tile takes you to the message monitor with the relevant filters applied. Choose a message to view more details, such as the sender and receiver, the message or application message ID, existing logs, and more.

Unlike other systems, you cannot see the contents of a message in Cloud Integration by default. However, you can temporarily activate the Trace mode for integration flows to record such details during message processing and view it for a limited time.

The Trace mode can be activated in the Manage Integration Content area (1) within the Log Configuration section. Once activated, it stays active for a limited time, usually 10 minutes. During this period, a detailed message log is generated for messages processed, including payload and header data at each internal processing step. You can view these details in the Monitor Message Processing area after selecting a processed message (2). The trace data is typically retained for one hour.

Depending on your user roles on SAP BTP, you might be able to activate the trace mode, and see some details for each processing step, such as the processing time, but you may still not see the Message Content. The following screenshot shows this situation, where the message You are not authorized to view trace data. Contact your tenant administrator for permissions. is displayed instead.

In such a case, your user needs a different or additional user role. Common examples are:

• Role collection PI_Integration_Developer allows you to carry out most tasks in Cloud Integration, such as integration flow deployment and message monitoring, but doesn't give you access to the message content.
• Role collection PI_Business_Expert allows you to monitor messages, including the message content (payload)

You can find more about roles in the SAP Help Portal.

In the following video, a sample product is sent, and we track the message across the systems using each system's monitoring tools.

1. The product is sent from SAP S/4HANA using transaction DRFOUT.
   1. The Data Replication Log appears after triggering the replication. Alternatively, you can open the log with transaction DRFLOG.
   2. The web service message monitor in transaction SRT_MONI can be used to verify that the message was successfully sent to the middleware. You can use the Message ID to track a message across subsequent systems.
2. In Cloud Integration, you can view processed messages under Monitor→Monitor Message Processing. You can find the message by entering the message ID into the ID field. The properties section refers to it as Application Message ID.
3. In SAP Sales and Service Cloud Version 2, the Message Monitor is located within the Integration card in the System Settings. You can Search by Message ID to find the message.
4. Since the message was processed successfully, the product can be viewed in the Products app.