Starting the ABAP Profiler
- Run your program before profiling it: It's a good idea to run your program at least once before you launch the ABAP Profiler. That way, any side-effects of compilation, initialization of caches, or other time-users, are eliminated before you actually create an ABAP trace (result of the ABAP Profiler).
- By starting the ABAP Profiler for an individual ABAP program directly
from the source editor or from the Project Explorer view.
More on this: Launching Profiler for an ABAP Program
- By launching the profiler wizard tool - independently of any context, you can select an arbitrary development object to be profiled.
More on this: Creating an ABAP Trace Using a Wizard
-
By creating a trace request. Certain programs or program units cannot be started directly as ABAP applications. As an alternative to profiling such a program in its ABAP Unit tests, you can create a trace request and profile a method or function module whenever its execution is triggered in the back-end system by a transaction, HTTP request, RFC call, or within a background process
More on this: Creating an ABAP Trace Request
-
By using a predefined launch configuration for the ABAP Profiler
More on this: Working with Profile Configurations
- Other ways to start the ABAP Profiler for a program that you cannot
start directly:
- By using the debugger to start or stop the ABAP Profiler.
More on this: Starting and Stopping the ABAP Profiler in the Debugger
- By embedding code that includes the method or other object that you want
to profile in an ABAP PROGRAM. You can then use the standard option
Profile As 
ABAP Application 
to profile the method.
- By using the debugger to start or stop the ABAP Profiler.