Question:
Hello -
I have an infocube on BW 2.1 that contains some duplicate requests. The data was originally loaded via flatfile. All of the data in the cube has been aggregated but the requests in question have not been compressed. Is there a way for me to reverse post the duplicate requests? What are the steps to do that? I'm trying to avoid rebuilding the aggregates as one of them took 31 hours to build the first time!
Thanks in advance for any advice!
Beth Phlegar
Owens Corning
beth.phlegar@owenscorning.com
Answer:
your aggregate is a subset of the info in the cube;
you want to change data in the cube without changing the aggregate;
how do you think the system could be able to achieve that ?!
delete the request from the cube, if your changes are not too much, the aggregate will be modified - not rebuild from scratch, so could be shorter
Ch
Answer:
CH -
Thanks for your reply. I guess my initial message was not clear enough. I DO want to update the aggregate, I just don't want to have to recreate it from scratch. I was hoping I could reverse post the request so that the offsetting entries would, in effect, delete the request. I thought this might be a way around having to recreate the entire aggregate. We don't have a great deal of experience with aggregates and I don't have any experience reverse posting a request although I believe I've seen references that suggest it can be done. When I try to delete the request, BW gives me a message saying it can't because of the aggregate.
Can you confirm, is there a way to reverse post a request that has already been aggregated?
Thanks,
Beth
Answer:
to be able to delete the request you first need to deactivate the aggregate, then delete, then reactivate ; but then I am pretty sure the aggregate will be rebuild from scratch (I was a little bit too optimistic in my first answer)
trying to reverse the request is a good idea,
I don't think there is any easy way to do it (but would welcome any comment on this)
something that is possible if your request is still in the PSA :
temporarily modify your update rules to revert each key figures, then upload the request again from the psa (*)(and then don't forget to re-revert your update rules !)
this way your additional request would reverse the wrong one and the aggregate will just have to be slightly modified to encounter the new request
'hope this is clear enough
Ch
(*) if not, tell me, I have other ideas