Scribd
Upload
17 views1 page

Influence The Program Behaviour at Runtime: Implmetation Check and Probability Check o Implemetnation

This document discusses different techniques for influencing the flow of an ABAP program during debugging to focus on specific pieces of code. It describes using goto statements to avoid modifying code to reach the desired section. Breakpoints can be made more powerful by using special dynamic breakpoints that stop at every instance of a specified statement, like AUTHORITY-CHECK, making it easier to identify all authorization checks without manually browsing all code. Conditional breakpoints can also be used to control program flow during debugging.

Uploaded by

sandeep
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
17 views1 page

Influence The Program Behaviour at Runtime: Implmetation Check and Probability Check o Implemetnation

This document discusses different techniques for influencing the flow of an ABAP program during debugging to focus on specific pieces of code. It describes using goto statements to avoid modifying code to reach the desired section. Breakpoints can be made more powerful by using special dynamic breakpoints that stop at every instance of a specified statement, like AUTHORITY-CHECK, making it easier to identify all authorization checks without manually browsing all code. Conditional breakpoints can also be used to control program flow during debugging.

Uploaded by

sandeep
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 1

Implmetation check and probability check o implemetnation.

Influence the Program Behaviour at Runtime


When you are examining the flow of an ABAP program in the debugger and you aim to focus on a
certain piece of it only, it may happen that the specific case you’re investigating only occurs under
certain circumstances (e.g. certain variables having certain values). In such a case you have to
invest time to modify everything so that the debugger reaches the piece of code you’re interested in.

Avoiding this effort (time is money) you can leverage the simple, but nevertheless very valuable,
feature named Goto Statement.

Make your Breakpoints more powerful


Breakpoints allow the developer to specify in which code line the debugger should stop.

Typically you choose one particular code (e.g. line x in program z) because you want to inspect the
program flow around this code. Besides such dynamic breakpoints you can leverage special
dynamic breakpoints and conditional breakpoints to make your debugging experience easier.

Special Dynamic Breakpoints

Assume we require to identify all authorization checks conducted during a program flow. We know
that AUTHORITY-CHECK is the respective ABAP keyword. How do we solve this challenge?

Firstly, we could execute the ABAP program in the debugger and follow the program flow by hand.
After browsing through all methods, function modules etc. we have noted down all authorization
checks. Apparently this approach is time-consuming and also error prone as you never know if you
have missed some piece of code deep in the call stack.

Secondly, as an advantageous approach you can leverage special dynamic breakpoints (that’s the
official name according to the documentation). This feature let’s you create breakpoints at every
instance of a certain e.g. statement, exception, or function module.

In order to define special dynamic breakpoints, choose Breakpoints -> Breakpoint At in the debugger
menu. Choose Breakpoint at Statement with regards to our example. In the appearing pop-up we
enter the name of the command.

You might also like