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: 8 rules found
brain-overload
    Impact
      Clean code attribute
        1. Cognitive Complexity of functions should not be too high

           Code Smell
        2. Cyclomatic Complexity of functions should not be too high

           Code Smell
        3. Loops should not contain more than a single "CONTINUE", "EXIT", "CHECK" statement

           Code Smell
        4. Control flow statements "IF", "CASE", "DO", "LOOP", "SELECT", "WHILE" and "PROVIDE" should not be nested too deeply

           Code Smell
        5. Cyclomatic Complexity of classes should not be too high

           Code Smell
        6. Magic numbers should not be used

           Code Smell
        7. Expressions should not be too complex

           Code Smell
        8. Files should not have too many lines of code

           Code Smell

        Loops should not contain more than a single "CONTINUE", "EXIT", "CHECK" statement

        adaptability - focused
        maintainability
        Code Smell
        • brain-overload

        Why is this an issue?

        Restricting the number of CONTINUE, EXIT and CHECK statements in a loop is done in the interest of good structured programming.

        One CONTINUE, EXIT and CHECK statement is acceptable in a loop, since it facilitates optimal coding. If there is more than one, the code should be refactored to increase readability.

        Noncompliant code example

        DO counter TIMES.
          IF sy-index = 2.
            CONTINUE.
          ENDIF.
          IF sy-index = 10.
            EXIT.
          ENDIF.
          WRITE sy-index.
        ENDDO.
        
          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