> 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-cloud/analyzing-source-code/languages/abap.md).

# ABAP

This language is available only in the Enterprise plan. See the [Subscription plans](/sonarqube-cloud/administering-sonarcloud/managing-subscription/subscription-plans.md) page for details.

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

To discover and update the ABAP-specific properties, navigate in SonarQube Cloud to *Your Project* > **Administration** > **General Settings** > **Languages** > **ABAP**. See [Configuration overview](/sonarqube-cloud/analyzing-source-code/analysis-parameters/configuration-overview.md) for more information about setting properties.

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

In order to analyze your source code with SonarQube Cloud you need to first extract it from SAP onto a file system. 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 ALM system.

## In-line suppression of issues <a href="#in-line-suppression-of-issues" id="in-line-suppression-of-issues"></a>

Adding the \* NOSONAR or " NOSONAR comment on the line will suppress all issues on that line.

{% hint style="warning" %}
Rather than relying on this method, we suggest refining your analysis scope to avoid creating major gaps in your code review. Because the `NOSONAR` comment silences all current and future issues on a line without regard for their severity, it is an imprecise tool. Even if you only intend to hide a minor stylistic point, you could unintentionally obscure a serious security flaw.
{% endhint %}

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

* [Analysis parameters](/sonarqube-cloud/analyzing-source-code/analysis-parameters.md)
* [Analysis scope](/sonarqube-cloud/managing-your-projects/project-analysis/setting-analysis-scope.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sonarsource.com/sonarqube-cloud/analyzing-source-code/languages/abap.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.