Since the transformation call is done in ABAP using the language element CALL TRANSFORMATION, it is possible at this point to branch either from the execution moder or the ABAP Debugger into the XSLT Debugger. A standardized transition of this type however – either by pressing a pushbutton or through a menu function in the ABAP Debugger – is not available. Switching to the XSLT Debugger can only take place, therefore, if a breakpoint is also set in the called XSLT program.

See also: Starting and Exiting a Debugging Session.

The situation is the same when you wish to switch from the XSLT Debugger into the ABAP Debugger. ABAP calls within an XSLT program – for example, using the statments CALL-EXTERNAL or EXTERNAL-FUNCTION only execute the switch to the ABAP Debugger if a breakpoint is set in the called ABAP code of the method or the function module.

See also: Starting the ABAP Debugger.

Let us assum that you start an ABAP program in Debugging mode and then you continue execution up to immediately before the calling point of the transformation. Since the called XSLT program (in our case: TRANS) contains breakpoints, the XSLT Debugger is started at this point and execution of the transformation is stopped at the first breakpoint. If you continue processing of the XSL source code up to an ABAP method call (call-external) , the system switches into the ABAP Debugger at the calling point – should the called method (in our case: M1) contain a breakpoint. Continue execution at this point by pressing F8. Then you return again to the XSLT Debugger. The line after the external method call is now the current line in the XSLT program. Finally, after completion of the transformation, you return to the ABAP Debugger. The current line is now the line after the calling point in the transformation.