> For the complete documentation index, see [llms.txt](https://docs.sonarsource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonarsource.com/sonarqube-server/analyzing-source-code/languages/abap.md).

# ABAP

ABAP analysis is available starting in commercial editions of SonarQube Server 2026.5.

## Language-specific properties <a href="#language-specific-properties" id="language-specific-properties"></a>

Discover and update the ABAP-specific analysis parameters by going to **Administration** > **Configuration** > **General Settings** > **Languages** > **ABAP**.

## Source code extraction <a href="#source-code-extraction" id="source-code-extraction"></a>

In order to analyze your source code with SonarQube Server you need to first extract it from SAP onto a filesystem. You can use your own tool or an open-source tool; Sonar does not provide any connectors or source code extraction tools.

You can also use [abapGit](https://github.com/abapGit/abapGit) client to manage your project in a Git repository and analyze it directly from your DevOps system.

## Related Pages <a href="#related-pages" id="related-pages"></a>

[Analysis parameters](/sonarqube-server/analyzing-source-code/analysis-parameters.md)


---

# 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.sonarsource.com/sonarqube-server/analyzing-source-code/languages/abap.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.