To maximize system performance, you need efficient data management. This especially applies to the biggest tables in the R/3 system such as line item tables and related indexes—for example, FI line item secondary index table BSIS. A new functionality introduced last year (archive connection for FI line item lists) helps manage the size of your database. It allows you to view line items from the archive as well as from the database.
The BSIS, BSAS, BSID, BSAD, BSIK and BSAK tables, which store FI line item data, are for historical reasons known by the term "secondary index tables." They are not to be confused with database indexes. Database indexes are also often called "secondary indexes" and are directly stored with their belonging table in the database. The FI secondary indexes are their own separate database tables.
A new archiving functionality allows you to view FI line items from the archive, which means you can delete the secondary index data earlier. It reduces the size of your database, and thus speeds up system performance.
I'll show you how to set up this functionality, so that for the first time your FI end users can obtain an entire overview of all periods of all accounts after archiving, even if they do not know anything about archiving. You need one of the following releases to be able to take advantage of the archive line item access: ECC 5.0; R/3 Release 4.70 – Support Package 14; R/3 Release 4.6C – Support Package 45; R/3 Release 4.6B – Support Package 54. The archived FI data will be just as visible to SAP applications via transactions FB03, FBU3, and line item display as the database data (BSIS, BSAS, etc.).