FBL1N- Line items display performance enhancement

[Former Member]

Hi,

I am using this tcode for line item view with a huge data selection:

data selection criteria is as:

VENDOR ACC: 1 to 10000000

Company code: <any one>

Line item selection as Open

the data fetched is around 6 lac.... also the List generation is taking much time.

Overall I have output dump in production system due to this.

I have trace for this and found that table BSAK, BSIK and VF_KRED  is taking enormous time...

OSS notes like

1135916 - Line items: Help for analysis for long runtime

194842 - Poor performance when you display line items

is not applicable for my system.... only way I have is to create index for table BSAK

[Former Member · Accepted solution]

Hi Anup,

ABAPer can help in this case,

But tell me one thing why you are selecting that much huge data?

Defiantly system gives timeout error if you select that much data,

Regards.

[Former Member · Accepted solution]

Hi Ram,

I am ABAPer and this is the requirement from the functional end. So anyhow we need to solve the timeout issue.

We have implemented the corrections and now its working fine with this huge data also.

Solution would be:

table statistics had no effect but the indexes that
were recommended in the OSS note  194842 improved the performance of the transaction
and I was able to complete it without a timeout error.

[Former Member · Accepted solution]

Hi Anup,

I have the same situation. We have upgraded to Ehp6 (we have migrated from DB2 to Sysbase too), and the performance of FBL1N and FBL5N is very poor, even too many times the t-codes end in time-out error.

You talked you fixed the problem by creating the indexes recommened in OSS note 194842.

I have some indexes created in the tables indicated in the OSS note, but there isn't anyone with the 4 mentioned fields. Did you have any index created in the mentioned tables before creating the new ones?

Thanks in advence.

See you later!

PacoMS

[Former Member · Accepted solution]

Hi colleagues

The problem has been fixed or relieved. Our SAP Administrator found out about some Sybase parameters.

His own words:

“OSS note 1539125 suggest this:

The statement cache needs to have at least 100 MB.

> statement cache size >= 100M [REQ]

http://infocenter.sybase.com/help/index.jsp?

topic=/com.sybase.help.ase_15.0.sag2/html/sag2/sag2108.htm

We have changed this to:

sp_configure 'statement cache size', 500M

Also sp_configure 'open objects', 110000

We have been forced to increase 'max memory' parameter to allocate this changes, changing them without find any problem.

Now we are not facing the 'time out' dump and performance is noticeably improved...”

Best regards

PacoM

[former_member612567 · Accepted solution]

Hi Anup,

I am a abaper, I also got the same requirement from functional.

can you explain in some more deeper on the same.

I dont have much Idea on Indexes but using google I may solve that.