SonarSource Rules
  • Products

    In-IDE

    Code Quality and Security in your IDE with SonarQube Ide

    IDE extension that lets you fix coding issues before they exist!

    Discover SonarQube for IDE

    SaaS

    Code Quality and Security in the cloud with SonarQube Cloud

    Setup is effortless and analysis is automatic for most languages

    Discover SonarQube Cloud

    Self-Hosted

    Code Quality and Security Self-Hosted with SonarQube Server

    Fast, accurate analysis; enterprise scalability

    Discover SonarQube Server
  • SecretsSecrets
  • ABAPABAP
  • AnsibleAnsible
  • ApexApex
  • AzureResourceManagerAzureResourceManager
  • CC
  • C#C#
  • C++C++
  • CloudFormationCloudFormation
  • COBOLCOBOL
  • CSSCSS
  • DartDart
  • DockerDocker
  • FlexFlex
  • GitHub ActionsGitHub Actions
  • GoGo
  • HTMLHTML
  • JavaJava
  • JavaScriptJavaScript
  • JSONJSON
  • JCLJCL
  • KotlinKotlin
  • KubernetesKubernetes
  • Objective CObjective C
  • PHPPHP
  • PL/IPL/I
  • PL/SQLPL/SQL
  • PythonPython
  • RPGRPG
  • RubyRuby
  • RustRust
  • ScalaScala
  • ShellShell
  • SwiftSwift
  • TerraformTerraform
  • TextText
  • TypeScriptTypeScript
  • T-SQLT-SQL
  • VB.NETVB.NET
  • VB6VB6
  • XMLXML
  • YAMLYAML
ABAP

ABAP static code analysis

Unique rules to find Bugs, Vulnerabilities, Security Hotspots, and Code Smells in your ABAP code

  • All rules 94
  • Vulnerability4
  • Bug14
  • Security Hotspot7
  • Code Smell69
Filtered: 12 rules found
convention
    Impact
      Clean code attribute
        1. Asterisks should be used for headers and to comment out code

           Code Smell
        2. "DATA" variable names should comply with a naming convention

           Code Smell
        3. Report names should comply with a naming convention

           Code Smell
        4. Macro names should comply with a naming convention

           Code Smell
        5. Function names should comply with a naming convention

           Code Smell
        6. Form names should comply with a naming convention

           Code Smell
        7. Statements should be on separate lines

           Code Smell
        8. Interface names should comply with a naming convention

           Code Smell
        9. Tabulation characters should not be used

           Code Smell
        10. Lines should not be too long

           Code Smell
        11. Class names should comply with a naming convention

           Code Smell
        12. Method names should comply with a naming convention

           Code Smell

        Report names should comply with a naming convention

        consistency - identifiable
        maintainability
        Code Smell
        • convention

        Why is this an issue?

        Shared naming conventions allow teams to collaborate efficiently. This rule checks that all [report/]program names match a provided regular expression.

        Noncompliant code example

        With the regular expression ^([A-Z0-9_]*|[a-z0-9_]*)$:

            IDENTIFICATION DIVISION.
               PROGRAM-ID. MY-PROGRAM.      *> Noncompliant
        

        Compliant solution

            IDENTIFICATION DIVISION.
               PROGRAM-ID. MY_PROGRAM.
        
          Available In:
        • SonarQube IdeCatch issues on the fly,
          in your IDE
        • SonarQube CloudDetect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories
        • SonarQube ServerAnalyze code in your
          on-premise CI
          Developer Edition
          Available Since
          9.1

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use