Delete Compressed requests

Dear All,
I am trying to delete the compressed request from the cube ;but it seems that deletion has not occured.
Please sugeest for the same.
Regards
Nidhi Walia

Hi Nidhi,
You cannot delete by the request ID if it is compressed. The other option would be to attempt Selective deletion by cube contents, if you can accurately highlight or pinpoint the data loaded by way of this request. Selective deletion is irreversible.
Once the requests are compressed the request number is set to 0.
Regards
KP

Similar Messages

Deleting compressed requests

Hi Experts,
In a cube i am having 15 requests in which 10 requests are compressed,Now due to some changes in the routines i have to reload the entire data again so i want to delete the data in the cube so how can i delete the data in the cube as 10 requests are compresed and the data is moved to E Table .
Can body tell me how to delete the data in the cube
For confirmation i can check in both the tables F and E once you tell me the procedure how to do it.
Regards,
Vikram ingh

Hi,
This is the procedure to empty the cube
right click on the cube-->delete data..it asks for two options select delete all entries..it deletes all the data from the cube(including compressed data and aggregates).
You cannaoit delete the compressed data by request wise. U can go for selective deletion.
Regards,
Malar

How to delete the compressed Request ID in the info cube... ?

Hi BW Gurus,
one of the info package will upload the request in to three data targets and failed due to error with duplicate records. I am able to delete the bad request in two data targets and facing problem with one data target due to the request is available in green and got compressed.
The reasons why i am unable to delete the request in that data target is it is already got compressed and rolledup.
I tried with selective deletion based on same request ID i have done that successfully but the request still presents in the data target. I have checked in listcube and found no data for the request id.
now i have one more question like the request has bring down to status not ok in the monitor and done selective deletion will it be a problem on the data missing please advise me if any data missing will occur for the particular data target.
can any one help on this. Thanks in Advance.
Venkat.

Hi Venkat
You have one way to delete the compressed request
But this is possible only if u have the request in PSA
If the request is in PSA, do reverse posting
This will nullify the particular bad request by changing the press sign into - and - sign into + for all the records went in the cube for that particular request
Regards
N Ganesh

How to delete the compressed request in bi 7.0?

how to delete the compressed request in bi 7.0?
Reverse Posting option available in BI 7.0?
Thanks,
Pramod

Hi Pramod,
Check this Thread,
Re: Selective deletion after compression
before posting a thread pls check in the forum.Lots of threads are already been posted related to your Query.
Hope this helps..........

Deletion of compressed request in BI 7.0

Hi,
I have loaded info cube by using process chain, in process chain I added compressed.
How to delete the compressed request from info cube .
Note : System is BI 7.0.
Thank you for advance.
Regards.
Suman.

Hi Suman,
Greetings.
Yes you can perform selective deletion of data from the compressed request in the Cube.
Either you can go to Manage option in the Cube and schedue there or use TCode delete_facts and delete from there.
If in case you want to schedule this deletion in a process chain, you will need to generate the program using delete_facts in dev and copy it to a Z program in Dev and add that in a process chain. Now migrate the program and the process chain.
Schedule it howvere you want it to be.
Let me know if it helps.
Thanks
Sachin

Non-compressed aggregates data lost after Delete Overlapping Requests?

Hi,
I am going to setup the following scenario:
The cube is receiving the delta load from infosource 1and full load from infosource 2. Aggregates are created and initially filled for the cube.
Now, the flow in the process chain should be:
Delete indexes
Load delta
Load full
Create indexes
Delete overlapping requests
Roll-up
Compress
In the Management of the Cube, on the Roll-up tab, the "Compress After Roll-up" is deactivated, so that the compression should take place only when the cube data is compressed (but I don't know whether this influences the way, how the roll-up is done via Adjust process type in process chain - will the deselected checkbox really avoid compression of aggregates after roll-up OR does the checkbox influences the manual start of roll-up only? ).
Nevertheless, let's assume here, that aggregates will not be compressed until the compression will run on the cube. The Collapse process in the process chain is parametrized so that the newest 10 requests are not going to be compressed.
Therefore, I expect that after the compression it should look like this:
RNR | Compressed in cube | Compressed in Aggr | Rollup | Update
110 |                    |                    | X      | F
109 |                    |                    | X      | D
108 |                    |                    | X      | D
107 |                    |                    | X      | D
106 |                    |                    | X      | D
105 |                    |                    | X      | D
104 |                    |                    | X      | D
103 |                    |                    | X      | D
102 |                    |                    | X      | D
101 |                    |                    | X      | D
100 | X                  | X                  | X      | D
099 | X                  | X                  | X      | D
098 | X                  | X                  | X      | D
If you ask here, why ten newest requests are not compressed, then it is for sake of being able to delete the Full load by Req-ID (yes, I know, that 10 is too many...).
My question is:
What will happen during the next process chain run during Delete Overlapping Requests if new Full with RNR 111 will already be loaded?
Some BW people say that using Delete Overlapping Requests will cause that the aggregates will be deactivated and rebuilt. I cannot afford this because of the long runtime needed for rebuilding the aggregates from scratch. But I still think that Delete Overlapping should work in the same way as deletion of the similar requests does (based on infopackage setup) when running on non-compressed requests, isn't it? Since the newest 10 requests are not compressed and the only overlapping is Full (last load) with RNR 111, then I assume that it should rather go for regular deleting the RNR 110 data from aggregate by Req-ID and then regular roll-up of RNR 111 instead of rebuilding the aggregates, am I right? Please, CONFIRM or DENY. Thanks! If the Delete Overlapping Requests still would lead to rebuilding of aggregates, then the only option would be to set up the infopackage for deleting the similar requests and remove Delete Overlapping Requests from process chain.
I hope that my question is clear
Any answer is highly appreciated.
Thanks
Michal

Hi,
If i get ur Q correct...
Compress After Roll-up option is for the aggregtes of the cube not for the cube...
So when this is selected then aggregates will be compressed if and only if roll-up is done on ur aggregates this doesn't affect ur compression on ur cube i.e movng the data from F to E fact table....
If it is deselected then also tht doesn't affect ur compression of ur cube but here it won't chk the status of the rollup for the aggregates to compress ur aggregates...
Will the deselected checkbox really avoid compression of aggregates after roll-up OR does the checkbox influences the manual start of roll-up only?
This check box won't give u any influence even for the manual start of roll-up....i.e compression of aggreagates won't automatically start after ur roll-up...this has to done along with the compression staus of cube itself...
And for the second Q I guess aggregates will be deactivated when deleting oveplapping request if tht particular request is rolled up....
even it happens for the manual deleting also..i.e if u need to delete a request which is rolled up and aggregates are compressed u have to deactivate the aggregates and refill the same....
Here in detail unless and until a request is not compressed for cube and aggregates are not compressed it is anormal request only..we can delete without deactivating the aggregates...
here in urcase i guess there is no need to remove the step from the chain...
correct me if any issue u found......
rgds,

Deletion of compressed request

Hi
I have two compressed in InfoCube
Req A - 200 records Timestamp 2008
Req B - 300 records Timestamp 2007
Now I want to delete the request "B" from the Cube which is beneath req A in the Cube.
I have already deleted the data for the Req B via selective delete, now the only thing I have been asked is to delete the request.
Can I delete the same via RSICCONT table and if so what is the Impact of the same.

Hi DPN,
Once u do the compression then the request idds will be deleted and the data will move from F table to E table, If u want to delete the compressed data then u have to do Request reverse posting for this you should have the data in PSA. If u do this all the in that request will be multiply with -1 and send to cube with new request, after that u have to do the compression so that + and - values will be cancelled.
I have already deleted the data for the Req B via selective delete, now the only thing I have been asked is to delete the request.
I dint understand this. Remember request ids will be deleted once u do compression.
Khaja

How to delete the rollup and compress request from the cube

Hi Experts,
I have a requirement, one request was updated into the cube and it was been rollup and then compressed. As the request was compressed so based on request id we cant perform the deletion.
So it is possible with selective deletion. Now before performing the selective deletion do i need to deactivate the aggregates.
Help me out on this.
Regards
Prasad

Hi.........
U hav to deactivate the aggregates................bcoz.........Selective deletion is only possible with uncompressed requests...............ie from F fact table...........after compression data moves from F fact table to E fact table.............. you can't do selective deletion on E fact table.........So first deactivate the aggregates............then do the selective deletion..............then again activate the aggregates..............and do the aggregate filling job manually in RSA1..............but I will suggest u delete the request...............bcoz any how u hav to deactivate the aggregates............and in case of selective deletion u hav to be very particular................if ur load is not taking much time............then delete the request and repeat the load............
Regards,
Debjani...........

Deletion of compressed request in cube

Hi All,
Is there any way i can delete a compressed request in a cube
and please keep mind that I also have other request in the cube there should not be deleted at any case as the source system of these requests is not connected to BW system now.
Regards,
Antony

Hi,
no, you can't delete a compressed request.
What you can do is to post the request reversal (all keyfigs x -1) provided you still have the data in the PSA or you can reextract it
or you can selectively delete the data of this request if you can find a selection criteria of the data to be deleted....
can you give more details on this request? was it a delta? coming from which DSource?
hope this helps...
Olivier.

Deletion of compressed requests

Hi,
can anybody tell me is there any way to delete compressed requess in cube.

Hi,
You can not delete a compressed request.
When you compress a request it moves from the F fact table to E fact table. Here in the E fact table you do not have the request-id column, hence the data can not be recognized with the request number when it is compressed(when the data is in E fact table).
One thing you can do is delete the data based upon selections >> Selective deletion can be performend in such cases if you have any particular parameters ex: date, doc no. range etc etc. to do so.
Regards,

Compression request deletion in cube bi7

please guide me how to delete
Thanks

Read abt Selective deletion.
Re: what is the use of request reverse posting in rsmo?
Re: Selective deletion after compression
Re: Info Cube Compression
Re: how can we delete the request after compression? is it possible ?if so how?
http://help.sap.com/saphelp_nw04/helpdata/en/ca/5c7b3cbd556915e10000000a114084/frameset.htm

It is possible to delete the request after compression

Hi,
It is possible to delete the request after compression,if it yes,how can delete the request.

Hi,
You cannot delete the request individually but you can one of the following:
1. Do a selective deletion from the cube. RSA1 -> Cube -> Contents -> selective deletion.
2. Delete all the data in the cube and then reconstruct only the required request ids. This would work only if you have the PSA available for all the requests.
3. Reverse posting is another possibility.
Bye
Dinesh

Deleting Infocube request (already rolledup and compressed in aggregate)

Dear All,
I found that there is one request which has incorrect data. This request was updated in cube and rolled up and compressed in aggregates. Now I changed request status to red and deleted it. This deletion request is running from last 20 hours. I checked the job log and found that it has dropped all the aggregate tables and refilling them. Since this cube has around 12 crore records its taking too much time to complete. Can i load further data while this deletion is happening? What will be best strategy to handle this situation?
regards:
Jitendra

Hi
If your data is not compressed in your cube then the best way is
1) deactivate the aggregates
2)delete the request from CUBE
3) reload the data to cube
4) fill the aggregates again
If data is compressed in CUBE, then you can not do the request based deletion. the only way to do is selective deletion.
When the deletion is work in progress, you can not load the data to the same target. target will be locked.
Regards,
Venkatesh

Cube Compression - How it Affects Loading With Delete Overlapping Request

Hi guys,
Good day to all !!!
Our scenario is that we have a process chain that loads a data to infocube and that has delete overlapping step. I just want to ask how does the cube compression affects the loading with delete overlapping request. Is there any conflict/error that will raise? Kindly advice.
Marshanlou

Hi,
In the scenario you have mentioned:
First the info cube would be loaded.
Next when it goes to the step i.e delete overlapping request: in this particular step, it checks if the request is overlapping (with the same date or accd to the overlapping condition defined in the infopackage, if the data has been loaded).
If the request is overlapping, then only it deletes the request. Otherwise, no action would be taken. In this way,it checks that data is not loaded twice resulting in duplicasy.
It has nothing to do with compression and in no way affect compression/loading.
Sasi

Can we delete the request after the Compression?

Hi All,
Can any body tell me, Can we Delete the Request after Compression?
Thanks In Advance
Regards,
Kiran Telkar

Hi
You can delete data by request id even after compression.
Steps:
1. Goto Monitor screen and select the particular request.
2. Click on the icon request reverse posting.
It will make the values of the key figure as "0" of that particular request. This is the way you can delete the contents by request id.
You can also do selective deletion and you will find this option in the manage screen of the data target under the tab contents.
Hope it works.
Assign points if it is usefull.
Regards
Saddy

Delete Compressed requests

Similar Messages

Maybe you are looking for