compression problem

[Former Member]

Hi All,

If we compress the request data moves from F-table to E-table and all the requset id's are deleted from F-table why?

[Former Member · Accepted solution]

Hi,

When data is loaded into Info cube, they are grouped with Requests ID. It is possible that there can be the same data record in different requests. This can be solved by compressing data and bringing data from different requests together into one single request (request ID 0). Compression will move the data from F Fact table to E Fact table and aggregate the records based on similar characteristics. After Compression the E fact table is optimized for reporting and the F fact table is optimized for data load and correction.

http://help.sap.com/saphelp_nw70/helpdata/en/ca/aa6437e7a4080ee10000009b38f842/content.htm

http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/c035d300-b477-2d10-0c92-f858f7f1b575

Thanks.

[Former Member]

Hi ....

Compressing means now you can't split the records request wise..........they are in a consolidate form....

The request ID concept can also cause the same data record to appear more than once in the fact table. This unnecessarily increases the volume of data, and reduces performance in Reporting, as the system has to aggregate using the request ID every time you execute a query.

Using compressing, you can eliminate these disadvantages, and bring data from different requests together into one single request (request ID 0).

Please check the below link :

http://help.sap.com/saphelp_bw30b/helpdata/en/ca/aa6437e7a4080ee10000009b38f842/content.htm

Regards,

Debjani....

[Former Member]

Hello,

Once all the request Id's get deleted from F fact table and move to E fact table in a single request. By this packet dimension will also be deleted and thus that deleted space will be used as buffer for increasing the reporting performance.

Thanks

PT