ABAP Debugging Tips

Some useful ABAP Debugging tricks.
Check this out:

Ref: https://www.youtube.com/@ERP-UP

Debug the POPUP in SAP

 Since Debugging of the Popup is not possible directly in SAP.  Cause we cannot put '/H' in the command line. So there is a way by which we can debug the Standard Popup or any Z Popup.

Create one TXT File in you system.. Lets say File name is 'Debug.Txt'.

Now Write the Below mentioned code in the .TXT file. 

[FUNCTION]
Command=/H
Title=Debugger
Type=SystemCommand

Now Save this File.

 Now execute your SAP and Open any POPUP .

Steps: First go to the file 'debug.txt' and drag that file and drop that file on the POPUP

Please See below screen shot.  
 

Now Click the Button and you would notice that the There is one status message comes up ' Debugger switched on'.  
 

and when you clikc any button then the deubger will come up 

How to Debug Popup Screen in ABAP

Debugging in ABAP for ABAP developers is a vital requirement during building application in SAP systems. There are numerous ways to debug ABAP code or debug SAP screens for ABAP developers. But many ABAP programmers who are new to ABAP development may not know how to debug popup screen in SAP platform. In this short ABAP tutorial, I'll try to share you ABAP trick to debug SAP popup screens.

Please note that, this tutorial does not cover debugging using "/H" option or using break points in ABAP code. I want to concentrate on developers requirement to debug an unknown ABAP code block which they want to discover.

First step is open your Notepad application and type or copy-paste the following commands in a new blank text file.

[FUNCTION]
Command=/H
Title=Debugger
Type=SystemCommand


Then save the above text file as a batch file. You can name it as debug.bat for example.

Now ABAP developers are ready to debug a modal popup SAP screen. Let's assume that you want to debug output processing log screen for an invoice output

Now drag and drop debug.bat batch file from your Windows desktop onto the modal popup SAP screen.
Then the SAP GUI will inform you about the debugging status with message "Debugging switched on"

Now ABAP developers can easily activate debugging screen in ABAP on the modal popup SAP screen.

How to debug Smartforms

Debugging SmartForms using Function Module

If you want to debug Smartform document in non-modifiable client, then you can try debugging Smartforms Function Module using soft break point.

First you need to find the function module name of the target SmartForm for debugging.
If you do not know how to get the function module name of the SAP Smart Form, please read the Smart Form tutorial titled How to Find SAP SmartForms Function Module Name.
Without knowing the function module name, we can not debug SmartForms in non-modifiable clients.

After you find the function module name, we can now display the ABAP source codes of the SSF FM (Function Module) using the SAP Transaction SE37.

Within the ABAP codes of Smartform FM you can put a soft break-point any where suitable for your debugging Smartforms purposes.

It is better to copy the node name or some parts of the ABAP code in the SAP Smartform and search the text within the SE37 displayed source code of the Smartforms function module (FM).

You can place a soft break point in the source code using Ctrl+Shift+12 key combination or using the Stop icon .

Let's assume that you want to debug Smartforms codes within program lines named '%CODE10' as seen in the followin Smartform screenshot,

First click on the Search button , and not use the Ctrl+F since searc button has far more powerful functionalities than ordinary Ctrl+F search.

Enter the text you are searching in the Find text area.
You can search for the node name '%CODE10' as well as for a part of your SmartForm code.

What is important here in this Search is be sure that you selected the option "In main program".
Otherwise your search will take place only for a limited part of the Smartform function module codes.

When the place of the target code block is found, you can run the SAP Smart Form and start to debug Smartform document.

Debugging workflows and generating sub-workflows

Debugging workflows and generating sub-workflows

Comment:

Workflow Debugging

First of all, you cannot set breakpoints in a workflow, so I assume you mean that you have set a break-point in a method used in one of the task's used in your workflow?

If so, and if this task-method is a background method (i.e. a non-dialog task), debugging is not possible, since a background method, as the name states, is executed in another context in background.

To see how the workflow passes values from/to the different container's, you can use transaction SWUD (to see if the values needed for your method, are binded correctly).

Other useful tools for workflow error search, are: SWEL (first turn on even trace with SWELS) or simply look at the workitems created to see what kind of errors they may have encountered: SWI2_FREQ f.x.

If background task, I recommend you use SWUS for the specific task in question to create a WorkItem. Find the workitem with SWI2_FREQ, then display it. From there, display Container, to see the outcome.

You can debug the method, from SWO1 for the Object Type owning the method. From SWO1 simply click the test button. Then click "create instance". Execute the method for the object instance and you will be able to debug the method.

Generating Sub Workflow

1. Add one of your subflows to the main workflow as an activity step and define the binding. This subflow is just a place-holder and will be replaced by another subflow when the workflow runs.

2. In the step definition specify "Task to be determined using an expression" and specify which container element (or expression) contains the subflow ID to be used.

At run time, the place-holder subflow will be replaced by the subflow that is specified by the expression. In other words this expression reads the table that you created to find the subworkflow to call and this subworkflow is called by the main workflow instead of the (static) place-holder subflow.

Finding out the Object Types involved

• Switch the event trace ON (Tcode SWELS), carry out your transaction and view the event log (Tcode SWEL).

• If there is a standard event then the trace will tell you the name of the object and the event raised.

• Otherwise create your own object and events and trigger it (them) using FM "SWE_EVENT_CREATE".

How to Debug Pop-up window

The okcode field is deactivated when a modal window (the technical name of popup windows) is displayed, so it seems impossible to enter the debugger (using /H okcode).
In common dialogs, the okcode field is available:



But it is not available in modal windows (we see it but we can't enter anything in it):




The solution is to create on the frontend a SAPGUI shortcut (file with extension .SAP), of type System Command and command /H, and drag and drop it from Windows desktop to the SAP modal window. The creation of SAPGUI shortcuts is explained here: SAPGUI shortcuts.