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

Getting different result while executing the report by debugger

Former Member
0 Likes
813

Hi All,

I am facing a peculiar issue. When i execute the report from SE38 i am getting a particular set of values in a alv report.

But if i start debugging the report by using /h and execute . i am getting another set of result. How does it happen any idea.

Without debugger result is

a

b

c

With debugger i am getting result as

a

d

e

f

What may be the reason . Kindly help.

Thanks in advance.

S.Velsankar

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
712

In debugger COMMIT is triggered after every line. So if you are trying to update DB and based on that you are trying to display then you can get different values. If it is a stand alone report this sort of problem should not occur.

5 REPLIES 5
Read only

Former Member
0 Likes
712

Hi,

you mean you have'nt change anything while debugging and results are different when ALV is displayed?

I don't really understand your issue... Could you give more details?

Kr,

m.

Read only

Former Member
0 Likes
712

Hi,

Yes i havent changed any values in debugger. but the value changes can you help

Read only

0 Likes
712

From where come those values? Are you retrieveing them from DB? Are you trying to update a DB somewhere in the process?

Can you just give details about the process?

The first thing I would think of is a COMMIT issue while debugging...

Kr,

m.

Read only

Former Member
0 Likes
713

In debugger COMMIT is triggered after every line. So if you are trying to update DB and based on that you are trying to display then you can get different values. If it is a stand alone report this sort of problem should not occur.

Read only

Former Member
0 Likes
712

Closing the ticket. I used Goto statement in the debugger i think the problem is because of that