Abap Report Performance

[Former Member]

One of our abap report is extremely slow, this report is used by all

branches of our company

and we are facing serious performance problem in this report. I have

analyzed the problem

and noted following things.

1) The report used "BSIS" table for a query.

2) In peak times it is observed lot of IO wait is happening on that

particular report and on

"BSIS" table.

3) After analysis of table BSIS it is noted that table has more than 12

million records and

exceeding table class limit in technical setting of tables.

4) Size of table is 4 GB.

5) Table also does not have other indexes apart from one composite PK-

unique index. This

index is composed of 9 fields.

6) Update Stats is has been taken in 10 minutes of BSIS~0.

We are closely analyzing code and where clause of our report.

I want to ask do we need other indexes specially on DATE field which is

not included in

existing index?

Do we need index rebuild as stats are gathered in 10 minutes which is

quite a long time in

my opinion?

Do we need table partition right now as BSIS has 12 million records and

4 GB of size ?

Best Regards

Waqas

[andreas_mann3]

Hi,

1) table bsis is the table for open items (GL-accounts)

-> perfect state of such a table is that there are <b>zero</b> entries,

because all open items had to be cleared and are moved to table bsas

(cleared items)

-> so 1st there is an organisational problem in your company / account dept.

why there are so many open items?

2) analyse the select statements and the abaps, which fetch bsis-table with

st05

-> check, whether key-fields BUKRS and HKONT are filled in where-clause

3)-> look to wiki- ABAP Performance and Tuning

https://wiki.sdn.sap.com/wiki/display/HOME/ABAPPerformanceand+Tuning#ABAPPerformanceandTuning-Whattoolscanbeusedtohelpwithperformancetuning%3F

regards Andreas

[Former Member]

Rather than "tricking" the system into running longer. Yous should fix your code as I showed in your other post.

This is a duplicate post. Please close one or the other.

Rob

[Former Member]

Apart of SQL and code optimization what is the high time to rebuild index and when a DBA consider table partitioning and index rebuild?

Regards

Waqas

[Former Member]

Hi Waqas,

It is not easy to say if you need another index without knowing the program.

What I can advice is to look at chapter 4.2.3 of the "Data Management Guide" which you can find in <a href="http://service.sap.com/data-archiving">http://service.sap.com/data-archiving</a>.

There you will find some advice that might help you. I would also rebuild the index (online), but make sure this is done in a low activity period.

[Former Member]

Dear Alexander ,

Thanks for your reply, i will look into archiving as may be there is lot of useless data in this table, moreover what do you think when table partitioning becomes necessary and what indicators compel administrator to rebuild indexes,

MY stats collection logs showing only BSIS~0 index which is taking over 10 minutes in stats collection, strangely BSIS table itself is not in list of tables which are taking time in stats collection .

Regards

Waqas

[Former Member]

Hi Waqas

To Avoid Time Out you can use following Code

DATA: D_LI_PERCT TYPE I,

D_LC_ITEXT TYPE ITEX132.

D_LC_ITEXT = 'Reading Bsis'

CALL FUNCTION 'SAPGUI_PROGRESS_INDICATOR'

EXPORTING

PERCENTAGE = D_LI_PERCT

TEXT = D_LC_ITEXT .

Function Module 'SAPGUI_PROGRESS_INDICATOR' will alot additional Time to read Table Bsis and you can avoid the Time Out in your Report .

Hope it will help you .

Regards

Siddharth

[Former Member]

thanks Siddharth

Ok i ll try and will tell you

Regards

Waqas