Since SAP NetWeaver 7.5 SP00, the ABAP Debugger also
supports simple transformation (ST) in ABAP Development Tools (ADT). Hence, you can debug
and test whether a simple transformation converts ABAP source code to XML as
required.
Prerequisites
You can only debug activated development objects.
For debugging simple transformations, a 745 kernel version, which is provided with SAP
NetWeaver 7.5, is required.
Context
You can call simple transformations, for example, in ABAP classes or programs. To
test the behavior of a simple transformation in advance, proceed as follows:
Procedure
- Open the simple transformation.
- To set a breakpoint, click on the corresponding position within the
<tt:template> section in the ruler bar.
The breakpoint is set and displayed with the
decorator.
- Open, for example, the ABAP class or program where the ST is called.
- Run, for example, an unit test or the ABAP program.
If the execution pointer of the ABAP Debugger points at a CALL
TRANSFORMATION statement of a simple transformation, choose
F5.
- [Optional:] Confirm possible dialogs whenever you are asked to switch to the
Debug perspective with
Yes.
The Debug perspective is opened. The ABAP Debugger
will stop directly at the breakpoint.
- [Optional: ] Simple transform template calls are reflected by the ABAP Debugger stack.
Therefore, you can navigate to calling templates or ABAP methods on the ABAP
stack. To do this, proceed as follows:
- In the Debug view, double-click the relevant template or
method.
The source code editor displays the corresponding source code and sets the execution
pointer at the calling position. In addition, in the
Variables view, the current value of the
selected parameters, local variable, and data nodes are
displayed.
- [Optional: ] To display the current value of variables, parameters, and data nodes of
simple transformations, hover the relevant symbol on the simple transformation
source or double-click it.
A popup is opened that displays the current value of the selected
element.