FI Transactions e.g. FAGLL03, performance is bad when look for archived data

[former_member613838]

Hi All

We have some questions about FI transactions related to archived data.

Out team set up data archiving for FI_DOCUMENT with SAP basic functions.

FI transactions , e.g. FAGLL03, FBL1N, FBL5N the response is really bad, when get the archived data.

Before FBL5N finished within a minute, but currently it took several hours some times.

2 questions below:

Q1: In the case of file input/out response is bad, the transactions like FBL5N finished within 1 minute before,

after archived, took several hours, is it usual?

Q2: Is there any good solution to avoid performance degradation when get archived data with FI transactions?

[former_member201157]

The transaction FAGLL03 reads  the FAGLFLEXA index and the transaction FBL3N reads the BSAS index.

check these notes also 1852923,798540.

1135916 - Line items: Help for analysis for long runtime

read 2. How does transaction FAGLL03 select the data? in this note

the indexes and placement of archive files will impact performance .

remember the program is not reading data from tables but in archive files that are stored in file system or a content repository.

take the help of ABAP to put a trace on the FAGLL03 and determine best route to improve performance.

if you notice that there is significant lag or delay in the programs that read archive data, report to SAP as well