> For the complete documentation index, see [llms.txt](https://docs.itconductor.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.itconductor.com/user-guide/monitoring/sap/business-process/bdoc.md).

# BDoc Monitoring

BDocs, short for Business Documents, serve as containers for the data that constitute a business process, such as application messages or transactions. It is a concept specific to the SAP Customer Relationship Management (CRM) system.

BDoc messages are internally transmitted within the CRM Server, facilitating communication between the CRM Application and the CRM Middleware, as well as between the CRM Server and CRM Mobile Clients, also known as Field Applications.

SAP ERP does not incorporate the concept of BDocs, thus preventing the exchange of BDoc messages between an SAP ERP system and SAP CRM. Instead, business data is encapsulated within containers when utilizing BAPI calls. Consequently, when exchanging data with SAP ERP, there are indeed outbound and inbound BDoc messages within the CRM Server, specifically to interact with the inbound and outbound ERP (R/3) adapters.

### Configure BDoc for Monitoring <a href="#configure-bdoc-for-monitoring" id="configure-bdoc-for-monitoring"></a>

1. In the IT-Conductor Service Grid, navigate to the system where you want to enable BDoc monitoring. Then click the object menu of the system.

<figure><img src="https://377464071-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXhp08OmU8050PePmMgDt%2Fuploads%2Fkwa4QVvcN5jWLVTkrJjj%2Fselect-object-menu-of-sap-system-in-itconductor-service-grid.png?alt=media&amp;token=159c816a-562c-449a-b50c-a9583baa1e04" alt=""><figcaption><p>Figure 1: Select Object Menu of SAP System in IT-Conductor Service Grid</p></figcaption></figure>

2. In the object menu, click **Retrievers**.

<figure><img src="https://377464071-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXhp08OmU8050PePmMgDt%2Fuploads%2Fzd3EE2GM5oLaeaDEnhsY%2Fselect-retrievers-in-object-menu.png?alt=media&amp;token=4a44ffad-5488-4fe2-95ce-e36a35f101ff" alt=""><figcaption><p>Figure 2: Select Retrievers in Object Menu</p></figcaption></figure>

3. In the Retrievers list, click the object menu of BDoc Errors. Then click **Activate**.

<figure><img src="https://377464071-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXhp08OmU8050PePmMgDt%2Fuploads%2FBYpE8ahSZgHinvAilPgn%2Factivate-bdoc-errors.png?alt=media&amp;token=bd121a78-8deb-4056-aa4a-68918df9558f" alt="" width="375"><figcaption><p>Figure 3: Activate BDoc Errors</p></figcaption></figure>

4. Navigate to the system in the IT-Conductor Service Grid and expand the BDocs node to view the monitored object.

<figure><img src="https://377464071-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXhp08OmU8050PePmMgDt%2Fuploads%2FsRk57WVXbQX50AkjPJaG%2Fbdocs-monitoring-in-itconductor.png?alt=media&amp;token=940e4396-b9ae-4afe-8dea-44c55c56be21" alt=""><figcaption><p>Figure 4: BDocs Monitoring in IT-Conductor</p></figcaption></figure>

You also have the option to view BDocs in-error directly from the service grid.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.itconductor.com/user-guide/monitoring/sap/business-process/bdoc.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
