Shulou(Shulou.com)05/31 Report--

This article mainly explains "how to use SAP's ABAP debugger". The content of the article is simple and clear, and it is easy to learn and understand. Please follow the editor's train of thought to study and learn how to use SAP's ABAP debugger.

First figure out the difference between the ABAP Classic debugger and the new debugger:

Classic debugger:

(1) Static breakpoint

A. BREAK-POINT: non-user specific

B. BREAK user name user specific

(2) Dynamic breakpoint

New debugger:

(1) Static breakpoint

(2) Dynamic breakpoint

A. Session breakpoint

B. External breakpoint

The difference between Session breakpoint and External breakpoint

(1) Session BP is only visible in all external sessions belonging to the same user session, while External BP is visible across all user sessions. Therefore, only External BP is valid for BSP / Webdynpro debugging.

(2) When a user logs off, Session BP will be deleted while external BP persists.

By setting this flag, if external session An is running, and in external session B (An and B belongs to the same user session) you set a session breakpoint in the program source code, the BP will be triggered immediately.

The difference between ABAP exclusive breakpoint (Exclusive Breakpoint) and non-exclusive breakpoint

The following figure is a non-exclusive breakpoint:

The following figure is the exclusive breakpoint:

Exclusive mode means the application to be analyzed exclusively occupies a work process of the application server during debugging. If all exclusive debug work processes are occupied, the Debugger is switched to non-exclusive mode. (rdisp/wpdbug_max_no)

Limitation for non-exclusive mode:

Due to technical limitations in ABAP debugger implementation, there are following limitations when debugger is run under non-exclusive mode:

(1) No possible to debug statement between SELECT and ENDSELECT. In this case, program terminates with this error:

(2) No possible for conversion / field exit.

(3) No possible for debugging in production system, program terminates with exception DEBUGGING_NOT_POSSIBLE.

How to read some metrics in the ABAP debugger?

Consider the following simple ABAP code:

Look at A1 in the debugger, which is a variable of the inner table: what does [2 × 1 (8)] mean?

2: table row number

1: table column number

8: byte length of table row

The time for which the new Debugger is active is determined by the profile parameter rdisp/max_debug_lazy_time-which is set to 600seconds in the standard version. After this time space has elapsed, the Debugger process is exited automatically and control is passed back to the application.

A few tips: how to debug background RFC?

Solution: use the transaction code sbgrfcmon

Tip 2: how to debug update task

Tip 3: how to use ABAP to watch Watch point

Exercise: when we enter the transaction code SE09, we will observe that the User field is automatically populated with the current login user. How to quickly find the value assigned by which line of code through the observation point?

When we use SE09, how can we find the logic of the User? When and where is this field filled? What does content come from?

Debugging step by step will be very time-consuming.

Tip 4: use ABAP to check the group Check group

Tip 5: transaction code SRDEBUG

Tip 6: debug scripts

Thank you for reading, the above is the content of "how to use SAP's ABAP debugger". After the study of this article, I believe you have a deeper understanding of how to use SAP's ABAP debugger, and the specific use needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.