Performance Issue on 0FI_GL_14 Extraction

[Former Member]

Hi experts,

We have a client scenario whose wants to see the report in a daily basis.

Unfortunately, the report consists of those data from a standard extractor named 0FI_GL_14 which involve with really huge SAP tables such as FAGLFLEXA.

The current BW system (SAP BW 7.01) schedules a daily job for this extraction daily and it takes approximately around 12 - 16 hours for daily data load. Yes, the table is really huge and there are approximately more than 300 million records reside in the table.

Therefore, we cannot leverage this daily data to be reported in time and would like to improve extraction performance.

We are considering two options to resolve this matter.

1. Develop a customize data source (ABAP program) in SAP which will only extracts necessary data. However, we still need to query data with Posting Date up to 2 months back, the performance of this program might be worse.
2. We have researched that SAP Note 1531175 might be helpful for this issue. It states that we should create a secondary index on the table. However, since the table is really huge and the functional user concerns on the impact of creating the index whether it will impact their existing reports, performance of their transaction, downtime required during the index creation, etc.

Would you please have any suggestion or advise in regard to this? We would like to get back to the client to recommend with the better solution.

Thanks in advance.

Ps. Figure attached is a current configuration for the mentioned table.

[Former Member]

Few points to consider:

• Do selective initialization for datasource based parameters like company code and fiscal year
• This will allow the dataset to be broken into smaller chunk for delta extraction

Do this with indexing and this will help (as GL line items extraction needs extra care)

Cheers,

Suyash

[Former Member]

Hi Harish & Ramanjaneyulu

Thanks for your prompt response.

Do you know whether there is any issue in terms of existing reports performance? Functional users has raised the issues that they have once in a while created secondary indices and it turned out that their existing reports which used another index executed slower.

Thanks again!

[RamanKorrapati]

in our case it won't disturb as i guess.

For our data source table we will create index on timestamp field.

That is specially for BW Extraction purpose. to know this,  please check ecc table FAGLFLEXA-->display -> click on tool bar - index icon and see there.

You can apply at dev environment and see the performance.

if there is no impact of existing reports then that would be good to go ahead.

[former_member184884]

I don't think because of index creation your reports performance will not impact, it might be some other issue!!!

Please go ahead with index creation as i said earlier you've to create indexes both App server level & even same things needs to be done DB level then only you can achieve result... make sure of thorough testing in quality before moving this changes to prod environment.

Thanks & Regards,

Harish

[Former Member]

Hi,

Adding new index will not affect other report directly.

But it may affect other report indirectly as there are some new stuff for database optimizer to consider and the decision may change and lead to slow performance.

But I don't think it is a common case, and it is more likely the statistics is not update and/or not enough, which is a database admin issue.

So, make sure you rebuild the statistics for the tables you created the new index then you should be fine.

Regards

Bill

[Former Member]

Hi Raman,

  We also having performance issue with 0FI_GL_14 and  we have sap defined index 7 for timestamp for the table table FAGLFLEXA but it index is missing  for all database system(option). So now I want create new index with same field combination  as  index 7( given by sap) and select as index on all database systems. Is this is a correct way to proceed?

Thanks

Vinod

[RamanKorrapati]

Hi Thanoo,

2nd  option was useful.

You will create index at ECC side on data source base tables.

So in such case it won't disturb any of your reports.

But better to take downtime or handle this case at weekends or where 0 business hours.

Mean while please refer SAP Note 1397864 .

Thanks

[former_member184884]

Hi,

Please go for 2nd options i.e. creation of secondary indexes on the base tables.

with this you can except some sort of performance improvement in the data extraction.

when comes to downtime yes you've to create indexes on App & DB server level on weekends so that you'll have zero impact on business postings.

Thanks & Regards,

Harish