topic Re: Debugging mode in Application Development and Automation Discussions

Debugging mode

Former Member — Sat, 16 Jan 2010 09:44:53 GMT

Hi frends we are facing an TIME_OUT runtime error.In the SOURCE CODE EXTRACT , we gt the code bcz of which it is happening.It is a select statement .:

IF NOT WF_BSEG[] IS INITIAL.
      SELECT DOCNR BUZEI BELNR MSL RACCT BUDAT
        FROM FAGLFLEXA 
        INTO CORRESPONDING FIELDS OF TABLE T_FAGLFLEXA2
                              FOR ALL ENTRIES IN WF_BSEG
                                       WHERE RBUKRS = '9009'
                                       AND RYEAR = E_FYEAR
*                                       AND RBUSA = P_WERKS
                                       AND RACCT IN P_KSTAR
                                       AND DOCNR = WF_BSEG-BELNR
                                       AND BUZEI = WF_BSEG-BUZEI.
    ENDIF.

is there any way to know that what condition in the where clause it is nt able to satisfy?

Edited by: Rob Burbank on Jan 17, 2010 8:06 PM

Re: Debugging mode

Former Member — Sat, 16 Jan 2010 16:25:18 GMT

Hi Achal ,

With TIME OUT error it means that , number of records fetched from this database table are many and hence the query execution takes more time.

You should try to optimize this query. Check that all the parameters used in where clause are having correct data type and try to increase the parameters in where clause.

Also, you can reduce number of records fetched from tables by making selection screen fields Mandatory.

Proceed with runtime analysis and use trace to check the index used.

Hope this helps you.

Re: Debugging mode

kesavadas_thekkillath — Sat, 16 Jan 2010 17:38:42 GMT

Try to pass the key fields available or

You can use OPEN CURSOR addition with the select statement.

Please search in SCN or Google for more details.

Re: Debugging mode

Former Member — Mon, 18 Jan 2010 01:08:01 GMT


> You can use OPEN CURSOR addition with the select statement.

@Keshav.T - how does OPEN CURSOR help here?

Rob

Re: Debugging mode

Former Member — Mon, 18 Jan 2010 04:31:31 GMT

hi fiends....this TIME_OUT is nt bcz of any performance issue.actuallly it is only a report in which we are obtaining data from different standard tables then store it into a z table,internal table and then just display it.actually i have checked a z table used in this report from which we display the data, it does nt contain the entry which is entered by user in selection.

actually it is a performance report of equipments like their fuel cnsmptn,ideal hours,working hours etc for PM module in which user has to enter only month and the plant name for which he wants to see the report. the problem is only for few plants and that too for particular months.I think there is some functional problem bcz for one of our plants it is working perfectly fine.

I want to trace that entry which causes the error and in debugging mode this was the select statement at which it keeps on processing

Edited by: achalmehra on Jan 18, 2010 5:31 AM

Re: Debugging mode

Former Member — Mon, 18 Jan 2010 04:58:14 GMT

Hi Achal ,

Try to trace your code using first by ST05 and then by SE30 .

This is the best method and recommended by SAP Experts for performance tuning of your code.

Please let me know if you need more help in this.

Regards,

Nikhil

Re: Debugging mode

Former Member — Mon, 18 Jan 2010 05:43:34 GMT

Hi nikhil

in ST05 it is shwing table RFBLG and in se30 it is showing the select statement given by me before.

Re: Debugging mode

Former Member — Mon, 18 Jan 2010 06:28:29 GMT

Hi Achal ,

RFBLG is a Cluster for accounting document . Its clear that this is refered somewhere in your code or in one of the select query in standard tables. It will be of great help if you could share the trace file so that I can recommend you something that will help you in incresing the Performance.

Regards,

Nikhil

Re: Debugging mode

Former Member — Mon, 18 Jan 2010 07:31:02 GMT

how to share.is there nay option to attach a file here..bcz the report has exceeded limit of max charators allowed here

Re: Debugging mode

Former Member — Mon, 18 Jan 2010 07:37:39 GMT

one more thing nikhil i wanna tell u.the report is working fine for the plants created earlier for all months.only for some of our plants, it is not working for the month after sept.,2009. I mean we are facing TIME_OUT for these.

like if for a new plant i use the month and year(mm/yy) : 10/09 then we face error

and if i use 10/10(mm/yy) : then we dont face error.

Re: Debugging mode

Former Member — Mon, 18 Jan 2010 07:40:43 GMT

One more thing achal i wanna ask you Can we have any updates on long discussion thread, Please?

Re: Debugging mode

Former Member — Mon, 18 Jan 2010 07:46:36 GMT

This message was moderated.

Re: Debugging mode

former_member194416 — Mon, 18 Jan 2010 07:53:01 GMT

Hi,

There is only two approach for the solution.

- Try to improve performance of select statement (You can check if it is possible to create an index, it will improve the performance)

- If not possible you can run the program in background. When program is running in background there will not be any time restriction.

Re: Debugging mode

Former Member — Mon, 18 Jan 2010 07:53:33 GMT


> hey amit....srry friend as i was nt receiving any further comments and solutions for that thread so i just closed it.I am still lukng for a solution of that problem. but let us nt disscuss that problem in this thread....so plz...i am srry.yeah if i will have the solution for that problem i will intimate u.gve me ur id if u come to know anythng abt that plz tell mee..thnxxxxxxxxxxxxx

Looks like vowels are not functioning on your keyboard? Is it?

Cheers

Re: Debugging mode

kesavadas_thekkillath — Mon, 18 Jan 2010 08:03:35 GMT

Hi Rob,

Not as much as you know

Doesnt open cursor with hold avoids the time out error.

Re: Debugging mode

Former Member — Mon, 18 Jan 2010 08:38:32 GMT


> Doesnt open cursor with hold avoids the time out error.

So are you suggesting OP to use Native SQL instead?

Cheers

Re: Debugging mode

kesavadas_thekkillath — Mon, 18 Jan 2010 08:45:43 GMT

Hi amit,

No not native sql.

I have seen so many discussions in forum related to this,

to use cursor with hold concept, so that there won't be time out error while fetching data from DB.

May be im wrong

Re: Debugging mode

Former Member — Mon, 18 Jan 2010 10:32:47 GMT

hi friends i have tried to run it in the background.The duration for it has reached 2200 seconds and the count is still on.I mean stilll the job is in active state nd not finished

Edited by: achalmehra on Jan 18, 2010 11:33 AM

Re: Debugging mode

Former Member — Mon, 18 Jan 2010 10:36:52 GMT

the report is running well for some plants.only it is not working for newly created plants and for period (mm/yy) 10/2009 to 03/2010.could there be some problem related to the configuration of these plants.?

Re: Debugging mode

Former Member — Mon, 18 Jan 2010 11:37:09 GMT

> No not native sql.

> I have seen so many discussions in forum related to this,

> to use cursor with hold concept, so that there won't be time out error while fetching data from DB.

??? open cursor is no Native SQL, but can see no advantage here. The OPEN CURSOR WITH HOLD is interesting if changes

to the db follow.

The problem is not really explained, how long does the actual SELECT need? I see no data?

How many records are in the driver table of the FAE, how many in the database table, what are the indices?

I am not familiar with that table but is does not make sense, to look up the settings in an other system.

Siegfried