> 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/idoc.md). # IDoc Monitoring IDocs, short for Intermediate Document, serve as standardized containers for the exchange of data between applications. Within SAP applications, this data interchange is facilitated through the Application Link Enabling (ALE) layer, which, in turn, employs either tRFC or File technology as its underlying methods. A single IDoc contains different types of information, such as application data intended for exchange (e.g., sales order) and technical data including source and target information. IDocs also contain status information that shows the current processing stage of the data exchange. ### Configure IDoc for Monitoring 1. In the IT-Conductor Service Grid, select the system where you want to enable IDoc monitoring.

Figure 1: Select SAP System in IT-Conductor Service Grid

2. Click **IDoc Monitors** from the available tools as shown in Figure 2.

Figure 2: Select IDoc Monitors

3. Click the **Create new IDoc Error Monitor** icon to create a new object and add monitoring for a new message type.

Figure 3: Create New IDoc Error Monitor Icon

4. In the New IDoc Error Monitor wizard, fill out the “Message Type” field. Then click the **Create new SAP IDoc Error Count Retriever** icon to save.

Figure 4: New IDoc Error Monitor Wizard

A new retriever is generated, and the message type is appended to the defined name.

Figure 5: IDoc Monitors List

5. Navigate to the system in the IT-Conductor Service Grid to view the monitored object.

Figure 6: IDocs Monitoring in IT-Conductor

You also have the option to view In-Error IDoc Count for specific message types 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/idoc.md?ask=&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.