Settings and Warnings (SAP Library

Settings and Warnings

From the Debugger, you can set the debugging mode and the system behavior in the event of a kernel warning by choosing Settings.

System Debugging

If you set this option, the Debugger is additionally activated for system programs (programs with status S in their program attributes). When you save breakpoints, the System debugging setting is also saved.

Update Debugging

Update function modules are not processed in the same task as the program that is currently running in the Debugger. Instead, they run in an update work process. These function modules are therefore not included in debugging. You can only debug them if you select the Update debugging option.

In Background Task: Do not Process

When you debug a program that calls function modules using the IN BACKGROUND TASK addition, they are processed in a background work process (additional internal session). If you set the In background task: Do not process option, the system collects the function calls, but does not start the background work process. The Debugger assigns a transaction ID, which identifies the background work process uniquely. You can now start the Debugger for the background work process using Transaction SM58.

Automation Controller

This Debugger option controls the way in which requests to automation objects (Automation Server and GUI controls) are processed.

If the option is not set, the requests are processed as they would normally be in the ABAP program. Requests with the NO FLUSH addition are not processed until

An explicit flush occurs

A request is processed that does not have the NO FLUSH addition.

If you select this option, all requests are processed synchronously, regardless of any NO FLUSH additions.

This helps you to find errors. If an error occurs when the automation queue is being processed, the synchronous request processing allows you to identify the request in which the error occurred.

Enabling this option dramatically affects the runtime of the program, since the ABAP program cannot continue processing until the request has been executed by the receiver. You must bear in mind that the receiver – the automation server or control on the presentation server – may be linked using a slow WAN connection.

For further information, refer to ABAP as an OLE Automation Controller.

Memory Monitoring

After each ABAP statement, the system examines the roll area of the current session. This allows you to check whether neighboring memory areas have been overwritten.

Runtime Warnings

The profile parameter abap/warnings controls the behavior of the R/3 System when a kernel warning occurs. You can display and change it using Transaction RZ11. The Debugger also allows you to override the default setting of this parameter during your debugging session by choosing one of the following options:

Log warnings: Any warnings that occur are recorded and listed in the Debugger under Settings.

Stop at warning: The system stops processing in the line of the program in which the warning occurred.

Dump at warning: The system triggers a short dump when a warning occurs.

You can display the last runtime error to have occurred by choosing Development ® Display last short dump. You can also use the transaction last_shortdump.