Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Debugging

Former Member
0 Likes
776

is debugging possible with in select....endselect ? give me the reasons plz..

1 ACCEPTED SOLUTION
Read only

uwe_schieferstein
Active Contributor
0 Likes
700

Hello Mohammed

It is possible to debug within a SELECT - ENDSELECT loop. However, sometimes this will result in a dump due to some interference of the debugging with selecting the data from the DB tables.

Regards

Uwe

4 REPLIES 4
Read only

uwe_schieferstein
Active Contributor
0 Likes
701

Hello Mohammed

It is possible to debug within a SELECT - ENDSELECT loop. However, sometimes this will result in a dump due to some interference of the debugging with selecting the data from the DB tables.

Regards

Uwe

Read only

0 Likes
700

Thank you for the reply, could you explain me the exact cause for the dump over here....(select..endselect)

Read only

0 Likes
700

Hi Younus

If you are debugging in between a select-endselect statement, it may lead to Dump due to the explicit commit work that is done by the debugger.

Refer this link for more info:

<b>

debugging a SELECT...ENDSELECT statements brings to a LUW commit work if no other work processes are available for debug.

See OSS notes 675, 2104.

From OSS note 675 **********************************

Cause and prerequisites

Chain of causes:

1. There is a statement in one of the Select loops, that leads to a database Commit (or Rollback).

2. A database Commit causes the database to lose the cursor.

3. The system cannot automatically continue within Select loop after loss of cursor.

Following statements lead to a database Commit:

  • All statements that cause a change of screen (CALL SCREEN, CALL DIALOG, CALL TRANSACTION, SUBMIT, I/W-Message)

  • BREAK-POINT/ Debugging

. if no debug process free

. always after regeneration (in order to release generation lock).

  • WAIT Here a work process is released and a Commit is executed.

  • COMMIT WORK/ROLLBACK WORK

From OSS note 2104 **********************************

Solution

The "COMMITWORK" message appears in the ABAP debugger when programs

orscreensrequireregeneration,or when not enough free capacity

is available inthesystem (or else the debugger blocks a system

process).

Normallyonly one work process is released for debugging. This

isgenerally insufficient ina developmentsystem, as processes

can be blocked for other reasonstoo(background processing,

CPI-C connections,andso on).

The number of work processes made available for debugging can

be configured using the profileparameter

rdisp/wpdbug_max_no

Forexample:

rdisp/wpdbug_max_no = 10

setsthe maximum number of work processes made available for

debuggingto 10. It may be necessary to generally increase the

numberofwork processesatthis time (parameter rdisp/wp_no_dia).

In all other known cases, an error in the application program is

involved.

if it heps reward with points

Regards,

rk

Message was edited by:

Rk Pasupuleti

Read only

Former Member
0 Likes
700

Hi,

Debugging is not possible between select and end select.

may the reason is SELECT is not a part of abap. it comes in native sql.

Regards

Ramesh