Check compression of Infocube

How do i check that compression of the infocube was successful.
I did check the number of entries in the E table.
But is there another way of checking that compression of the infocube was successful.
Thanks for help.
Michelle

Thanks Roberto.
I awarded you 10 points for ur help.
I appreciate it a lot.
I am looking for SAP BW project plan template, Business requirement gathering template, data flow from r/3 to bw template and reports technical template.
Michelle

Similar Messages

Compressing an infocube with agregate

Hi all,
I hade compressed an infocube with agregate.
In the infocube manage (RSA1), the compress status are OK (infocube and agregate), but the job compress run always, it did not stop .
Can you explain me the possible reasons please ?
Thank you in advance,

HI aziz,
check this link..
Compress job that took an unusually long time
cheers
Sunil

Compress an InfoCube

Please explain the steps to compress an InfoCube with marker update"
Regards,
Keith

Hi Keith,
RSA1 --> Your Cube --> right mouse click --> Maintain --> Tab Compression --> Select request till you want to compress --> Flag Marker --> Start compression.
It is a very slow process if you have a lot of request/data, try to execute when you have not jobs running.
Ciao.
Riccardo.

How to check workbook by Infocube

Hello bw gurus,
Is there a way to check Workbooks by Infocube. I am trying to check work by infoarea/ infocube but When I open the /ORRMX and open workbooks new pop up window gives me option to open work book by ROLE, Favourites and History.
I want to open the workbook like query where pop up window give u option to choose the infoarea first and then drilldown to infocube.
your help is highly appreciated.
I will immediately assign point to valid answers.
Thanks
Hitesh

Ok. So you can insert different queries in a workbook using the Tools button on the Bex toolbar. First you'll execute a query that you want to include in the workbook, then if you want another query on the second sheet, click and position your cursor on the second sheet and from the Tools button > Insert Query > then select the second query that you want to be part of this workbook. Similalry you can add more...
You can also read through it here:
http://help.sap.com/saphelp_nw04/helpdata/en/f1/0a55dfe09411d2acb90000e829fbfe/content.htm
To check which query is being used in the workbook, you can display it using the Text elements. From the Layout button on the Bex toolbar > Display Text Elements > General. You will see some rows added after the free chars and one of them has the name of the InfoProvider.
Hope this helps...

How to debug compression of InfoCube

The compression of our InfoCube is failing. Can someone recommend places in the code where I can set breakpoints so that I can troubleshoot this issue?
Thanks.
Ron

Couple checkpoints if you are using non-cumulative cube check this
985774 - Compressing non-cumulative cubes creates incorr ref points
Also did you try manual compression or its process chain enabled,could be load running while you doing compression??
what exactly is the error message
Hope it Helps
Chetan
@CP..

Error while compression of infocube

Hello,
I am facing following error while compression of inventory cube
ORA-04098: trigger 'SAPPW1./BI0/0500014656' is invalid and failed re-validation
Request have been loaded in the ranges of posting date and those request are not getting compressed.Can you help?

Please check the following SAP note . It might help you..
Note 385660 - Condenser: DBMAN 100; ORA-4098
https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=385660

Compress Requests Infocube

hi gurus...
i know that compressing requests move datal from E table to F table (or F to E) , so I have a basic infocube 7.0 with a lot of request with no compression, I m plannin to run compression of all request and include zero elimmination, i know that after compression a request can not be deleted no more, so i d like to know what r the dissavantages of doing this? amounts will be the same...
regards
joker

Hi,
Please remember the follwoing wrt compression :-
1. Start teh compression of few req together as it takes up a lot of system memory.
2. It adds one more step to the data loading process and hence the overall run of the process chain increases
3. Once compressed you ant delete the data request wise, you will have to run a selective deletion.
And the advantages are :-
Query access is faster
Cube size comes down - this helps in tasks like rebuild of aggregates etc.
Indexes are better maintained
Data Load is more efficient because the F Table has fewer requests ane lesser data.
Hope this helps.
Regards,
Rahul

Check statistics in Infocube

Hi all,
When i go to Right click --> Manage button and then Performance tab of any infocube i get 3 areas for concern.
Check index which is Green for my infocubes.
Check aggr index is also Green for my infocubes.
Check Statistics --> This is where i am getting Yellow signal.
I just hope these statistics are different from what we generate from
DB13 as daily job.
I also tried to Create statistics with Create stats button and triggered
job BI_INDX_STATISTICS_BW successfully.
But even after finishing that job so many days , i am still getting
Yellow symbol for Check statistics button.
Please let me know what is exact procedure to generate stats for Infocube and when ???
Appreciate your quick replies.
Best Regards,
AjitR

Refreshing the stats should start a job. Are you running it in background. NO job running would really sem to be the problem to look into. The job would refresh stats on the fact tables, the dimension tables and all the master data tables of characteristics in the cube.
RSRV should identify what tables are yellow.
Keep in mind, the Warning process used is nothing very sophisticated. SAP simply checks the date statistics were last collected on a table and if it is over 30 days old, flags it with a warning, regardless of how accurate/inaccurate the stats actually are. You very well may have tables that are being flagged because of the date last analyzed > 30, but if the table(s) being flagged really don't see have lots of records added, then the older stats are still perfectly fine.
The best method for handling DB statistics collection is to check with your DBA and make sure they are running BRCONNECT daily. It can be conifigured to refresh stats based on some percentage of table activity, e.g. addition of more than 25% new rows since last time stats were refreshed causes new stats on that table to be collected. If BRCONNECT is running regularly, then you don't need to worry about the yellow warnings - the tables that have regular activity will have stats updated by BRCONNECT, and tables that don't see much activity won't waste time rfreshing stats unnecessasarily.

Check size of infocube in terms of K (100 K or more dimension members)

Hi Experts,
How can I check Infocube size in terms of K (100 K or more dimension members) ?
Full points will be assigned.
Thanks!
Sapna

Hi Rakesh,
Thanks for your reply. I am assigning you full points.
Is there a tuning parameter in BW to increase the result buffer?
Thanks!
Sapna

How to identify that an InfoCube needs to be compressed?

How to identify that an InfoCube needs to be compressed?
Is there any ratio or method to check that the InfoCube is ready enough to Compress.

Hi Chandran,
When a request is loaded and aggregated(rollup) it is ready for compression. I don't understand what u mean by <i>"ready enough"</i>.
As SAP says, compressing the requests in InfoCube improves the query performace as it reduces the amt of data by eliminating request ids and do Zero elimination. see below link for detailed adv and disadv of compressing a cube.
http://help.sap.com/saphelp_nw04/helpdata/en/ca/aa6437e7a4080ee10000009b38f842/frameset.htm
Regards,
Sree

Did Infocube compression process locks the infocube?

HI All,
First of all thanks for ur active support and co-operation.
Did the compression process locks the cube?, my doubt is, while the compression process is running on a cube, if i try to load data into the same cube, will it allow or not? please reply me as soon as u can.
Many Thanks in Advance.
Jagadeesh.

hi,
Compression: It is a process used to delete the Request IDs and this saves space.
When and why use infocube compression in real time?
InfoCube compression creates new cube by eliminating duplicates. Compressed infocubes require less storage space and are faster for retrieval of information. Here the catch is .. Once you compress, you can't alter the InfoCube. You are safe as long as you don't have any error in modeling.
This compression can be done through Process Chain and also manually.
Check these Links:
http://www.sap-img.com/business/infocube-compression.htm
compression is done to increase the performance of the cube...
http://help.sap.com/saphelp_nw2004s/helpdata/en/ca/aa6437e7a4080ee10000009b38f842/frameset.htm
http://help.sap.com/saphelp_erp2005vp/helpdata/en/b2/e91c3b85e6e939e10000000a11402f/frameset.htm
Infocube compression and aggregate compression are mostly independent.
Usually if you decide to keep the requests in the infocube, you can compress the aggregates. If you need to delete a request, you just have to rebuild an aggregate, if it is compressed. Therefore there are no problems in compressing aggregates, unless the rebuild of the aggregates take a lot of time.
It does not make sense to compress the infocube without compressing the aggregates. The idea behind compressing is to speed up the infocube access by adding up all the data of the different requests. As a result you get rid of the request number. All other attributes stay the same. If you have more than one record per set of characteristics, the key figures will add the key figures by aggregat characteristic (ADD, MIN, MAX etc.). This will reduce the number of records in the cube.
Example:
requestid date 0material 0amount
12345 20061201 3333 125
12346 20061201 3333 -125
12346 20061201 3333 200
will result to
requestid date 0material 0amount
20061201 3333 200
In this case 2 records are saved.
But once the requestid is lost (due to compression) you cannot get it back.
Therefore, once you compressed the infocube, there is no sense in keeping the aggregates uncompressed. But as long as your Infocube is uncompressed you can always compress the aggregates, without any problem other than rebuild time of the aggregates.
hope it helps..

Check Infocube Basic or Transactional

Hi all,
I want to check if an Infocube is basic or transactional with Function Module; I've tested the return of FM RSD_CUBE_GET_ONLY_DB but in the field l_s_cube-cubetype always "B"....
I've analyzed the FM: RSAPO_CLOSE_TRANS_REQUEST; RSAPO_SWITCH_TRANS_TO_BATCH, RSAPO_SWITCH_BATCH_TO_TRANS, ... But my problem is tested only the type of infocube (Basic or transactional) moreover if transactional even if the cube can be planned by function SEM.
I have found the table RSMDATASTATE and the field LOADALWD... for me this field is perfect.... I want to check this by Function Module...
you know some Function Module....
any help is appreciated.
regards,
Alessandro
Message was edited by: Alessandro Gasparro

Thanks Paolo,
But in this table, the field TRANSACT not change if switch te Infocube, so the field value is always "X"..., moreover the field CUBETYPE is always "B"... I do not know the operation of this table. I think that the function RSD_CUBE_GET_ONLY_DB test this table,.....
Regards,
Alessandro

Deselect auth. check for infocubes (Checks for infocubes) in RSSM

Hi,
An infocube I installed contains an authorisation relavant object (already exists) in BW3.5 system. By default the infocube is selected for auth. check in RSSM.
After I transported the cube to target system I realised the auth check in RSSM has also been transported with the cube.
Hence, I have deselected the auth. check for the infocube "Checks for infocubes" in RSSM and saved it. Then, I created a second transport and only transported the cube. But the changes I made in RSSM hasn't been transported.
Please can you advise me how to transport the changes I made in "Checks for infocubes" in RSSM?
Thanks a lot
Murali

Hi,
check this threads:
Re: RSSM: Checks Authorization Objects for Infoprovider are not activ
Re: RSSM Transports
Normally system would check all the authorization relevant objects whenever a new Info cube is imported and in case if you want to transport these changes to Production system manually then follow the below listed steps:
1) In Development system, check or un-check the authorization relevancy using the transaction RSSM on a given Info provider
2) These changes are stored in table RSSTOBJDIR
3) Create a manuall transport request and include these entries covering the required Authorization objects manually.
R3TR TABU RSSTOBJDIR
Ex: If Info object 'A' is authorization relevant in Development system but not in Production system and you want to transport this change to Production system then include object 'A' table entries manually.
Regards
Andreas

No Marker Update in InfoCube compression

Hi,
Please explain me how the No Marker Update works in InfoCube compression of inventory management.
Best Regards,
Ramesh

Marker update when uploading/compressing
We will use an example to explain the procedure for a stock InfoCube
when executing a query. The scenario is as follows:
     Current date: 31.03.2002
     You have set up an opening balance of 100 units on 01.01.2002 and loaded it into the stock InfoCube.
     Historical material movements from the three previous months (October 2001:10 units; November 2001: 20 units; December 2001: 10 units) are loaded into the BW.
     Since this point, successive material movements have been transferred into the BW in the delta process. Delta requests transferred at the end of January (20 units) and February (10 units) were already compressed after successful validation, the last delta request from the end of March (10 units) is still in the InfoCube in uncompressed form.
To help explain the role of the marker (= reference point), the different upload steps are considered over time.
After uploading the opening balance, the InfoCube looks like this:
You can see that the opening stock is not assigned to the actual date, but posted to a
point in infinity (0CALDAY= 31.12.9999, for example).
After the three previous months have been uploaded and compressed, the InfoCube
content looks like this:
Note here that the marker value remains unchanged at 100 units. This can be achieved
using the No marker update indicator during compression (see section 3.2.2, step 6).
The marker is thus not changed.
After successively uploading deltas from January to March, of which only the first two are
compressed, the InfoCube content has the following appearance:
Compressing the requests for January and February executes a marker update that can
be seen by the marker now having the value 130 units. The values for March have not
been included in the marker yet.
Please go though the document:
How ToHandle Inventory Management Scenarios in BW
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328
Cheers
Pagudala

HOW DOES COMPRESSION OF AN INFOCUBE INCREASE THE LOAD PERFORMANCE?

Hi all
I see that Compression of infocube is one of the parameters to improve/increase load performance. If I am not wrong, Can some one please explain how compressing a cube improves the load performance?
Thanks in advance
Rishi

Hi,
I see that Compression of infocube is one of the parameters to improve/increase load performance. If I am not wrong, Can some one please explain how compressing a cube improves the load performance?
As per my information Compression improves the Quaer performance not loading perforamnce
when u do compression the same characterstics which are having the same values those records will be moved to E Fact table
ex Custno   Mat NO Qty   Value
      C101     M101     10      100
      c101     m101      20      200
when u do comperession the recors will be compressed as below
c101   m101 30 300
when the query execution instead of reading two reocrds and compressing at the time of producing output at report level
but when already compressed it fetchs one record directly form E table like that the query perforamnce will be improved.
Not loading perforamnce.
Thansk & regards,
sathish

Check compression of Infocube

Similar Messages

Maybe you are looking for