Show TOC

Activating Checkpoint GroupsLocate this document in the navigation structure

Use

Overview

The activation of a Checkpoint Group is set differently for Breakpoints, Logpoints, and Assertions. The following operation modes are possible:

  • For breakpoints:

    • Inactive

    • Break

  • For logpoints:

    • Inactive

    • Log

  • For assertions:

    • Inactive

    • Break/Log

    • Break/Abort

    • Log

    • Cancel

Break means that the program stops in debugging mode. However, this is not possible in the following situations:

  • Background Processing

  • Synchronous or asynchronous updates

  • HTTP sessions without external debugging

In these situations, breakpoints are ignored. For assertions, you must select one of the activation states Break/Log or Break/Abort. When debugging is possible, the activation status Break is active. If debugging is not possible, a log entry is created, depending on the selection, or the program terminates with a runtime error.

The activation status of a checkpoint group can be set for:

  • One, more, or all users

  • One, more, or all servers

Overlaps are not possible. If you activate a checkpoint groups at user level, the activation automatically takes effect for all servers. Conversely, an activation on server level results in the checkpoint group becoming active for all users.

A not-inactive actitivity status is time-restricted. After a customizable period of time all activations are automatically set back to inactive.

Activation

A newly created checkpoint group is active by default since in this case no corresponding activation setting has yet been set. To activate a checkpoint group, call either transaction SAAB or, depending on the value of the ID addition, branch to it from the ABAP Workbench using forward navigation.

In transaction SAAB, enter the name under Checkpoint Group (value of the ID addition) and choose Activate. The activation status valid for your user is displayed on the Activation tab. This, therefore, is the user-specific activation setting for your user ID. You can change the activation using the radio buttons. Any changes you make are not active until you save. Then the respective activation settings are created, changed, or deleted.

When selecting the Save option, a dialog box appears where you can enter the maimum length of time that the activity remains valid for. Here you can select between the pre-defined time periods Today and This Week or another time of your choice up to 99 days and 99 hours. The activation period that has been set is then displayed on the Activation tab.

The buttons User and Server allow you to set the activation for different users or servers. You can also make global settings for all users or all servers.

Changes to the activation settings do not affect programs that are already running.

Unlike the checkpoint group itself, the activation settings for a checkpoint group cannot be transported. When a newly created group is transported, it is inactive in the target system by default. If changes are made to an existing group, the activation status in the target system remains unchanged.