House Keeping Activities for Archiving in BW System

Applies to:

SAP NetWeaver Business Warehouse (formerly BI). This will also work on SAP BI 3.5 and BI 7.0.

Summary :

This document will help to understand the various Housekeeping Activities required to perform before implementing Archiving in BW system.

Author: Arpit Khandelwal.

Company: Accenture Services Pvt. Ltd.

Author Bio:

Arpit Khandelwal is a SAP BI Consultant currently working with Accenture Services Private Limited. He has around 2 years of experience in  BW/BI implementation and support projects. He has been particularly involved in Archiving Activities in SAP BW system.

Methodology ::

Scope of a project needs to be defined while starting a Archiving Project.

For this, you need to identify the DSO’s  and Infocube’s where most of the data is retained for many years.

Next part of the project scope is the Basic Housekeeping Activities for the System/Log Tables. Also apart from the System/Log Tables we need to do housekeeping for the Data Targets also with the data that might be obsolete for reporting  or  legal retention pupose . This is where we will particularly focus in this article.

Eventually on the basis of DB size and growth of data in in system log/tables we need to define the House Keeping Activities ::

This might include some of the below House Keeping activities::

1)  Deletion of DTP Error Logs::

House keeping of DTP error logs should be deleted using Standard SAP programs. Hence further check on DTP integrity won’t be required.

DTP Error logs are stored in system log table RSBERRORLOG.

Program RSBM_ERRORLOG_DELETE  is used to delete all the DTP Error Logs.

Steps to do the same ::

a) Run Program RSBM_ERRORLOG_DELETE. Below screen will appear.

b) Input the Start Date and End Date as per requirement. Else mention the “but always older than … days” for which we want the retention period for these logs and rest all older than that will be deleted.

.

c) Execute the program in background.

2)  Compression of Infocube Data ::

An Infocube won’t be archived until the requests of the cube are compressed.This is a mandatory condition.

How to compress request would have been quite known to all of you. Still steps are provided as below.

Steps to do the same ::

a) Go to RSA1 transaction and then goto Manage option of the Infocube.

b)  Goto Collapse tab and put the request ID till the level where you want to compress the requests.

c) Click on Release. Collapse symbol will appear in Cube’s request.

3)  Deletion of unused Aggregate ::

Aggregates needs to be shortlisted for this. Criteria should be that those particular aggregates should not been used in query execution and aggregates should be almost as large as the parent aggregate from which they were created.

Steps to do the same ::

1) Function module RSDDK_AGGREGATES_DEACTIVATE can be used to delete the unused aggregates.

2)  In case, this functional module is not available then we need to go through manual process of Aggregates Deletion.

a) Goto Maintain Aggregates option of the Cube for which aggregate has been decided already to be deleted.

b) Then we need to select the aggregate required for deletion. Click on delete symbol to delete the aggregate.

PS :: Kindly note that you should be very sure and careful of what you are doing at this stage.

4) Clean up of BI Statistic Table ::

We can delete old BI statistics tables data through ABAP Program RSDDSTAT_DATa_DELETE We can delete old BI statisticstables data thru ABAP program RSDDSTAT_DATA_DELETE. We can choose specific statistics tables to delete & older than date criteria in the selection screen below.

5) Deletion of BW Background Management (RSBATCH) information ::

Delete the messages from BI background management as well as the internal parameters of the background processes that are executed by background management on a regular basis. This prevents table RSBATCHDATA from overflowing.

Steps to do the same ::

a) Run transaction RSBATCH BI Background Management, Logs and Toolsscreen.

b) On the next screen, define after how many days the internal messages of BI background management and the internal parameters of
the background processes should be deleted. This setting should normally prevent table RSBATCHDATA from being overfilled.

When defining the deletion selections, make sure that you keep the data as long as necessary in order to track any problems that might occur.

c) To define the starting conditions for the deletion job, choose Schedule. Select immediate or appropriate time in the Job schedule screen.

d) A Batch Manager Logs deletion program is executed in background.

Verify that the job is executed successfully in SM37.