Dynamic Logpoints in ABAP 
Logpoints indicate to the ABAP runtime that an ABAP program is to execute a custom action at a certain point within the program.
When the logpoint is reached during program execution, the logpoint is evaluated. The logpoint evaluation first checks the condition. If the condition is fulfilled, a log entry is written according to the specified logpoint parameters.
You can define logpoints by writing the LOG-POINT statement in an ABAP program (static logpoint) or by setting a dynamic logpoint at a certain location in the source code, without having to modify your source code.
Dynamic logpoints have been introduced in order to support logging in quality or productive systems where the source code cannot be changed. For example, you have found a location in the source code for which you need additional monitoring details, or you may be facing a poorly localizable error situation that happens from time to time in a batch job and cannot be debugged.
- Like a breakpoint, in the source code editor
- At any source code line that contains an executable ABAP statement.
- To store variable values in the context of a defined ABAP program line if a certain condition is fulfilled.
- To analyze execution of an individual Open SQL statement that you found in SQL Monitor in the context where a certain condition is fulfilled.
- To view the call stack for a specific ABAP program line where a certain condition is fulfilled.
- To activate SQL tracing for an individual Open SQL statement in order to be able to analyze performance issues in detail.
- To activate table buffer tracing for memory consumption analysis at a dedicated Open SQL statement.
- Active logpoints - When an active logpoint is reached during program execution, the logpoint is evaluated.
- Inactive logpoints - Inactive logpoints are ignored during program execution.