debugging with breakpoint and without breakpoint makes different results.

[Former Member]

Hi , all

The results are different while debugging a program with breakpoint and without breakpoint . why is that? Any suggustion is welcome and helpful .

Thanks in Advance

Thomas .

[Former Member]

use

delay 1 second.

after your database commit ( i.e.after ur call transaction)

as i am not having my sap system at home so i could not give u example code sorry for that.

when you are in debugging mode you are explicitly giveing system some time so it is working.

Edited by: S.r.v.r.Kumar on Jul 6, 2008 12:57 PM

[Former Member]

What are different???

[Former Member]

I have found that you can get different results as well. I have also seen instances where, while in the debugger, you saw entries in a table that didn't exist. The bottom line is you really can't trust the debugger 100%.

[Former Member]

I use a perform in the METHOD handle_hotspot_click_hipo of alv_grid . the perform is used to exc a SQL statement . It seems to run the perform while debugging with a breakpoint . and without a breakpoint , it doesn't run the perform .

[Former Member]

hi,

i think before perform you need to use commit work for sometime..

is that perform workin on any condition??

let me know...

[Former Member]

hi in some of the performs if you put the break points it will give dump..some times it will stop..it will not run ...some of the standard performs will not allows us to debug means we had no authorisation to debugg it....

[Former Member]

Hi,

Use COMMIT WORK statement where ever necessary like after using function module and after subroutine and check..

Hope this would solve your issue..

Regards

Narin Nandivada.

[Former Member]

Hi,

Is the method that you call somewhere inside a RFC FM. If so then it is possible.

Please let me know the details and then I can comment.

Regards,

Saurabh

[Former Member]

CASE e_column_id.

WHEN 'VBELN'.

SET PARAMETER ID 'AUN' FIELD ls_outtab-VBELN.

CALL TRANSACTION 'VA02' AND SKIP FIRST SCREEN.

PERFORM GETDATA_NONDEAL.

• CLEAR:INTAB,INTAB[].

CALL METHOD grid->refresh_table_display.

CALL METHOD cl_gui_control=>set_focus

EXPORTING

control = grid.

CALL METHOD cl_gui_cfw=>flush.

ENDCASE.

above is the source code . the perform is a select-sql statement,not insert or update statement . i need to

re-select the data from vbak while a SO changed . and then re-show the data in a grid . the most funny thing is that it runs the perform while pressing F5/F6 to debug the code.it doesn't while pressing F8 .

[Former Member]

Hi,

In debugg there is a delay in database update,

CALL TRANSACTION 'VA02' AND SKIP FIRST SCREEN.

wait up to 3 seconds.

PERFORM GETDATA_NONDEAL.

Hope this should sove your problem...

If the hint is usefulu2026 Say thanks by rewardu2026.

Regards,

Prabhu Rajesh

[Former Member]

hi

debugging is line by line till break point so it ll check all syntax and performance issues til ur break point ..when u remove break point some syntax errors as object doesn't used and all will be removed because the compiler will checks (debugs) entire program..

rate me if u felt it is helpful..

keep using F1 it is the best guide ...

[Former Member]

use wait or delay.

[Former Member]

hi S.r.v.r.Kumar

could you please show me the steps ?

[Former Member]

Need help .

[Former Member]

use

delay 1 second.

after your database commit ( i.e.after ur call transaction)

as i am not having my sap system at home so i could not give u example code sorry for that.

when you are in debugging mode you are explicitly giveing system some time so it is working.

Edited by: S.r.v.r.Kumar on Jul 6, 2008 12:57 PM

[Former Member]

Thanks S.r.v.r.Kumar , Prabhu Rajesh and Everyone ! the problem was solved . Add code " wait up to

X seconds, just as S.r.v.r.Kumar , Prabhu Rajesh said in the threat . Thanks again !

Thanks&regard

Thomas