REPOLOAD, REPOSRC, REPOTEXT: Report Objects

The report tables (REPO*) are necessary for the basis of the ERP system and cannot be avoided, summarized, deleted, or archived by general mass operation reports. Deletion is only possible on the different application levels. These tables are used by for the generation of ABAP programs.

5.1.15.1 Avoidance Cannot be used

5.1.15.2 Summarization Cannot be used

5.1.15.3 Deletion

Report SDBI_REPO_CHECK or RSREPOSRCCHECK (SAP Basis 7.10) can be used to find out whether report sources are readable (see SAP Notes 658169, 69871). Within table REPOSRC, the program status column indicates if it is A (active) or I (inactive). If there are a considerable number of inactive programs, check if some of them can be decommissioned.

See SAP Note:

· 69871 (SAP_APPL 300 – 46C): Checking and cleaning up development environment tables · 658169 (SAP_BASIS 610 – 711): Checking report sources

· 1582301 (SAP_BW 700 – 730): Temporary RSDRD reports are not deleted 5.1.15.4 Archiving

Cannot be used

5.1.16 RSBERRORLOG (Log Entries for DTP Data Records with Errors)

Table RSBERRORLOG belongs to the SAP Business Warehouse (SAP BW) component and contains log entries about erroneous data records during uploads via the data transfer process (DTP). This technology is available as of SAP Business Warehouse (SAP BW) 7.0.

5.1.16.1 Avoidance

Check whether you need the log entries for specific or all data transfer processes. You can use the DTP error processing function to determine how the system handles erroneous data records and to deactivate error handling, if necessary. For more information seeHandling of Data Records with Errors.

5.1.16.2 Summarization Cannot be used

5.1.16.3 Deletion

You can use report RSB_ANALYZE_ERRORLOG to analyze which DTPs have generated error messages for data records and for how many records the messages have been created. You can use report

RSBM_ERRORLOG_DELETE to delete the messages for requests up to a specified date for individual DTPs (SAP Note 1095924 SAP_BW 700 – 710, SAP_BW_VIRTUAL_COMP 700). Before you delete large data volumes, it is essential that you implement SAP Note 1144400 (SAP_BW 700 – 711,

SAP_BW_VIRTUAL_COMP 700).

5.1.16.4 Archiving Cannot be used

5.1.17 RSDDSTATAGGRDEF (Statistics Data OLAP: Navigation Step / Aggregate Definition)

Table RSDDSTATAGGRDEF belongs to SAP Business Warehouse (SAP BW) and contains entries that are not linked to other entries from tables RSDDSTAT* (BW statistics data).

5.1.17.1 Avoidance For SAP BW 7.0 or higher:

You can prevent SAP BW statistics data from being created as follows:

On the Maintenance of Statistics Properties screen (transaction RSDDSTAT, you can edit the statistics properties for individual objects as well as the default settings for the different object types.

Maintaining the statistics properties of a BEx Web template or a BEx workbook only has an effect on the creation of the respective front-end runtimes. However, maintaining the statistics properties for queries (or InfoProviders) only affects runtimes in the analytic engine and in the data manager. A complete recording of the runtime (data manager – analytic engine – front end) is, therefore, only guaranteed if the statistics properties are maintained for the relevant query and front-end objects.

Note: The system records a large amount of detailed runtime data as part of the BW query runtime statistics. Recording the runtime of a navigation step for a query can generate on average 20 to 40 records, depending on the level of detail of the statistics.

Deactivate the detailed runtime recording for all objects for which you do not require performance analyses.

Refer to SAP Library for more information at

http://help.sap.com/saphelp_nw70/helpdata/en/43/e37f8a6df402d3e10000000a1553f7/frameset.htm

5.1.17.2 Summarization Cannot be used

5.1.17.3 Deletion

For SAP BW 7.0 or higher:

The following deletion report exists for the BW statistics data tables:

To delete BW statistic data manually, go to the Maintenance of Statistics Properties screen (transaction RSDDSTAT) and choose Delete Statistical Data.

Using the Up to Day (Incl.) field, you can enter a date up to which the system is to delete the statistics data. If you do not enter a date, all data is deleted. Since this can be executed with a command (TRUNCATE

TABLE) and not using selective deletion in the database, this version is considerably faster.

By restricting to one day, packages of only 1000 records are always deleted from the tables; this is followed by a database Commit. This makes it possible to restart after a termination (resulting from a TIMEOUT, for example) without a need to redo previous work.

Please read also SAP Notes 934848 (SAP_BW 700 – 711, BI_CONT 702 – 704) (Collective Note: [FAQ] BI Administration Cockpit) and 1018114 (SAP_BW 700 – 710, SAP_BW_VIRTUAL_COMP 700) (Additional date restrictions for deleting statistics data).

Note: When using technical content, deletion of statistics recording for query runtime statistics (relevant for tables RSDDSTATHEADER, RSDDSTATINFO, RSDDSTATEVDATA, and RSDDSTATDM) is automated. Deletion takes place when the data is loaded into the InfoCubes of the technical content. The DataSources 0TCT_DS01, 0TCT_DS02, and 0TCT_DS03 automatically trigger a deletion of all data in the underlying statistics tables that are older than 14 days. This deletion is part of a delta upload. If necessary, this interval can be defined on a customer-specific basis in table RSADMIN using the parameter

TCT_KEEP_OLAP_DM_DATA_N_DAYS.

See SAP Note 891740 (SAP_BW 700, SAP_BW_VIRTUAL_COMP 700) for further details.

If you delete data from table RSDDSTATLOGGING and the system issues an error that is caused by database resources that are too small (space is too small), see SAP Note 1476860 (SAP_BW 700 – 711, SAP_BW_VIRTUAL_COMP 701 – 711) for further information.

Note:

Report RSDDSTAT_DATA_DELETE cannot be used to delete SAP BW 3.x statistical data in table

RSDDSTATAGGRDEF and RSDDSTAT in SAP BW 7.x systems. See SAP Note 1510697 (SAP_BW 350 – 702) for the available options for cleaning up obsolete entries from these tables.

5.1.17.4 Archiving Cannot be used