Debugger Execution Types (SAP Library - Transformation Editor)

Debugger Execution Types

In debugging mode, you can have the source text of the XSLT program to be analyzed run through in different execution types. Quick access to the corresponding functions is possible through the buttons in the application toolbar in the XSLT debugger.

The table below gives a detailed description of the individual pushbuttons:

Icon / Key Combination	Function	Description
F5	Single step	Executes the XSL transformation for each statement. If there are statements that cover further steps, the debugger goes into each individual step. Refer also to the note for this function (see below).
F6	Execute	Executes the current XSL statement completely. In statements that cover further process steps, the debugger does not go into each step sequence, in contrast to the single step above. The Debugger groups all the process steps of the current statement together and executes them completely. This function is important for statements such as. <xsl: apply-templates ..../> and <xsl: call-template>, or whenever named blocks are called (templates, functions). Refer also to the note for this function (see below).
F7	Return	Returns to the place where the calling XSL template takes over control. This function is provided for all situations where you wish to leave the current template and return to the calling template.
Source CTRL + F8	Continue up to next source node	Executes the XSL transformation from the current position up to the next node in the XML tree to be processed. This function therefore allows step-by-step processing along the tree hierarchy for the current XML document.
Result SHIFT + F8	Continue up to next result change	Execute the XSL transformation from the current position up to the next result change.
F8	Continue	Executes the XSL transformation up to the next breakpoint. The breakpoint line becomes the currently executed line. If there are no further breakpoints in the following XSLT program, pressing this key again means that the debugging mode is terminated as soon as the current line is processed. The XSL transformation is executed up to the end. If the XSLT program does not contain any breakpoints, the debugging mode is terminated immediately after you press this button and the XSL transformation is executed to the end.
SHIFT + F4	Create or delete line breakpoint	Inserts a line breakpoint at the line where the cursor is positioned within the XSLT program, provided this is an executable line. If the selected line cannot be executed, the breakpoint is set automatically at the next executable line. In this case, the system issues an appropriate message in the debugger message line. The breakpoint line is always marked in yellow. However, if there is already a line breakpoint on the line selected, this will be deleted after you have pressed the button.
CTRL + F4	Display current line	If the cursor is in the XSLT program display, the system makes the currently executed line in the XSLT program visible and the cursor is also positioned on this line. The same happens if the cursor is in the XML document display. If the cursor is currently not positioned on any of the two displays, a message box appears with an appropriate message.

Caution

Note that each time you press the pushbuttons (Single step) or (Execute), this does not necessarily effect a visible change in the debugger. This is due to the logic of the XSLT processor. Some steps in the XSLT processor cannot explicitly be made visible (for example, if tag attributes need to be created). In such cases, you must click the respective key several times in succession before a change becomes visible in the XSLT program display, in the XML document display, or in the result view.