topic Re: Debugging problem in Application Development and Automation Discussions

Debugging problem

Former Member — Tue, 21 May 2013 10:45:33 GMT

hi,
while debugging a standard report i encoutered a problem
In initilization Event
there is get parameter ID. doing F5 on it take me inside loop at screen
after loop finishes debugger comes out of report.
it does not go inside Start of selection event that is exactly after get parameter statement
since i have to debug a perform that is called in Start of selection event

how can i go to that perform.
i tried setting up breakpoint at perform, it does not go there

Re: Debugging problem

PeterJonker — Tue, 21 May 2013 11:15:29 GMT

Initialization event is called before the selection screen comes up. Therefore correct not to go to start-of-selection (unless you do not have a selection screen, in that case please supply us with the code)

Re: Debugging problem

Former Member — Tue, 21 May 2013 11:23:35 GMT

Hi Rishabh,

Once you start the debugger for the first time, give breakpoint at START-OF-SELECTION. If you don't have any input fields, then start of selection should get triggered automatically. If you have input parameters, after providing input execute, then it goes to start of selection, and then end of selection.

Re: Debugging problem

Former Member — Tue, 21 May 2013 11:31:11 GMT

Hi Rishabh,

Can you provide the standard program name that you are trying to debug? It is possible that the perform you are trying to debug is called in a condition check (if else block) and the condition is not getting satisfied when you execute the program.

Hope this helps,

~Athreya

Re: Debugging problem

Former Member — Tue, 21 May 2013 11:40:54 GMT

Hi Rishabh,

Events occurance order:

Initialization.

at selection-screen output

at selection-screen

start-of-selection.

end-of-selection.

top-of-page.

end-of-page.

so from initialization it will go to at selection screen in your case. Initialization triggers

before screen is displayed.give some screen input and start debugging.

Re: Debugging problem

Former Member — Tue, 21 May 2013 11:42:49 GMT

hi,

i am using SAP FS-CD,
T-code FPB7
report-RFKKKA01
need to get to perform BANK_STATEMENT_PROCESS
altough there are check inside start of selection but while debugging pointer does not come to Check statement it directly goes out after GET PARAMETER statement.

Re: Debugging problem

Former Member — Tue, 21 May 2013 12:01:27 GMT

Open code create break point at perform BANK_STATEMENT_PROCESS.

execute program give selection screen entries execute break point will stop at perform then debug ur code

Re: Debugging problem

PeterJonker — Tue, 21 May 2013 12:06:28 GMT

I don't have TC FPB7 but I do have program RFKKKA01.

However in this program in my system there is no initialization event. There is also no statement get parameter id in this program.

Furthermore this program has a selection screen and therefore the initialization event (where you say the get parameter id is called) is called before the selection screen comes up and therefore (with the version in my system) the behevior of your program is correct. Sorry that I can't be of any more help.

Can you post the code in the initialization event ?

Re: Debugging problem

Former Member — Tue, 21 May 2013 15:56:25 GMT

Hi Rishabh,

The step by step procedure to set breakpoint and reach the perform BANK_STATEMENT_PROCESS is,

Thanks,

Ankit.

Re: Debugging problem

Former Member — Wed, 22 May 2013 07:38:35 GMT

Hi ankit,

thanks for the screenshots.

i tried setting breakpoint following your steps but doing F8
breakpoint didnt reach and report was executed fully.
report RFKKKA01, where i want to debug is called by submit statement in perform SUBMIT_JOB.

report RFKKKA01,starts with:

3 include

initilization
get parameter id ''.

start-of-selection.

check ''
perform BANK_STATEMENT_PROCESS

(this perform contains code to update table entries).

so while debugging i reached Submit statement inside perform SUBMIT_JOB, and then debugger goes to above report and then to get parameter after it goes to some loop at screen.

after loop some function job_submit and then to main Perform SUBMIT_JOB.

database table are updated. couldnt reachd to perform BANK_STATEMENT_PROCESS

thanks in advance.

Re: Debugging problem

PeterJonker — Wed, 22 May 2013 08:40:52 GMT

your code has a statement

check ''

What does it check. Is that condition fullfilled, because if not, program stops and that would be exactly the behavior you are describing. That is the nature of the CHECK statement

Re: Debugging problem

Former Member — Wed, 22 May 2013 08:51:59 GMT

hi peter,
yes condition gets fullfilled
but atleast debugger pointer should got to that check statement and then check the condition.
but it didnt go.

thanks

Re: Debugging problem

Former Member — Wed, 22 May 2013 09:04:16 GMT

Hi Rishabh,

Please post the data and screenshots. I assume since you are not entering proper data on screen it is unable to break at the breakpoint.

Thanks,

Ankit Maskara.

Re: Debugging problem

himanshu_gupta13 — Wed, 22 May 2013 09:04:56 GMT

Hi Rishab,

Initialization event only calls when we start the report i.e. while executing the tcode it goes in initialization event first.

And to go in debugging after start-of-selection first input and then again start debugger using /h and then you will get into start of selection.

If you still facing problem then place the static breakpoint here after start-of-selection and then on debugger and execute.

Note : your program contains the check statement, kindly please clarify this statement and if it define clearly according to it if the condition fullfiled by check then it will go further other wise it terminates further execution due to false return by check..

It will be more better for me if you place here code clearly to resolve this.

Many Thanks / Himanshu Gupta

Re: Debugging problem

PeterJonker — Wed, 22 May 2013 10:04:57 GMT

Please provide the code in intialization event, get parameter-id.

Basicaly all code that is called directly before perform BANK_STATEMENT_PROCESS from a moment where you still saw the debugger pass it (get parameter id ? initialization ?)

I won't be able to help you w/o this code, because my version of this program does not have initialization, get parameter-id .