> 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/diagnostics/sap-ccms-missing-data.md).
# SAP CCMS Missing Data
### Problem
Sometimes, CCMS monitoring data is missing or invalid in RZ20 and thus affects monitoring within SAP as well as from external management from IT-Conductor.
### Troubleshooting
Follow these SAP-recommended steps to troubleshoot:
1. Activate Background Dispatching.
* Call transaction RZ21.
* The system displays the **Monitoring: Properties and Methods** screen.
Choose **Technical Infrastructure → Local Method Execution → Activate Background Dispatching**.
Note that not only does the job SAP\_CCMS\_MONI\_BATCH\_DP run under your user name but also the data collection methods that are started by this job. You should therefore ensure that your user has the authorizations required for this. The authorizations are combined in SAP\_BC\_BASIS\_ADMIN. (See [Central Monitoring with CCMS](https://help.sap.com/saphelp_sm71_sp13/helpdata/en/c8/40a442b024b211e10000000a155106/frameset.htm).)
2. Activate Central System Dispatching.
* Call transaction RZ21.
* The system displays the Monitoring: Properties and Methods screen. Choose **Technical Infrastructure → Configure Central System → Activate Central System Dispatching**.
3. In addition, the segment table might be off.
* Choose **Technical Infrastructure → Reorganize Segment Table.**
If nodes in the Alert Monitor are not provided with data, this can be due to monitoring contexts being in an incorrect segment. This is often the case after a system copies or copies from application servers (In most cases, the segment table is also copied).
In this case, select the **Delete all local application server entries** radio button and click the **"Execute"** icon (see also SAP Note 422129). The table is filled with correct entries again within five minutes.
To delete entries for inactive application servers, select **Reorganize local application server entries** and click the **Execute** icon. Use this command if you are no longer using an application server.
---
# 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/diagnostics/sap-ccms-missing-data.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.