Show TOC

Layer ProfilesLocate this document in the navigation structure

Use

A layer profile combines the Object Sets relevant for you. When you use a profile, you can also define the debugger behavior by specifying the following characteristics of the relevant object sets:

  • Visibility

    Relevant for the debugger step Single Step (F5). The debugger stops when the relevant code is entered. The code is visible and you can debug it in normal steps (for example single steps). This is pretty much like dynamically assigning the attribute System Code to non-relevant ABAP code. For example, if you perform a debugger single step on a method call into an object set with a visibility indicator that is not selected, in this case, the debugger does not step into this object set, but stops at the next ABAP code line of a visible object set instead.

  • Point of Entry:

    Relevant for the debugger step Single Step (Ctrl + Shift + F5). The debugger stops when the code of the specified object set is entered. This function is useful if you want to debug the code in big steps, jumping from layer to layer or from component to component.

  • Point of Exit

    Relevant for the debugger step Single Step (Ctrl + Shift + F5). The debugger stops right after the code of the specified object set is exited. This function is useful if you want to debug the code in big steps, jumping from layer to layer or from component to component.

  • Including System Code

    This function allows you to include all the system programs of the object set.

Each debugger profile contains a predefined object set called <<%REST%>>. This object set includes all ABAP code that is not part of the self-defined object sets of the profile. You can specify the debugger behavior concerning the <<%REST%>> object set.

You can delete the <<%REST%>> object set. This is especially useful if you are only interested in the calls between the object sets defined in the profile.

Example

You have defined two object sets: OM FI and OM HR and you have selected the Point of Entry indicator for OS HR. If you have included the <<%REST%>> object set, the debugger stops every time when OS HR is entered. In this case, it does not matter whether the OS HR is entered from OS FI or from <<%REST%>>. If you delete the <<%REST%>> object set and select the Next Object Set debugger step, then the system stops only when OS HR is entered from the OS FI object set.

Caution

If the characteristic Including System Code is switched off for the <<%REST%>> object set, then the relevant system programs are not part of the <<%REST%>>. In this case, the system programs are treated as described above for the case where the <<%REST%>> object set is deleted.

More Information