Scribd
Upload
20 views19 pages

SAP ABAP New Debugger Tool

The document outlines the features and functionalities of SAP's New Debugger Tool for ABAP development, emphasizing its advantages over the Classic Debugger. It covers various debugging techniques, types of breakpoints, and settings, along with practical examples to enhance debugging skills. The goal is to familiarize developers with the new tool to improve their debugging experience and efficiency in SAP ABAP development.

Uploaded by

atosishprakash
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
20 views19 pages

SAP ABAP New Debugger Tool

The document outlines the features and functionalities of SAP's New Debugger Tool for ABAP development, emphasizing its advantages over the Classic Debugger. It covers various debugging techniques, types of breakpoints, and settings, along with practical examples to enhance debugging skills. The goal is to familiarize developers with the new tool to improve their debugging experience and efficiency in SAP ABAP development.

Uploaded by

atosishprakash
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 19

SAP ABAP New

Debugger Tool
for Functionals
Oct 13, 2023

ILLUMITI.CO
M
By : Ish Prakash & Sweta G.
Agenda
The SAP New Debugger Agenda is a plan that guides Functionals
through the powerful features of SAP's latest debugging tool. In
simple terms, it covers the basics of understanding debugging in SAP,
highlights the challenges faced with traditional methods, introduces
the new tool's capabilities, explains its key features like advanced
breakpoints and real-time variable tracking, and demonstrates how to
use it effectively. The agenda also includes real-life examples, user
testimonials, and tips for efficient debugging. It aims to make
developers familiar with the tool, enhance their debugging skills, and
improve their overall experience in SAP ABAP development.
Topics to be cover

 Overview
 Different types of breakpoints
 Flow of Control
 Debugger Settings
 Debugging various ABAP objects
Overview -
Introduction

For any day-to-day issue faced in SAP, debugger is the most basic tool
that can be utilized to reach the root cause. It not only lets you
trouble shoot effectively but also helps you visualize ‘what-if’
scenarios. The Debugger is a programming tool that you can use to
execute ABAP programs, by line or by section. With this tool, you can
display data objects and check the flow logic of programs.

There are two types of Debugger available:


 Classic Debugger for release levels up to and including 6.40
 New Debugger, which is available for all releases after 6.40
Overview – Difference

Classic Debugger New Debugger


 Runs in the same roll area as application to  executed in a separate external session ,
be debugged while the application to be analyzed uses a
 Not all ABAP code can be debugged like second external session
conversion exits and field exits.  a flexible interface that can be configured
 No state-of-the-art user interface as required and has more than eight
 The classic Debugger analyzes a roll area desktops
that, when canceled, itself cancels the  the new Debugger analyzes an external
classic Debugger. Therefore, all the existing mode. As long as this external mode is
settings, such as breakpoints or display of active, the Debugger will remain open and
variables in the classic Debugger, control this mode.
disappear as soon as the limits of the roll
area are exceeded.
Overview - Switching

Switching from new debugger to classic debugger

Switching from classic debugger to new debugger


Overview - A first look at the detailed view of
new debugger
Overview - Advanced features of ABAP
debugger

 Split screen debugging


 Searching contents in internal table
 Download internal table to excel sheet
 Flow of control while debugging
 Variants Saving
Different types of breakpoints

Debugger Session User


Breakpoint Breakpoint Breakpoint
 When a breakpoint is  A breakpoint set in the  It is valid for all user
set in a debugger, it is ABAP Editor is a logons on the current
set as debugger session breakpoint. server of the current
breakpoint by default.  It remains active system.
 It is valid only when independent of  It is particularly
the debugger instance, existence of the required ,when
in which it was set, is debugger. debugging BSP
active.  It is valid for all applications or via
 When the debugger is external sessions of a Interface.
closed, all breakpoints logon.  It is valid only for a
set in it are deleted, period of 2 hours.
unless saved.  It is also known as
external Breakpoint
Different types of breakpoints – different ways to put
breakpoints
 Hard coded / Static break points: You can put a breakpoint in a program by writing
following statements.
 “BREAK-POINT” : To stop the execution irrespective of who is executing it.
 “BREAK ”: To stop the execution only for specific user mentioned by .

 Dynamic/Session break points: We can put dynamic breakpoints from SE80 or SE38 or
debugger. Dynamic breakpoints are always user-specific and are deleted when you log off
from the R/3 System. They can be deleted or deactivated during runtime.
Different types of breakpoints
 Debugging without Breakpoint: You can start the Debugger as follows
 In SE80: Select a program or transaction and from the top menu choose
Program -> Test -> Debugging.
 In SE38: From the top menu choose Program -> Test -> Debugging.
 From any other screen: From the top menu choose System -> Utilities -> Debug
ABAP.
 or Enter /h in the command field and press enter.
Once inside the debugger, breakpoints can be set at statements, subroutines, FM,
etc as shown here
Flow of Control

F5 (Single Step) : Step through the program statement by statement.


F6 (Execute) : Process Line by Line .Mainly used to execute a Module or subroutine
without entering into it.
F7 (Return) : Use this option to return back to the calling program.
F8 (Run/Continue) : Use this option when no more step check is required. The program either
executes normally or the debugger stops at the next breakpoint.
Display Field/List Contents: Double Click on the field or structure required. Its contents are then
displayed. If the program generates a List, then an icon appears as soon as the list is populated.
Click to open the list display.
Flow of Control - Watchpoint
Watch points help in monitoring the contents of individual variables. By setting a watch point, the
debugger stops as soon as the value of the monitored variable changes. To set a watchpoint, start
the debugger and proceed as follows:
 Choose Watchpoint.
 Enter the name of the field for which you want to set
the watchpoint. In the Program field, the name of the
program currently running is always defaulted.
 You can use the Additional Condition option to specify
whether the flow should interrupt after meeting the
specified condition.

Useful in looping conditions where you have to reach a


particular material out of several iterations. This can be
achieved by setting the variable SY-TABIX = intended
iteration
Debugger Settings
Debugger settings are accessed in ABAP debugger by navigating to Settings > Display/Change
Debugger settings.

 System debugging : In SE38, programs can be set to ‘system program’ in the status. The debugger
then skips the program if system debugging is turned off. If there is problem that involve system
programs, such as with a function that can’t be accessed in debugger, turn on this setting. System
debugging can be turned on by entering ‘/hs’ in the command field in the debugger.
 Update debugging : To analyze asynchronous updates, we use update debugging. Asynchronous
updates are functions that are called with addition IN UPDATE TASK as CALL FUNCTION ‘..’ IN
UPDATE TASK .. The debugger can’t follow this update modules, and we won’t see anything for
these modules during debugging, if we don’t use ‘update debugging’ setting.
Debugging various ABAP Object - Smartforms

The best way to debug the form is to put a breakpoint in the function module generated by the
smartform. For this, open the smartform we want to debug. Goto Environment -> Function
module name.
Debugging various ABAP Object - Smartforms

Open the function module in SE37. From the menu GOTO -> main program. Open the last
include.

This include contains the entire code i.e. the code we have written in initialization + form routines +
program lines + sap generated code. Put a breakpoint at any point you want. If we issue any doc
which triggers this form, when the control reaches the break point it will stop. Prefer session break
point in the related function module.
Debugging various ABAP Object – Batch Jobs

Debugging Active Jobs(SM50 OR SM66):


 Go to SM50 (Waiting/Running/On hold jobs) : Menu > Program/Session > Program >
Debugging. Now control will go to debug mode.

 Go to SM66(Running/Debugging Objects) : Place cursor on your job and click on debugging


button in tool bar.
Debugging various ABAP Object
Debugging Completed/Cancelled jobs
 If necessary, place a breakpoint in the program.
 Go to transaction SE37 and select our job.
 Enter ‘JDBG’ in the command window and press on the enter key.
 Now the control goes to the debugger .
 Press F8 and control goes to our break point.
THANK YOU

ILLUMITI.CO
M

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy