Compression of requests in a cube

Document Version / Dtails : Ver 1.0 / 22-Apr.-2011

Record Of Release

Version No. 1.0

Created/Modified By Gayathri.R

Reviewed By Pawan Chaturvedi

Release Date 22/04/2011

Modifications Done Initial

Project ID:

E6806

Project Name:

FSS BW Operation

Scope of Document: This document helps us to understand the process of compressing the requests in a cube.

What is compression? Each data Load done in an info-cube is uniquely identified with a request ID. Deleting these meaningful load identifiers in info-cubes is called as Compression. Compression improves Performance Tuning as it removes the redundant data.

Step1: Log in the SAP. Enter below details: Connection Type: Custom Application server Description: GRP Application server: 155.111.150.189 (we can use from 187 to 194) System ID: GRP Client: 400

Step 2: Enter user name and password.

PM-03-04 Ver 1.0/22-April-2011

Page 2 of 12

Step 3: How to do Compression? Go to RSA1 >> Select Cube >> Manage >> Requests (Tab)

Step 4: After clicking Manage, below screen will appear. You can see that under the tab of requests, there are two Cs. The first C refers to Compression of requests and the second C refers to compression of aggregates. Now to compress certain requests, you must first view the requests. So in the request display, enter the date up to which the requests have to be deleted and click on refresh.

PM-03-04 Ver 1.0/22-April-2011

Page 3 of 12

PM-03-04 Ver 1.0/22-April-2011

Page 4 of 12

Step5: The below screen pops up.

The tick marks tell that the compression of those requests have completed. Now, let us see how to compress the requests. Here, this is an illustration of compressing a single request. One can compress many requests in a time. For that, the last request id has to be to be taken. It can be seen the highlighted area is the request id. We are going to compress this request.

PM-03-04 Ver 1.0/22-April-2011

Page 5 of 12

Step 6: Go to the collapse tab, enter the request id, then click on release.

PM-03-04 Ver 1.0/22-April-2011

Page 6 of 12

Step 7: When you click on release, it asks to specify the name of the application server. We need to enter the server group as GRP_STANDARD_BTC.

PM-03-04 Ver 1.0/22-April-2011

Page 7 of 12

Step 8: Now it will show the compression job in progress stage.

PM-03-04 Ver 1.0/22-April-2011

Page 8 of 12

Step 9: To see the status of the job activity, copy the job name from the collapse tab and enter in sm37 job monitor.

PM-03-04 Ver 1.0/22-April-2011

Page 9 of 12

Step 10: To know the job status go to sm37 you can also enter your user name credentials. Enter the appropriate dates.

PM-03-04 Ver 1.0/22-April-2011

Page 10 of 12

Step 11: You can see the job status active. Keep refreshing, once job is completed, the job status changes to finish. Upon clicking refresh, the status will show finished when job gets over.

PM-03-04 Ver 1.0/22-April-2011

Page 11 of 12

Step 12: After that, you can check in the cube the compression has completed which is indicated by a tick mark.

PM-03-04 Ver 1.0/22-April-2011

Page 12 of 12