BDoc (Business Document) messages are used in SAP CRM systems as containers for the data that constitute a business process (application message, transaction). BDoc messages are exchanged internally within the CRM Server between the CRM Application and the CRM Middleware, and between the CRM Server and CRM Mobile Clients (Field Applications). SAP ERP does not know the concept of BDocs, so there is no exchange of BDoc messages between an SAP ERP system and SAP CRM. Instead, the business data is packed into containers during BAPI calls. So during a data exchange to and from SAP ERP, there are in fact outbound and inbound BDoc messages on the CRM Server, but only to communicate with the inbound and outbound ERP (R/3) adapters. Externally the content of the BDoc message is mapped to the mentioned BAPI container structure.

To display BDocs in your system you can use transaction SMW01 or SMW02. 

Technical Prerequisites

The following technical prerequisites have to be met in order to use the BDoc Monitoring:

  • The managed system has an SAP Basis ≥ 7.00
  • The managed system is an ABAP-based SAP CRM system (“CRM Server”) on CRM release 3.0 or higher and SAP Basis release ≥ 6.40.

Advanced Integration Monitoring Setup

Please, select...

To be able to monitor interfaces of an on-premise system you first have to add it to Interface & Cloud Monitoring and select the monitoring categories you want to monitor for the system. 

  1. Open the Advanced Integration Monitoring Application by clicking on the 'Integration & Cloud Monitoring' tile in transaction FRUN
  2. Click on the pinwheel in the upper right corner of the 'Integration & Cloud Monitoring' application
  3. In the configuration panel expand the 'Technical Systems' tray and click on the pen icon in the upper right corner. This will open the 'Integration and Cloud Monitoring - Systems' view. 
  4. If your system is not on the list yet, click the 'Add' button to add it. If it is on the list, click on the system ID of the system. 

In the next step, you see all monitoring categories which are available for the system, depending on the system type and the installed software components. Some recommended standard monitoring categories are preselected.

Select the monitoring categories in scope.

Available Monitoring Categories

The available monitoring categories are:

  • BDoc: BDoc sent to or from the ABAP system (Monitoring transaction SMW01 and SMW02).

Please, select...

After selecting your monitoring categories you have to maintain filters to define what exactly you want to monitor. Some monitoring categories come with standard filters that usually just select all items of this monitoring category. SAP Focused Run can handle this high amount of monitoring data, so you can stick to this standard filters. Or you can set up filters of your own. You can create more than one filter for a monitoring category.

Available Filter Options


For BDoc Monitoring you can collect all BDocs sent or received in the managed system. You can also use the following filter parameters, to restrict the data collection:

  • BDoc Type: Please note that the shorter generation name of a BDoc is used, not the longer description.
  • BDoc State: Status group for the BDocs (Errors, Non-Final, Intermediate State, Rejected, Processed)
  • BDoc State with Description: exact BDoc state. Use input help.
  • Flow Context Direction: BDoc direction (Inbound 'I' or Outbound 'O'). The Flow Context Direction is a broader filter than the Flow Context with Description.
  • Flow Context with Description: Exact flow context for the BDocs. This is a subset of the Flow Context Direction. The data collector will use the wider filter. So if you set 'I' and restrict by an inbound flow context, you will still collect all inbound BDocs
  • Sender/Receiver Site Name: Name of the sender/receiver site
  • Sender/Receiver Site ID: GUID of the sender/receiver site
  • Validation Type: Message validation type (C, E, T, I, X). Use input help.
  • Queue Name: Queue name to be used for message

Please, select...

The setup of the filters for the monitoring categories only makes sure that the data is collected, however, alerts are not created automatically. To create alerts and notifications you have to create an alert individually. If you didn't use specific filters in the setup before, but rather opted to collect all data, you have to create filters for the alerts.

  1. Click on the 'New Alert' button in the upper right corner of the alerts table. A new panel will appear below the table for you to enter the alert information
  2. Select the monitoring category
  3. Select the metric name. The available metrics depend on the monitoring category.
  4. Enter a name for the alert
  5. Enter a name for the filter

In the next sub-step, you have to maintain the filter. The filter values are the same as described above. For some metrics, you have to maintain metric parameters. Find details below in the overview of the available metrics.

In the last sub-step you have to activate the alert:

  1. Check the checkbox next to 'Active'
  2. You can adjust the calculation frequency and the severity
  3. Available threshold types depend on the metric selected. If the threshold type allows it you can adjust the threshold value which triggers the alert.
  4. Select the notification variant and the outbound connector variant from the drop-down list.

For single exceptions, the threshold type is always 'Already Rated'. This means depending on the calculation frequency the number of exceptions is checked and an alert is created if this number is bigger than 0. If you want to reduce the number of alert for these metrics, you could increase the value for the calculation frequency to increase the time between checks.

Available Metrics

For interfaces of type BDoc the following metrics are collected:


  • Number of BDocs in Error Status: Number of new erroneous BDocs found during the collection interval