Aggregates Definition

Hi All,
I have a query which is running slow so i am going to create a aggregate for that query. My query has the following definition.
Display Chars
Company code
Asset
Capitalization date
Filter
Company code -- has variable
Depreciation area -- restricted with '1'
But the Key figure contain the restriction with the Transaction type
Now my question is
What are the Chars do I need to include in Aggregates? If I dint include the Transaction type will my query use the aggregate?
Thanks
Kiran

Hello Kiran,
You can let the system create an aggregate for you, depending on the query. You need to go into the aggregate maintainence screen. In the toolbar goto Propose-> Propose from query ->Choose your query ->Transfer selections. The system will generate an aggregate for you based on this query.
You can refer the below link for more info.
[http://help.sap.com/saphelp_nw70/helpdata/EN/10/244538780fc80de10000009b38f842/frameset.htm]
Regards.

Similar Messages

Question on aggregation level "%" (percent) in aggregate definition

Hello,
I would like to find out all the aggregates that have at least one navigation attribute of a specific characteristic (let's say 0CUSTOMER) in their definition. The idea behind that is to find out which aggregates are potentially affected in a change run by a master data change for the 0CUSTOMER characteristic.
Well, I looked in table RSDDAGGRCOMP for entries that met the selection criteria {OBJVERS = 'A'; IOBJNM = '0CUSTOMER_*'}
For all navigation attributes of 0CUSTOMER - except for those that can actually be seen in the aggregate definition screen (launched via "Maintain Aggregates") - there are records that have as aggregation level (field AGGRST) '%'. What does this aggregation level mean and why is it in that table? That field description ("SAP-internal use only (technical:facts)") doesn't really bring me forward.
An aggregate, that only contains '%' as aggregation level in RSDDAGGRCOMP for navigation attributes of char 0CUSTOMER is not affected by a change run regarding the master data change of 0CUSTOMER attributes, is that right?
Thanks to any replies in advance.
Regards,
Philipp

aggregation against cubes require the following approach-
http://epmandbitech.blogspot.com/2010/12/obiee-11g-and-multidimensional-data.html
http://epmandbitech.blogspot.com/2010/12/obiee-11g-integration-with-microsoft.html
Thanks.

Cannot change variable for key date in aggregate

Hello,
when I drag time-dependant attributes into an aggregates definition I am prompted to enter a key date or choose a variable for that. I then activate and fill that aggregate. Afterwards I deactivate it and remove the time-dependant attributes so there are no time-dependant attributes in the definition any longer. I then want to also remove the variable for the key date but I can't do so. This property is greyed out and there is no context menu for the entry "Variable for key date".
The SAP Help says this should be possible by changing the key date variable through the context menu (see http://help.sap.com/saphelp_nw04/helpdata/en/7d/eb683cc5e8ca68e10000000a114084/frameset.htm).
Has anyone faced this problem, too? I do not want to redefine my aggregate as this is not an elegant solution to the problem.
Thanks to any answers in advance.
Regards,
Philipp

Hey Karim,
Because you have time dependent attributes in the aggregate you need to specify key date:
check this
http://help.sap.com/saphelp_nw70/helpdata/en/44/70f4bb1ffb591ae10000000a1553f7/frameset.htm

Can we add an info object and its nav. attr in an aggregate together?

Hello
I am getting an error when I try to add 0MATERIAL and 0MATERIAL_OPROD_HIER in an aggregate at the same time. In the cube, both 0MATERIAL and its attr 0MATERIAL_0PROD_HIER sit in the same dimension. Therefore, when I try to create an aggregate and drag these chars in, they try to come into the same dimension here also.
1st scenario:
1. I add 0MATERIAL in the aggregate.
2. I try to add 0MATERIAL_0PROD_HIER in the aggreate, I get an error message ' Aggregation levels cannot be defined for 0MATERIAL_0PROD_HIER.
3. And it does not let me add this nav attr at all.
2nd scenario:
1. I first add 0MATERIAL_0PROD_HIER in the aggregate.
2. I try to add 0MATERIAL now.. I get the same error as above for 0MATERIAL this time.
3. But it lets me add 0MATERIAL inside.
4. Now, when I go its context menu (right click) and select aggregation as 'All Char Values' for 0MATERIAL, then the error goes away.
5. But after I activate and fill the aggregate, I have a look it again.. and now I only see 0MATERIAL and its nav attr which I added first has disappeared.
Why do the above 2 happen? And if I have an info object and its nav attr in ROWS in a query, and if I am not able to add both of them to the aggregate.. how can I improve the performance of the query?
Please advise.

Hi Srinivas
In your scenario, it is sufficient if you just add 0Material when you are creating the aggregate. Need not add the nvaigational attribute in the aggregate definition. The procedure you followed the first time is right i.e. Drag and drop 0material first.
The system does not allow you to add the nav attribute because it is not required. I say this because a navigational attribute added to your infoprovider is like (in terms of SQL) joining your infoprovider with your material master table. Navigational attribute's value is not physically stored in your cube. It is brought in during execution time in both list cube as well as in your query output.
Similarly when you execute your query with 0material as your aggregate, even if you add a filter or variable restriction on 0Material_prodHier your query WILL use the aggregate since 0material is referenced.
You can even check this in RSRT. Give your query name, and generate report first. Then click on Execute + Debug, Choose Display SQL/BIA Query and enter your selection and choose enter. You will see the SQL of your query and in the SQL select statement you will see that your aggregate table is chosen instead of your infocube. This aggregate table only will be read during your query execution in Bex as well.
I hope this helps.
Thanks.

Creating aggregates using abap instead of relying on the interface

Does anyone know how to create aggregates in BW by using abap instead of the habitual dragging and dropping?

Hi dear,
I know there is a report to copy an existing aggregate to a cube to another one (look at OSS note 608814 "Program for copying aggregate definitions")...
Maybe this can be useful...
Bye,
Roberto

Fixing at aggregate level & unfixing at detailed level.

Hi,
Our requirement is as given below......
Our Demand Planning Process is Top-down process. Head Quarter will enter the demand at Territory, Channel and Product Group Level. These values are fixed and gets disaggregated to further planning level based on historical sales. The further planning levels are Sales Officer, Location & Product. Territory Manager can change the demand with in his targets across Sales officers (i.e. he should be able to change the targets of Sales officers without exceeding or reducing the Territory targets).
Can anyone suggest how to fix the keyfigures at Aggregate Level without fixing it at detailed level. We tried FIX_CALC macro, but could not resolve the issue.
Thanks in advance.
SP

You need to create AGGREGATES in your PLANNING OBJECT STRUCTURE, right click on POS and create the following aggregates
(1) ALL TERRITORY characteristics
Now you will be able to fix at the top level and still be able to change at the detailed level.
Read the following:* Let me know if you have any questions*
Aggregate
Definition
The aggregates in APO are not the same as those in the Business Information Warehouse (BW), but they have the same purpose: to speed up data access and therefore increase performance. SAP recommends that you use aggregates in Demand Planning.
These aggregates are sometimes referred to as persistent aggregates, in particular when talking about detail and aggregate levels in interactive planning.
Use
An APO aggregate contains a subset of the characteristics in the master planning object structure. The creation and use of aggregates is optional. The data is always saved on the lowest level of detail. If aggregates exist, the system saves the planning data on the defined aggregate levels as well as on the lowest level of detail. The data is saved twice, but consistently; that is, the sum of the details equals the aggregate value.
SAP recommends that the aggregates you build in APO for planning data also exist in BW for actual data.
If you want to save fixed values at aggregate level ; that is not at detail level of the master planning object structure, in a planning book, you must create aggregates for this level. Otherwise the data is only saved at detail level.
You cannot form aggregates for navigational attributes
See also:
Fixing Key Figure Values
Aggregates are discussed in detail in OSS note 503363. SAP recommends that you read this note thoroughly before configuring your master planning object structures and aggregate hierarchy.

Aggregate on 0CALMONTH

We want to create an aggregate that includes 0CALMONTH. But when I pull OCALMONTH into my aggregate definition it also brings in 0CALDAY, which defeats the goal on our aggregate.
Is it possible to create an aggregate to include the month without pulling the day into the aggregate?
Thanks,
Chris

I'm refering to points. I don't think it recognizes me anymore as the original poster of the message that's why I can't get to the award point buttons.
(If you click on my name by the original post it will list my recent posts as the two from yesterday, but not any today. If you click on my name next to today's post it will list todays post as my recent ones but not yesterdays. So that's why I'm guessing that it does not recognize me as the original. I was able to gives point yesterday. It probably has something to do with me getting my account set up and changing my initial password yesterday. Thanks for helping understand the exception aggregate on the key field!)

Error in Aggregate activation

Hi Experts
I am trying to create Aggregates on a Info Cube.
Go to t.code: RSDDV
select the IFC
In the Aggregation screen, select the characteristic that will be based on your aggregate (drag and drop)
When i try to Activate the Aggregates it showing me error
No aggregates selected for activation
Please help

.      You are in the Modeling function area of the Administrator Workbench.In the navigation window, choose InfoProvider.
       2.      In the InfoProvider tree, navigate to the InfoCube whose queries you want to optimize.
       3.      In the context menu for the InfoCube, choose Maintain Aggregate.This will bring you to the Maintain Aggregates screen.
If an aggregate was already created for the selected InfoCube, you can also go to the maintenance screen by double-clicking on .
If you create the first aggregate for an InfoCube, you will first go to the Proposals for Aggregates dialog box. You can define whether the system should propose aggregates or whether you want to create them manually.
       4.      The left side of the screen shows the dimensions, characteristics and navigation attributes of the selected InfoCube in a tree structure as Selection Options for Aggregates.
Select one or more objects to be copied to the aggregate.
Define the granularity you need for the data in the aggregate. Add all the characteristics derived from these characteristics.
For example if you define an aggregate for the month, you should also include the quarter and year in the aggregate.
This enhancement does not increase the data set, but permits
·         a year aggregate to be built from this aggregate,
·         those who need the annual values can also use queries of this aggregate.
You can only include a characteristic and one of its attributes in an aggregate in expert mode (Extras ® Switch expert mode on/off). Such an aggregate has the same granularity and size as an aggregate that was only built with the characteristic, but is affected by the hierarchy/attribute change run. Compared with the aggregate for the characteristic in which the attribute information is defined by a join with the master data table, the aggregate for the characteristic and the attribute only saves the database join.
We therefore recommend that you either build an aggregate using with the characteristic or you build a much smaller aggregate using the attribute.
       5.      You have different options for creating an aggregate:
·         Transfer the selected object(s) to the Aggregates column on the right side of the screen using Drag&Drop.
·         Select Create New Aggregate.
The Enter Description for Aggregate dialog box appears.
       6.      Enter:
Short Description
Long Description
To change the text at a later time, select Change Description Text from the context menu of the aggregate.
       7.      Choose Continue. You get to the Maintain Aggregates screen.
The system displays the aggregate at the upper right of the screen. The log is displayed in the lower part of the screen.
For more information see Displaying an Aggregate and its Components.
       8.      If an aggregate contains a time-dependent component, you must assign a key date to the aggregate.
When you fill the aggregate, the key date behaves like the key date of a query: The time-dependent attributes and hierarchies are evaluated on this key date. For this reason aggregates with a time-dependent component can only be used in a query if the key date of the query is the same as the key date of the aggregate.
In the Select Variable or Fixed Date dialog box select the following as key date:
·         a variable that is also used in queries for the key date and can be automatically calculated in the SAP Exit or Customer Exit processing types (see Using Variables),
0CWD Current workday
0DAT Current calendar day
0P_KEYDT Key date of due date
0P_KEYD2 Key date of posting (from key date of due date)
0P_KEYD3 Key date of clearing (from key date of due date)
0P_KEYD4 Key date of posting (posting date)
0P_KEYD5 Key date of clearing (from key date of posting)
Aggregates with a variable key date must be updated regularly. This process must be included in a Process Chain (Further BW processes -> Adjust Time-Dependent Aggregates).
·         A certain calendar day
To enter a calendar day, select object CALENDAR in the Select Variable or Fixed Date dialog box (). Choose Transfer selection. This takes you to the Calendar dialog box. You can copy this date to the aggregate definition by double-clicking.
The system displays the technical name of the variable you chose or of the fixed calendar date in the aggregate tree under Properties for node Variables for Key Date.
Once the aggregate has been activated and filled, the system copies the key date computed from the variable when the aggregate should be filled into the line Key Date.
       9.      You can change the structure of the aggregate by adding further components or deleting existing ones. You can also change the key date.
Inserting components into the aggregate
i.         Select one or more objects in Selection Options for Aggregates.
ii.       Transfer them to the aggregate to be changed at the right of the screen with Drag&Drop.
iii.      As needed, change the Aggregation Level with the associated entry in the context menu:
All Characteristic Values
Hierarchy Level
Fixed Value
Aggregates containing fewer than 14 components are stored on the database in optimized form (see Efficiently Loading Data into Aggregates).
Note that the characteristics that are defined in the InfoCube are also included in the aggregate and thus increase the number of components even though they are not visible on the surface.
Deleting components from the aggregate
i.         In the aggregate tree navigate to the characteristic(s) or navigation attributes you want to delete.
ii.       Select these components.
iii.      To delete the components from the aggregate you can:
-         Choose Remove Components in the context menu.
-         Copy the components to the left part of the screen with Drag&Drop.
To delete a dimension from an aggregate, you have to delete all the characteristics and navigation attributes of this dimension.
Changing the key date
i.         In the aggregate tree under Properties, select node Variable for Key Date and choose Change from the context menu. You get to dialog box Select Variable or Fixed Date.
ii.       Select and transfer the required variable or calendar date.
The key date computed from a changed variable is only copied to line Key Date when the Adjust Time-Dependent Aggregates process has been executed.
   10.      To check the aggregate definition for inconsistencies choose Check Definition.
   11.      Save the new or changed aggregate.
Edited by: Rama on Sep 24, 2008 12:03 PM

Creating a view on KONA & KONH - Failed with 'Field name DATAB not unique'

Hi all,
    I am creating a view on KONA (Rebate Agreement) & KONH (Conditions Header) tables. The link is KONA-KNUMA = KONH-KNUMA_AG.
   The field 'DATAB' exists in both tables and I have included those two fields under 'View Fields' . When I tried to activate the View, it fails with 'Field name DATAB not unique'.
   The following is the complete error message:
Message no. MC060
Diagnosis
When you define aggregates (views, lock objects or matchcode objects), you can assign the aggregate fields your own names (the system assigns names to the basic fields automatically). These names must be unique.
System response
The system has established that the names assigned to the aggregate fields in an aggregate definition are not unique and issues an error message.
Procedure
Assign unique names to the aggregate fields in question.
   Why I am not able to create the view after including a field that EXISTS in two tables, PLEASE ?
Thanks,
Venkat.

Hi,
you can include both fields (but what for??); most likely KNUMH will also complain after fixing DATAB (just a guess...).
You can include both fields if you name them differently (different aliases):
In the view fields tab, enter two different names in the column "view field".
this will work.
hope this helps...
Olivier.
Message was edited by:
        Olivier Cora

Can I create my own .cbx file or modify a current .cbx file?

What I would like to do is create an object that will give me a DOUBLE Action Verification message (Are you sure? YES! Are you REALLY SURE? YES!) I'm doing this already with a cloggy of pop-up messages, and wanted a CLEANER and Easier way to do this. My thought was to modify the current PUSHBUTTON -- logctrl.cbx file. Or create a similar one. Any thoughts???

If this is the case, have you thought of using the Aggregate object? You can "create" your own Object out of the existing pop-up windows and push-buttons once and for all and keep using this as an "Object" in future.
Here's a snippet from the Online Help on the Aggregate Object:
The Aggregate object is a way for you to create a collection of Lookout objects, already connected and configured, and use that collection multiple times as an element in your processes.
Create an aggregate by creating a Lookout process and saving the process as an aggregate definition file, choosing which of the object parameters and data members to expose when aggregate is used in another process. Then use that aggregate definition process in other processe
s by creating an aggregate object that uses your aggregate definition as its source. ...

Regarding line-item-dimention

hi,
plz clarify my doubt regarding line-item-dimention.
When line-item Dimensions are used without containing the line-item characteristic in the aggregate, which aggregate should be built?
thanks,
Neelima.

Hi Nl .G
Aggregates can be built out of other aggregates to reduce the amount of data to be read and, hence, to improve the roll-up performance Aggregate hierarchy is determined automatically.
In order to use an aggregate in the first place, it must be defined activated and filled. When you activate it, the required tables are created in the database from the aggregate definition. Technically speaking, an aggregate is actually a separate BasicCube with its own fact table and dimension tables. Dimension tables that agree with the InfoCube are used together. Upon creation, every aggregate is given a six-digit number that starts with the figure1.
am sure using basic aggreate will solve this issue..Try and let me know..
any furthur info you can read from the given link..
[Aggregates|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cbd2d390-0201-0010-8eab-a8a9269a23c2]
Edited by: Prasanna Kumar Perla on Aug 4, 2008 1:52 PM

QAGGRUSED column in RSDDSTAT

Hi folks,
I have created a aggregate for a query and after every time the workbook associated with the query is executed, I see the "used" column in the aggregate definition increasing by 1. So which means the aggregate is being used by the query.
But if I look into the statistics row in RSDDSTAT for that query, the QAGGRUSED column is blank. Why is this column not populated? Do I have to turn on the statistics for the aggregate like how we turn on the statistics for the infocubes?
Also, if the query is based on multiprovider and there are 5 base infocubes and each base cube has a aggregate defined and if the system uses all the 5 aggregates for five separate cubes, will the RSDDSTAT row show all the five aggregate names?
Thanks.
Abdul

Hi Alain
Thanks.
All you got to do is the same as before, bind the column right in the begining before you add to the matrix
'declaring of datasource must only happen once and before
'adding to matrix
oForm.DataSources.UserDataSources.Add("#D", SAPbouiCOM.BoDataType.dt_SHORT_TEXT, 20)
oColumn = oColumns.Item("#")
oColumn.DataBind.SetBound(True, "", "#D")
then to add a row and assign a number use the following
Dim oMatrix As SAPbouiCOM.Matrix
Dim oColumn As SAPbouiCOM.Column
Dim oColumns As SAPbouiCOM.Columns
Dim oEdit As SAPbouiCOM.EditText
'declaring of matrix and column must only happen once
oMatrix = SBO_Application.Forms.Item("FormID").Items.Item("MatrixID").Specific
oColumns = oMatrix.Columns
'repetitive part
oMatrix.AddRow()
oEdit = oColumns.Item("#").Cells.Item(i).Specific
oEdit.Value = i
Hope this helps

"Field name BUKRS not unique" ???

Hi,
I am trying to create a view based on two tables. One is T001 and other is custom table. When i tried to activate, it gives error message like "Field names BUKRS not unique".
Can anyone please tell me about this ?
Thanks,
Regards,
aarthi
[email protected]

The description of the message given by the system is like below
Field name BUKRS not unique
Message no. MC 060
Diagnosis
When you define aggregates (views, lock objects or matchcode objects), you can assign the aggregate fields your own names (the system assigns names to the basic fields automatically). These names must be unique.
System Response
The system has established that the names assigned to the aggregate fields in an aggregate definition are not unique and issues an error message.
Procedure
Assign unique names to the aggregate fields in question.
Regards,
aarthi
[email protected]

Count Distinct Wtih CASE Statement - Does not follow aggregation path

All,
I have a fact table, a day aggregate and a month aggregate. I have a time hierarchy and the month aggregate is set to the month level, the day aggregate is set to the day level within the time hierarchy.
When using any measures and a field from my time dimension .. the appropriate aggregate is chosen, ie month & activity count .. month aggregate is used. Day & activity count .. day aggregate is used.
However - when I use the count distinct aggregate rule .. the request always uses the lowest common denominator. The way I have found to get this to work is to use a logical table source override in the aggregation tab. Once I do this .. it does use the aggregates correctly.
A few questions
1. Is this the correct way to use aggregate navigation for the count distinct aggregation rule (using the source override option)? If yes, why is this necessary for count distinct .. what is special about it?
2. The main problem I have now is that I need to create a simple count measure that has a CASE statement in it. The only way I see to do this is to select the Based on Dimensions checkbox which then allows me to add a CASE statement into my count distinct clause. But now the aggregation issue comes back into play and I can't do the logical table source override when the based on dimensions checkbox is checked .. so I am now stuck .. any help is appreciated.
K

Ok - I found a workaround (and maybe the preferred solution for my particular issue), which is - Using a CASE Statement with a COUNT DISTINCT aggregation and still havine AGGREGATE AWARENESS
To get all three of the requirements above to work I had to do the following:
- Create the COUNT DISTINCT as normal (counting on a USERID physically mapped column in my case)
- Now I need to map my fact and aggregates to this column. This is where I got the case statement to work. Instead of trying to put the case statement inside of the Aggregate definition by using the checkbox 'Base on Dimension' (which didnt allow for aggregate awareness for some reason) .. I instead specified the case statement in the Column Mapping section of the Fact and Aggregate tables.
- Once all the LTS's (facts and aggregates) are mapped .. you still have to define the Logical Table Source overrides in the aggregate tab of the count distinct definition. Add in all the fact and aggregates.
Now the measure will use my month aggregate when i specify month, the day aggregate when i specify day, etc..
If you are just trying to use a Count Distinct (no CASE satement needed) with Aggregate Awareness, you just need to use the Logical Table Source override on the aggregate tab.
There is still a funky issue when using the COUNT aggregate type. As long as you dont map multiple logical table sources to the COUNT column it works fine and as expected. But, if you try to add in multiple sources and aggregate awareness it randomly starts SUMMING everything .. very weird. The blog in this thread says to check the 'Based on Dimension' checkbox to fix the problem but that did not work for me. Still not sure what to do on this one .. but its not currently causing me a problem so I will ignore for now ;)
Thanks for all the help
K

Non Unique Indexes on Dimension Table

Hello ,
I have Material Dimension that has Product MainGroup, Brand , SPC code broken from Product Hierarchy.
As per Business Requirement , we don't want to use the Product Hierarchy , that should need to split into 3 pieces.
Since The Cube Dimensions already reached the 13 , we can not increase the dimensions to keep these 3 fields into separate dimensions.
I heard from Basis guy as <b>we can have index on three fields in same dimension table</b> & read some negative impact on aggregate definition.
Is it true , which one is true , am not sure.
Which one impact causes more worst & usefull..?
Could please some experts throw some light on this.
Cheers
Martin

Martin -
Not sure what you mean by "read some negative impact on aggregate definition".
But as far as adding additional indices on other columns of a dimension table, that certainly is doable. I have never done this as part of an actual intentiional design, but it seems like a valid apporach if you are limited by dimensions. I'm assuming when you say you already have 13, that the 13 does not include the three standard dimensions for time, request, (drawing a blank, is it currency), so that you really have 16 dimensions, 13 of which are user defined.
We have added dimension tabl e indices in our shop when we have found large dimension tables that, either from poor initial design, or changes to the data and/or queries, have resulted in full tables scans against large dimension tables. In some cases, the query costs of the full scan of the dimension table was more than the cost for the access of the fact table itself.
These indices must be added by your DBA as they can not be added thru the Admin Wkbench. You should also probably keep a record of any of these indices you create because if for some reason you delete the tables and reactivate the cube, you'll probably lose them.
Pizzaman

Aggregates Definition

Similar Messages

Maybe you are looking for