There is a common requirement from functional consultants on how to do debugging. Below is the raw info on the debugging and different ways of doing it.
Debugging is a common tool used by the technical team to analyze dumps during transactional processing and program behavior. Through debugging we will come to know the run values of the program as well.
Debugging can be performed in two different ways :
1. Debugging by watchpoint
2. Debugging by Breakpoint
Debugging based on watchpoint
At times, we are unsure about how the value is getting determined for a variable then we can put the watchpoint on the variable deriving the value so that the system will stop at all points where the value is being fetched for the variable.
Debugging based on Breakpoint
Debugging based on break point will be done only when the consultant is aware of the exact piece of code where a breakpoint can be enabled.
The breakpoint can be done in two ways.
- Internal breakpoint
- External breakpoint
Internal Breakpoint
- Static Breakpoints
Static breakpoints are always user-independent if there is no specification of a user name. Once a user has inserted the statement BREAK-POINT or BREAK name in an ABAP program, the system always interrupts the program at that point for that user or only for the user name
It is not recommended to use statement BREAK-POINT as it will be applicable for all users and will annoy other users as breakpoint will be triggered for them as well.
Just for that reason, the technical consultant should use statement BREAK as this will enable breakpoint on specific user and breakpoint will not be triggered for other users.
It is not recommended to use statement BREAK-POINT as it will be applicable for all users and will annoy other users as breakpoint will be triggered for them as well.
Just for that reason, the technical consultant should use statement BREAK as this will enable breakpoint on specific user and breakpoint will not be triggered for other users.
External Breakpoint
- Dynamic Breakpoints
Dynamic breakpoints are user-specific. Therefore, you should use them if you only want the program to be interrupted when you run it yourself, not when it is being executed by other users. All dynamic breakpoints are deleted when you log off from the R/3 System.
The breakpoint can be enabled at below different levels:
- Breakpoints at statements
- Breakpoints at subroutines
- Breakpoints at function modules
- Breakpoints at methods
- Breakpoints at messages (Error, Warning or Information)
Comments
Post a Comment