1. SAP Support Portal Home
  2. Application Lifecycle Management
  3. SAP Focused Run
  4. SAP Focused Run Expert Portal
  5. Integration & Cloud Monitoring

BDoc

Bdoc

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

Available Monitoring Categories

The available monitoring categories are:

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

Available Filter Options

BDoc 

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
 

Available Metrics

For interfaces of type BDoc the following metrics are collected:

BDoc 

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