Video Lesson 6.2: SAP Code Inspector

Learn ABAP

Video Lesson 6.2: SAP Code Inspector

In this lesson, you will learn about the basic functions and the purpose of the program analysis tool Code Inspector.

The Code Inspector offers you the option of analyzing your programs with regard to performance, security, and typical semantic errors.

Are SELECT statements embedded in loops?

  • Security
    Is data read from a client other than the login client?

Is the database table or the WHERE clause dynamically specified in the SELECT statement?

  • Typical semantic errors
    Is the sy-subrc field checked after each AUTHORITY-CHECK statement?

Is a client actually specified for CLIENT SPECIFIED?

Are several messages of type E (E messages) sent in direct succession?

  • As the result of an inspection you receive a list of error and warning messages.
  • The i button that belongs to the message shows a detailed error description as well as improvement suggestions.
  • Double-click on the error text to branch to the corresponding program statement.->




Video Lesson 6.1 : SAP Runtime Analysis Tool

Learn ABAP

Video Lesson 6.1 : SAP Runtime Analysis Tool

In this lesson you will learn about the basic functions and the purpose of the program analysis tool Runtime Analysis. This is a brief introduction of the tool.

  • The runtime analysis tool makes it possible to take detailed measurements of the runtime requirements of your programs.
  • You can use it to localize low performance source code blocks in your programs and tune them if necessary.
  • However, always note that the measurement results depend on the current system and network load as well as the current table buffer and dataset.
  • You can measure not only programs, but also transactions and function modules with regard to their runtime.
  • Hint: It is advisable to create your own measurement variant with the setting “Aggregation: None” and to use this for the measurement since a detailed analysis of the measurement results is only possible with this.
  • Execute is used to start the runtime analysis.
  • The generated measurement results are stored in a measurement-related file.