Difference vs rollup and aggregation

Hey guys,
I know they are both the same i.e. Rollup and aggregate. i guess I need to know the difference between MAINTAIN AGGREGATE (when you click on an infocube it gives you the option to maintain aggregate) and ROLLUP (when you go to manage an infocube and click on the tab called Rollup. Also I need to know if there is a document or an article that would tell me the criteria of creating aggregate.
Thanks and your help is much appreciated as always,
RG

Hi Ram,
Rollup is like delta from Cube to the agggregates. When ever we post a new data into Cube, the need to be updated into t he aggregate tables to be visible in reporting. If you have aggregate on a cube, then when new data gets into the cube, there is a process to fill the new data into the aggregate and this process is called roll up.
Rollup is the process to load deltas into aggregate from cube.While you are creating the aggregate you have to fill the aggregateit is right.. that is initial fill. After that new data will come to cube, thisnew/delta data should be reflected in the aggregate for further reporting.o do this we use to run ROLLUP in the info cube manage option.f it's not rollup and the cube is having aggregate and the aggregate is in active mode, then you won't get latest information in your query.
Importance of Rollup:
1. once you load data into Infocube is to ensure that recent data is available for reporting.
2. Rollup analyze and updates database statistics for aggregate objects.
Pls check this link..
http://help.sap.com/saphelp_nw04/helpdata/en/9a/33853bbc188f2be10000000a114084/frameset.htm
When you try to maintain/create aggregates, inside the maintain aggregate window, from the drop down menu, there is a propose from query option, try that will help to build an aggregates for you
Criteria for Aggregation:
http://help.sap.com/saphelp_erp2005vp/helpdata/en/9a/33853bbc188f2be10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/75/21054da1392649948e5b94e4fc4bce/content.htm
http://help.sap.com/saphelp_erp2004/helpdata/en/82/f2dc37f0f12313e10000009b38f8cf/content.htm
**Pls assign points if info is useful*
Regards
CSM Reddy

Similar Messages

Difference between Compression and Aggregation

Hi,
Can anybody explain the Difference between Compression and Aggregation.Performance wise which is better and explain me in detail.
Thnaks,
Chinna

Hi,
suppose you are having three charecteristics in a cube say X,Y,Z..
Even for the records which are having the same combination of these charecteristics but are loaded with different request they won't get aggregated.
So when you go for compression the records , it deletes the request number, and aggregates the records which are having the same combination of these records.
Coming to the aggregates , if you build a aggregate on the charectaristic say 'X' then it aggregates the records which are having the same value for a particular charecteristic.
ex: say you are having the recrds as
x1, y1 ,z1......(some key figures)
xi, y2,z1,.....
x1,y1,z1,....
x3,y3,z3...
If you compress them, you will get three records.
If you go for aggregates based on the charecteristic 'X' you will get two records.
So aggregates will give more aggregate level of data than compression
regards,
haritha.

What is the Difference between Consolidation and Aggregation

Hi Masters
What is the difference between Consolidation and Aggregation? i think both are same, what is the exact difference in-terms of HFM and Essbase?
regards
Taruni

The differences lies in the mechanism used to calculate and store the value. Dynamic members such as parent accounts or customs, derived views, parent periods, or <Total> members in the value dimension are performed on the fly in the HFM app server's memory without any discrete action on the user or adminisrator's part. These are aggregations in this context, and are distinct from amounts that are calculated and then stored in the HFM database which are either the result of direct data entry (from data loads or journals) or calculated amounts resulting from HFM's rules. "Consolidation" in your question would be one of the stored, calculated amounts in HFM.
--Chris

Difference between composition and aggregation

Could anyone explain to me the difference between aggregation and composition. I remember studying some but cant recall it.

though this question has been put in for quite some time now but being of an interesting nature I would like to answer that still.
As far as I know aggregation is a simple has a relationship
e.g A student has books.
A professor has students.
Naome has a Car.
Now you cannot say that : -
A student is composed of books.
However in composition the relationship is has a, is composed of .
So A university is composed of many schools.
A car is composed of parts.
A housed is composed of windows.
The second type of relationship is compositiob while first one is aggregation.

What are the major differences between a Access Switch and Aggregation Switch w.r.t Carrier Ethernet domain?

In a Carrier Ethernet domain,Could someone please help me understand what's the basic difference between Access Switch and Aggregation Switch both in terms of s/w and h/w functionalities. MEF deals OAM,CFM, EVC provisioning only at the access edge switches. Do we need to repeat all these at the aggregation level? or is it just used for routing purpose? Do we have a separate Fault Management at the aggregation level?

Duplicate posts. :P
Go here: https://supportforums.cisco.com/discussion/12137156/what-are-major-differences-between-access-switch-and-aggregation-switch-wrt

Difference between Property binding, Aggregation Binding and Element binding?

what is difference between Property binding, Aggregation Binding and Element binding?

HI Rajesh,
Firstly ,
A binding path can either be absolute (starting with a slash), or relative (starting with a name token)
1. Element Binding:
Here we specify the refrenced object.
eg if you bind company object to a layout, like
var oMatrixLayout = new sap.ui.commons.layout.MatrixLayout();
oMatrixLayout.bindElement("/company");
then all the children of this layout can refer to the context of this object. like suppose company has name attribute, then we can directly pass it to the child like:
oMatrixLayout.createRow(
new sap.ui.commons.Label({text: "Name:"}),
new sap.ui.commons.TextField({value: "{name}"})
All the relative bindings within the control and all of its children are resolved relatively
2. Property binding is similar to the context mapping in WebdnyPro. We bind it to a property of the UI. It is automatically updated when its vlaue is changed.
3. Aggregation binding (basically a list) defines a template(a model which others can copy) and this template is cloned for each entry of the list. When we make an entry in the list, a clone of the template is created.When the clone is created, the context is set to the entry in the list. Thus all the binding to the template are resolved relative to the entry. This is maily used for large data sets where we will only clone the current entry and not the complete list.
Regards,
Nikhil

How to delete a request in a collapsed and aggregated infocube ???

Hi all,
The situation :
I have a cube that is collapsed, and that has aggregates.
I'm not the one that designed this cube but if my understanding is good, aggregates were created to avoid the duplication of the recordings for the same key of characteristics because of the multiple loading. Actually KFs of the same recording are fed by various chains. Each chain creates a segment for the same characteristic values while updating the concerned KF. The aggregates make it possible to gather all these segments within the same recording by aligning the various updated KF. (that's definitelly not clear to me but...this might be the reason why...)
In the last chain that feeds the cube, right after loading datas, there is an "adjust" step, and then a "collapse" step.
The problem :
Sometimes for this cube (when we have a problem with figuresfor example) I have to run loading chains a second time for the same day. The result of that is obviously that datas are doubled in the cube, so that I have to delete requests in the cube to have them right.
The problem is that, when I try to delete a request, the following pop up message appears : "Request ID xxx is aggregated, compressed or scheduled
Message no. RSM725"
I think I have to "uncollapse" the cube to do that, but I don't know how to do. By the way I'd want to "recollapse" the cube after that (it seems it's necessary so...).
Could someone explain steps to solve the problem, and in the same time, explain the necessity and differencies of creating aggregates and collapsing please ????
That would be so usefull to me, obviously I assign points for helpfull answers !
Thanks !
Fabrice

Aggregates
check this links for aggregates
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/3f66ba90-0201-0010-ac8d-b61d8fd9abe9
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/e55aaca6-0301-0010-928e-af44060bda32
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cbd2d390-0201-0010-8eab-a8a9269a23c2
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/2299d290-0201-0010-1a8e-880c6d3d0ade
How to doc
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e55aaca6-0301-0010-928e-af44060bda32
relation between agg and comp
Relation between Rollup and compression.
Aggregate Rollup and Compression

What is difference betwwen aggregates and compression in bi 7.0.

hi All,
will you please tell me difference between compression and aggregates in bi.

Dear Ganesh,
Aggregates allow you to improve the performance of BI queries when data is read from an InfoCube. The data of a BI InfoCube is saved in relational aggregates in an aggregated form. Relational aggregates are useful if you want to improve the performance of one or more specific BI queries, or specifically improve the performance of reporting on characteristic hierarchies
Compression is phenomenon where all the contents of ur info cube moves from F to E table,,This is called compression and data will be aggregated when this compression happens..
Why do we do compression..??
When you load data into the InfoCube, entire requests can be added at the same time. Each of these requests has its own request ID, which is included in the fact table in the package dimension. This makes it possible to pay particular attention to individual requests. One advantage of the request ID concept is that you can subsequently delete complete requests from the InfoCube.
However, the request ID concept can also cause the same data record (where all characteristics are the same except the request ID) to appear more than once in the fact table. This unnecessarily increases the volume of data and affects system performance when you analyze data, since each time you execute a query, the system has to perform aggregation using the request ID.
You can eliminate these disadvantages by compressing data and bringing data from different requests together into one single request (request ID 0).
For more info on aggregates
http://help.sap.com/search/highlightContent.jsp
and info on Compression
http://help.sap.com/search/highlightContent.jsp
Hope this helps u...
Best Regards,
VVenkat..

Diff between valid for consolidation and aggregation property in ODI column

Hi John,
I have a query regarding the columns when we revers the dimensions in ODI. In the columns tab of each dimension, there is valid for consolidation column. What does this column to when we select it. Coz any how i will be using the aggregation for plan type where i will be giving the consolidation operator. Could you please let me know the differences between them
And also there is one more column Operation. What does this do

Hi,
You can ignore the "valid for consolidation column" as far as I am aware it is not used.
Operation is for different types of load, these are
Update (default)–Adds, updates, or moves the member being loaded.
Delete Level 0–Deletes the member being loaded if it has no children.
Delete Idescendants–Deletes the member being loaded and all of its descendants.
Delete Descendants–Deletes the descendants of the member being loaded, but does
not delete the member itself.
Cheers
John
http://john-goodwin.blogspot.com/

Composition and Aggregation

hey guys
I have read the previous posts about composition and aggregation. And here is what i have got.
Composition: life time of objects got to be the same. For example there is a composition between carframe and a car. If the car gets destroyed the carframe woulod also get destroyed.
Aggregation: Life times of the objects are not the same, one oject can live even after the other object has been destroyed.
But i seem to get all these things in theory, but when it comes to coding am not able to translate these theories. To be particular i would want someone to help with me how these relationship can be coded
Thanks
K

Consider the following example :
Car has an engine, chairs, wheel, etc. it is clear
that this is composition, because "Car" is composed
of engine, chairs wheel and so on. but think about
what happens if you want to destroy the car, but
reuse its engine, thing that frequently happen when
you get your car smashed (didn't happen to be thanks
god). Anyway you destroy the car, but it parts stay
alive. so the "composed" objects lifetime can exceed
the "composer" object lifetime.
I think of composition and aggregation in the
following way :
if there is no meaning to the object without its
parts (parts of which it is
composed) then it is composition. if there is any
meaning for the object without its parts (like empty
paragraph (without words) in text, which can be left
empty till the wrighter have something to write in)
well, then it is aggregation.sometimes a car could be smashed and the engine would still be running, junkyard sells tires from wracked cars... all tha, however, has nothing to do with composition or aggration.
composition is a strong form of ownership, a car probablly needs to have an engine, some tirs etc in order to be sold as a car, so the engin, tirs are usually composed as composition. life time of them begins when the car is instantiated and until the instance vanishes. when a car is smashed or totaled, it is merely a state of the car instnace, like a flat tire, the car instnace still exists, so a running engine on a totaled car is ok.
usually if your object has a field referencing an object, that object is a composition, even the creation occurs earlier that the creation of the instance itself, such a case would be a DI: dependency injection. the destruction of an instance is a bit beyond the control of the composing instaance, that however dosnt matter, once the field loses the reference, we can think of it as the end of the life of the composed object. this is a bit different from C++ which allows you to invoke the destructor of the composed object. another difference is that you can have local objects, java objects all live in the heap area, no local objects.

Difference between validation and susbstittution with tcodes

hi all can any body tell me about difference between validation and susbstittution with tcodes
regars
sravya

Hi,
Settting up the FI Validations
You can use additional validation to supplement the existing SAP logic to fit you into your businness needs.
For e.g. to allow postings from company code 0001 to business area AA only.
GGB0 - To maintain the validations
Validation - Enter a validation name e.g. VBUS
Applicaion Area - SAP module e.g. FI
Calling Point - Dependent upon the application area that is selected.
0001 - Document Header - validate enteries at document header, e.g BKPF table
0002 - Line Items - check line item entris within a document, e.g. BSEG table
0003 - Complete Document - check settings for the whole documents.
e.g. Validation step 001
Allowed company code '0001' to post to business area AA only. 'FI00' checks that line item is from FI.
If checks failed, the error message number 14 is displayed to stop the transaction.
Prerequisite
<BSEG> $BUKRS = '0001' AND
<BKPF> $GLVOR = 'FI00'
Check
<BSEG> $GSBER = 'AA'
Message
Type E No. 14 - Business Area not allowed for company 0001
Output fields 1 - BSEG - GSBER 2 - BSEG - BUKRS
3 - 4
OB28 - Define Validations for Posting
CC CallPnt Validation Description Activtn Level
0001 2 VBUS Business Area Validation 1
Activtn Level - 0 - Not Active 1 - Activated 2 - Activated for all except batch input
GGB4 - Manage the activation of all validations in the SAP system.
Validations, Substitutions, and Rules
Purpose
With the validations and substitutions software, you can validate and/or substitute data at the time of entry in the FI-SL System and other SAP Systems.
Implementation Considerations
You do not need to change the standard system to customize your validations and substitutions. For each installation, you can define exactly which validations and substitutions are necessary to ensure the integrity of your data.
Features
Validation
In the SAP System, almost all input values are validated by a program or against tables or master files. Since some types of validations cannot be standardized, you can use FI-SL's validations program to create validations for your system.
With validations, you can check values and combinations of values as they are being entered in the SAP environment. Validation rules are stored in the Rule Manager; as data is entered, the Integration Manager validates the data against the validation rules stored in the Rule Manager. Because data is validated before it is posted, only valid information enters the FI-SL System.
You define validation rules using Boolean logic. When you define a validation rule, the system checks the validation rule to ensure that it is syntactically correct.
You can also define the result of breaking the validation rule. For instance, you can specify that a message is issued but the user can continue processing. You can also force the user to correct the error before processing can continue.
For more information, see Validation or What Are Validations?. For more information on using validations, see Creating a Validation. For more information on Boolean Logic, see Introduction to Boolean Logic.
Substitution
Substitution rules are stored in the Rule Manager. When data is entered in the system, it is substituted by the Integration Manager. The Integration Manager calls the Rule Manager. Substitution occurs before the data is posted to the FI-SL databases.
You define substitution rules using Boolean logic. When you define a substitution rule, the system checks the substitution rule to ensure that it is syntactically correct.
For more information, see Substitution or What Are Substitutions?. For more information on using substitutions, see Creating a Substitution. For more information on Boolean Logic, see Introduction to Boolean Logic.
Rules
A rule is a Boolean expression that you can use as a condition, as a check, or in another rule. Rules enable you to refer to frequently used Boolean statements simply by specifying the rule name.
The FI-SL Integration Manager uses Boolean logic. When you use Boolean logic and syntax, you can:
Validate data
Substitute data
Select ledgers for posting
Transfer substitution data to a rollup ledger
Select report data
The Rule Manager stores the Boolean rules used to analyze data. The Integration Manager calls the Rule Manager and determines whether entered data should be used. If a Boolean statement is true, an action is taken; if a statement is false, no action is taken.
Boolean logic is used in the following FI-SL modules:
Validation
Substitution
Ledger selection
Report Writer
Rollups
To use Boolean Logic in one of the functions listed, you create statements that are used as formulas in the FI-SL System. For more information on using Boolean Logic, see Introduction to Boolean Logic or Boolean Logic Statements and Rules.

Difference between SIP200 and SIP400

Hello.
Is there anyone who can explain what exactly BIG difference between SIP200 and SIP400 ?
They have same four bays, support almost same wan interface cards.
Please help me : )

Hi,
The difference is mainly speed:
The Cisco 7600 series router is an edge aggregation router, and the SIPs provide a cost-effective solution for customers seeking moderate- to high-port density and line rate services:
•The Cisco 7600 SIP-200 provides WAN edge aggregation through lower-speed and low-density SPAs for network environments requiring regional office connectivity to headquarters, or collapsed LAN/WAN deployment.
•The Cisco 7600 SIP-400 provides higher-speed, high-density link aggregation for network environments requiring leased line and metro aggregation.
•The Cisco 7600 SIP-600 provides a high-speed interface for WANs and metro aggregation.
link:
http://www.cisco.com/en/US/products/hw/routers/ps368/module_installation_and_configuration_guides_chapter09186a008044013b.html#wp1063979
HTH

Difference between cumulative and non-cumulative key figures

Hi,
What is the difference between cumulative and non-cumulative key figures and under what conditions they are used. What is snapshort and where it is used.

Hi.............
Basically the key figures are of two types cumulative and non cumulative.
Cumulative are the normal one which you use always and they always bring the new values of the key figures in the delta that is if suppose A has value 10 and after change the new value is 20 then you will use cumulative key figures there, and your delta( new value) will bring 20.
but suppose your key figures field only the change in the prior value that is in this case the delta in the key figure value will bring 10 (20-10- change of 10 )as new value in the key figure A then you will have to model it through the non cumulaitve key figures.
Now
1) Cumulative is for the first case that is if the key figure alwyas brings the new values of the key figure and not the change sin the key fiures value.
2)NCum. value with NCUM value change:
In this case ther is only one field which brings the changes for a particualr key figure and you ahve to define that key figure as non cumulative.
Ex: In case of stock only one filed brings both ingoing value and outgoing value so 10 ,-4,100,-34.....
In this case you will this option and use the key figure here in the space provided.
3) In this case you haev two separate key figures one for the inflow of stocks and one for the outflow of the stocks.
you use one key figure for the inflow and one key figure for the outflow.
The main key figure autiomatically takes care of the logic and gives the correct output upon the summation
net value of stocks( inflow- outflow).
Also do remember in this case the key figure for inflow and out flow are the basic key figures that is cumulative key figures.
A non-cumulative is a non-aggregating key figure on the level of one or more objects that is always displayed in relation to time. Examples of non-cumulatives include headcount, account balance and material inventory. here the aggregation of key figure is based on the another info object
There are two different ways to define non-cumulative key figures:
Non-cumulative key figure with non-cumulative changes:
Before you can define the non-cumulative key figure, an additional cumulative key figure containing the non-cumulative change must exist as an InfoObject.
Non-cumulative key figure with inflows and outflows
There has to be two additional cumulative key figures as InfoObjects for non-cumulative key figures - one for inflows and one for outflows. The cumulative key figures have to have the same technical properties as the non-cumulative key figure, and the aggregation and exception aggregation have to be SUM.
Features of non-cummulative key figures
A non-aggregating key Figure.
Records are not summarized for Reporting
Exception Aggregation is being applied on these key figures on the level of one or more info objects usually with time .
Examples: Head Count, Account balance, Material stock
consider simple senario
Date Net Stock Quantity Sales Revenue
01.02.2005 40 1000
02.02.2005 50 2000
03.02.2005 25 3000
this is the query output if stock quantity has treated as cummulative and non-cummulative key figures
if stock quantity taken as a cummulative key figure
Date NET STOCK QUANTITY SALES REVENUE
01.02.2005 30 1000
02.02.2005 50 2000
03.02.2005 20 3000
RESULT 100 6000
in the above result the key figure has aggregated to the total value that wont give sense to the net stock quantity
if stock quantity taken as non-cummulative key figure
Date Net Stock Quantity (LAST) Sales Revenue
01.02.2005 30 1000
02.02.2005 50 2000
03.02.2005 20 3000
RESULT 20 6000
Hope this helps you..............
Regards,
Debjani................
Edited by: Debjani Mukherjee on Sep 15, 2008 7:22 AM

What is the difference between cumulative and non cumulative keyfigures?

Hi Friends
What is the difference between cumulative and non cumulative keyfigures, when we r using the cumulative and non cumulative
Regards
Ravindra

Hi Ravindra,
Have a look at the help:
http://help.sap.com/saphelp_nw2004s/helpdata/en/8f/da1640dc88e769e10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/80/1a62f8e07211d2acb80000e829fbfe/frameset.htm
Go through these.
Re: Types of non-cumulative keyfigures
http://help.sap.com/saphelp_nw2004s/helpdata/en/8f/da1640dc88e769e10000000a155106/content.htm
See the following threads
non-cumulatives KF in reporting
Re: use of non cumulative keyfigure
Re: When do we use Non-Cumulative values?
Key figures:
1. Cumulative Vaules
2. Non Cumulative Values
Cumulative Values:
Cumulative Values are Keyfigures for which Keyfigure Values are must posted in every time unit that reported on (= time period specific Values).
Example:
Revenue
Non Cumulative Values:
Non Cumulative Values are Keyfigures for which KeyFigures are only evaluated for selected time Periods.
Cumulative Keyfigures With Exception Aggregation:
It's a 'normal' KF (with summation, min or max as aggregation behaviour), but you set some exception in this behaviour...for example, you can say that a KF, normally aggregated by 'summation', have to show the max value (or the average, or '0' or something else), that is the 'exception aggregation' when you use it in combination with 0DOC_DATE (or other char), that is the 'exception aggregation char reference'...in this case OLAP processor give to you the possibility to see your KF with different behaviour depending from you use 0DOC_DATE (in our example, MAX) or something else (SUMMATION).
Non Cumulative keyfigure with Associated Single Delta:
If you have a stock KF that is fed from only one (other) movement KF that can assume positive and negative sign.
KF1 (initial) STOCK (non-***.) = 100
KF2 flow = -30
KF2 flow = 70
KF1 (final) STOCK (non-***.) = 140
Non-cumulative key figure with associated in and outflow:
This is the case of 2LIS_03_BF KF stocks fields.
Here, we have the same situation in point 2, but you will have not only ONE flow KF, but TWO, one dedicated to in and another one dedicated to out !
You have to use this scenario if you have no KF that have positive and negative sign, but two KFs each one representing positive (in) and negative (out) logical sign!
KF1 (initial) STOCK (non-***.) = 100
KF2 (out))flow = 30
KF3 (in)flow = 70
KF1 (final) STOCK (non-***.) = 140
Website Addresses For Non Cumulative KeyFigures:
http://help.sap.com/saphelp_nw04/helpdata/en/80/1a62dee07211d2acb80000e829fbfe/frameset.html
http://help.sap.com/saphelp_nw04/helpdata/en/82/f2dc37f0f12313e10000009b38f8cf/content.html
http://help.sap.com/saphelp_bw31/helpdata/en/82/f2dc37f0f12313e10000009b38f8cf/content.html
http://help.sap.com/saphelp_erp2004/helpdata/en/d2/e0173f5ff48443e10000000a114084/content.html
Re: Non-Cumulative keyfigure example
Re: Types of non-cumulative keyfigures
/community [original link is broken]
http://help.sap.com/saphelp_bw32/helpdata/en/80/1a62dee07211d2acb80000e829fbfe/frameset.html
/community [original link is broken]?forumID=131&threadID=29557&messageID=273049
/community [original link is broken]?forumID=131&threadID=111914&messageID=1248243
Check this very useful docu.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/93ed1695-0501-0010-b7a9-d4cc4ef26d31
****Assign Points If Helpful****
Regards,
Ravikanth

Difference Between Aggregates and Compression

Hi,
Can you tell me what is the difference between Aggregates and Compression?
I know ,once compressed data is not available for deletion in request wise
and it moves from F table to E table .
Aggregates means ,data will move from cube to aggreagates(Baby cubes).
But my query is ,As both of them aggregates the data.which of them should be used. at what situation?
I hope you understood my Query.
Regards.
Naresh.

Hi,
An aggregate is a materialized, aggregated view of the data in an InfoCube. In an aggregate, the dataset of an InfoCube is saved redundantly and persistently in a consolidated form into the database.
Aggregates make it possible to access InfoCube data quickly in Reporting. Aggregates serve, in a similar way to database indexes, to improve performance.
especially in the following cases we create aggregates:
The execution and navigation of query data leads to delays with a group of queries.
You want to speed up the execution and navigation of a specific query.
You often use attributes in queries.
You want to speed up reporting with characteristic hierarchies by aggregating specific hierarchy levels.
For more info on aggregates go though the link below
https://help.sap.com/saphelp_sem320bw/helpdata/en/c5/40813b680c250fe10000000a114084/frameset.htm
Compression creates a new cube that has consolidated and summed duplicate information.
2. When you compress, BW does a group by on dimensions and a sum on measures... this eliminates redundent
information.
3. Compressed infocubes require less storage space and are faster for retrieval of information.
4. Once a cube is compressed, you cannot alter the information in it. This can be a big problem if there
is an error in some of the data that has been compressed.
For more info go though the below link
http://www.sap-img.com/business/infocube-compression.htm
Regards,
Marasa.

Difference vs rollup and aggregation

Similar Messages

Maybe you are looking for