Ways of Debugging (SAP Library - ABAP Workbench Tools)

Ways of Debugging

Use

In debugging mode, you can analyze the source code of an XSLT program in different execution modes. The pushbuttons on the application toolbar give you quick access to the corresponding functions.

Features

The table below gives a detailed description of the individual execution types:

Icon / Key Combination	Function	Description
F5	Single Step	Executes the XSL transformation statement by statement.
F6	Execute	The debugger executes the whole XSL statement. If the statement contains multiple steps, they are executed in one go. This function is important for statements like <xsl:apply-templates …/> and <xsl:call-template>, or when you call named blocks (templates, functions and so on).
F7	Return	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 the next source node	This function allows you to process the tree hierarchy of the XML document step by step. When you choose the pushbutton, the XSL transformation is executed from the current position up to the next node in the XML tree.
Result SHIFT + F8	Continue up to the next result change	Executes the XSL transformation from the current position up to the next change in the result.
F8	Continue	Executes the XSL transformation up to the next breakpoint. If there are no more breakpoints in the XSLT program, choosing this pushbutton closes the debugging mode as soon as the current line is processed. The XSL transformation is executed up to the end.
SHIFT + F4	Create or delete breakpoint	Inserts a line breakpoint at the line where the cursor is. If the line does not contain an executable statement, the breakpoint is inserted at the next executable line. If there is already a breakpoint at that line, choosing this pushbutton removes it.
CTRL + F4	Display current line	Displays the line where the cursor currently is.

Note

Note that choosing the pushbuttons This graphic is explained in the accompanying text Single step or Execute does not always result in a visible change. This is due to the logic of the XSLT processor. Some steps in the XSLT processor are not visible (for example, if tag attributes need to be created). In such cases, you must push the respective pushbutton several times in succession before you see any change the XSLT program display, in the XML document display, or in the result view.