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.

Similar Messages

Aggregation level and planning filter question

Hi,
I have below questions on aggregation levels and planning fitlers.
Scenario: An Aggregation level is built on a multiprovider( Actual Cub1(5 chars, 4 keyfig), Actual Cube2(8 chars, 6 key fig), and Real Time Cube3(8 chars and 3 keyfig)). A FOX copy function has to be built on this aggregation level in which data from cube1 will be copied to cube 3.
1. Does an Aggregation level need to have all chars and keyfigures from cube 1 and cube 3? or it should have structure of Cube 3 only as data will be written to cube 3?
- what are the standard design considerations for defining aggregation level?
2. In planning filter, both cube1 and cube3 are to be restricted or only cube3?
Is it necessary that only target planning cube is to be resricted? In that case how function will get the source data from cube1?
- what are the standard design considerations for defining planning filter?
Please provide some info on this...
any document on design consderations for planning object will be great.
Thanks,
Pundari.

Please go thru the following link u will find step by step procedure for IP:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e0568315-7727-2d10-d4ba-88ab69e16577?quicklink=index&overridelayout=true
Please provide ur valuable points if it is helpful:)
Regards,
Prasad.

Aggregation Level issues

Dear Experts,
I have 2 questions about aggregation level now.
1) I have deleted an Aggregation Level in Planning Modeler But it's not being deleted from the InfoArea of
    BI Modeling section. How do I delete it from InfoArea ?
2) Currently that Aggregation Level is based on 1 InfoProvider.
    How do I add another InfoProvider under that ?
    Or how do I delete the existing one and replace it with a new one ?
Thanks,
Akash

Thanks for your help...
Actually I had this aggregation level used in a query and also I did create Filter, Planning Functions and Planning Sequences on it.
So I had to delete the Query first, then Planning Sequences, then Planning Functions and then Filter and finally the Aggragation Level.
And then when I refresh the InfoArea it was still there until I signed out and logged in back to Admin Workbench.
Hope these help for other people out there.
Thanks all.
Akash

IP question: Aggregation Level picture icon color?

We are pretty new on IP (Integrated Planning). You know that the picture icon of Aggregation Level look like a two step stair. When we check our BI 7.0 system, find for some aggregation levels, both the steps are white color, while for others, the top step is white color and the bottom step is blue color which looks like a small cube shape. What are the difference? The one with bottom step being the blue color means this aggregation level is activated and the one with both steps being white colors means they are inactivated?
Another question, as what we know, in order to do planning, the Cube must be real-time cube other than standard InfoCube in the setting of the cube, right? In our system, we find the aggregation is built on a Multi-Provider and underlying the Multi-Provider, there are about 6 cubes. But when we check all the 6 cubes, find the settings for these cubes are all set to Standard InfoCube. That means with the aggregation level built upon this multi-provider, users can't do any planning, right?
We will give you reward points!

Hi Kevin,
You can build a simple aggregation Level on a real time cube.
Aslo we can build AGgregation levels on Multi providers ( which must contain atleast one real time Cube) . These kind of aggregation levels are called as Complex Aggregation levels.
Also regd the Aggregation level Colours , your understanding is right.
http://help.sap.com/saphelp_nw70/helpdata/en/43/1c3c7031b70701e10000000a422035/frameset.htm
Search for Aggregation level and you would get more details .
Hope this clarifies.
Raja

Aggregation level - design question

Hi, All
we are in BI-IP ( Netweaver 2004s SPS16).
I have a design question for this scenario.
User needs to plan the amounts for a duration (start period and end period), Jan2008 -Dec2008 (001.2008, 012.2008) = 12000.
We need to distribute this to the periods equally. 001.2008 = 1000, 002.2008 =1000 .... 012.2008=1000.
If the user changes the period amounts, it should be reflected back in the duration amount.
Pl suggest the design for the aggregation levels to achieve this.
Thanks in advance.
velu

Hello Velu,
As the name also goes, creating an "aggregation level" will only result in "aggregation". What your requirement is, is called disaggregation or distribution - this cannot happen automatically - you will either have to use the feature in input queries or use the distribution planning function or create your own planning function using fox/exit.

MultiCube over IP Aggregation Level Question

Hi, I have a MultiProvider over an IP Aggregation Level and a Real InfoCube. This was all handed down to me from previous development. The Aggregatation Level has the same level of detail as the planning infocube it is based on.
Is there any reason for the MultiProvider to be over the Aggregation Level instead of the actual planning infocube?
I guess I'm reading that a multiprovider over an aggregation level is for planning only and not reporting? If this is true then do I need a multicube for planning and a separate multicube for reporting using the actual planning infocube?
Thanks for any clarity you can offer...

Wouldn't this modeling work as well for planning? I mean while they are planning values they might want to see actual values as well to help in decision making?
Thanks!

Aggregation level includes filter objects...

Hi,
We are using a BO universe on top of a BEX query to create WebI reports.
We now run into the following problem when filtering on a certain characteristic in the BO query.
The result set of rows is limited to the correct values, but not aggregated up to the requested aggregation level. The problem exists whether the key figure is defined as having an aggregation to be database delegated or sum.
In the query results we see the number of rows being pulled back is too high, the results displayed are correct (because aggregated by WebI). In the example below we selected three stores, but not store as a result object.
*** Query Name:Query 1 ***
** Query Properties:
Universe:Retail Sales and Stock
Last Refresh Date:9/2/10 2:29 PM
Last Execution Duration: 33
Number of rows: 4,947
Retrieve Duplicate Row: ON
** Query Definition:
Result Objects: Style Code, NSLS @ PCS
Filters ( Only RMS Billing Documents Infoprovider
AND Given Legacy Division Set
AND Given Currency Conversion Type
AND Store Key In List { 1001; 1002; 1003 }
AND NSLS @ PCS Not Equal 0
We cannot attach a document, but the actual amount of rows should have been 2,856,
the number of different style in these 3 stores.
When we include the store object in the results, we can see the number of rows stays the same (proof that it did indeed return rows on a store level and not aggregated upt to the style code...
*** Query Name:Query 1 ***
** Query Properties:
Universe:Retail Sales and Stock
Last Refresh Date:9/2/10 2:09 PM
Last Execution Duration: 13
Number of rows: 4,947
Retrieve Duplicate Row: ON
** Query Definition:
Result Objects: Style Code, Store Key, NSLS @ PCS
Filters ( Only RMS Billing Documents Infoprovider
AND Given Legacy Division Set
AND Given Currency Conversion Type
AND Store Key In List { 1001; 1002; 1003 }
AND NSLS @ PCS Not Equal 0
Is this behaviour fixed in any fix pack? Or did noone address this problem?
The problem becomes a real problem when the user wants to select everything u/i a certain date.
The number of rows are then pulled back on a style/store/day combination and easily reached 100.000 rows.
Thanks for any insight you can give on this,
Marianne

Hi Rik,
Thanks for at least trying
I didn't try this before, so I just did, despite the fact that the aggregation level only has something to do with the way data aggregates within webi. (I'm that desperate)
No difference, other then the fact that I now get #MULTIVALUE in the cells with multiple underlying rows.
Anyone else?
Marianne

Problems creating aggregation levels over a Multiprovider

Hi experts,
When I create a aggregation level over a multiprovider the system returns an error " Infoprovider XX cannot be used for definition". I have read other threads with the same question and its solutions. I have checked my system and all is correct. The multiprovider has linked five infoproviders, one as real time.
Any Idea?
Please, it is very urgent to solve this.
Thanks a lot in advance.

Hi Mayank and Ravi,
I have checked the identification of chars and kf. The realtime cube has five chars and a kf. All of them are assigned with all cubes witch are linked with the multiprovider.
I have tried by removing the realtime cube and the system shows the same error message. I have also tried by reactivating the cubes and multicube.
Any idea?
Thanks.

Aggregation Level & Selection ID in Demand Planing Background job

Folks
Whle creating a Demand Planning job in the background, we need to make few selection such as
            1. Choosing a Selection ID(One, Several & Select All) and
            2. Choosing an Aggregation level.
My question is : Doesn't the selection ID already have the aggregation level defined with in as selection ID is basically something defined or shown as Product by Location and then by Sales Org etc. Isn't this the same as the aggregation level ???
Why do we need to have Selection Id as well as Aggregation level in Background job ?
In the interactive planning do we need the aggregation Level ? If so where do we specify the same ?
TIA

The aggregation level can make a big difference to the forecast results. If you run the forecast on a high level (for example, at division level), the system aggregates the historical data (for example, the historical data of all products in a division) before it carries out the forecast. However, if you run the forecast on a low level (for example, for just one product), the system creates the forecast based on the historical data at this level, and then aggregates the forecast results in the planning screen at runtime.
The default level is the most detailed level.Here values will be disaggregated to the lowest detailed level and forecast will be executed in that level for each CVC.
say
PRD LOC     PRD_GRP
A       A1           PG1
B       A1           PG1
C       A1           PG1
A       B1           PG1
B       B1           PG1
C       B1           PG1
here forecast wil be carried out for 6 CVCs
However, in real time, as you have many CVCs, we dont follow this.
Say we specify the aggregation level as PRD_GRP and LOC.. Then system aggregates values at product group and location level..executes forecast and then disaggregates.
in this case forecst will be carried out for
PRD LOC     PRD_GRP
      A1           PG1
      B1           PG1.
Selection ID on the other hand will be used for specific selections.
Suppose if u want to execute one profile for PRDGRP PG1 at LOC A1 , you create a selection ID with this selection like in interactive planning..
How ever, if your selection is
PRD         *
PRDGRP *
LOC          *,
then , here ur aggregation level helps how to disaggregate values before running the forecast

Cross-Aggregation-Level Selection Evaluation indicator

Hi,
Can any one explain me the meaning of the below statements in the two paragraphs. This is for "Cross-Aggregation-Level Selection Evaluation indicator" in alert monitor.
If the Cross-Aggregation-Level Selection Evaluation indicator has not been set in the SDP alert profile, only planning objects that exactly correspond to the aggregation level defined in the selection are taken into account. This means that the planning objects contain exactly the characteristics of the aggregation level. Planning objects that have additional characteristics are not taken into account.
If however, the Cross-Aggregation-Level Selection Evaluation indicator is not set in the SDP alert profile, the system takes into account not only planning objects that exactly correspond to the aggregation level of the selection but also those containing additional characteristics.
Example
If you use a selection with the aggregation level 'Product' in the SDP alert profile and set the Cross-Aggregation-Level Selection Evaluation indicator, alerts will be issued not only for this product but for the relevant location products.
Thank you.

Hi Datta,
Let me go further with my data model first.
Selection criteria:
Sales organisation = CZ01
Sales statut = active
Standard / promo = standard
Product size = A, B, C, D, E
Aggregation level:
Sales organisation
Distribution chanel
Division
Product size
What I understand of the 546079 OSS notes:
Distribution chanel and division are to be out of the aggregation level. Moreover in my case, there is only one value possible.
What I understand of the 374681 OSS notes:
The system searches for all the characteristics of the sales organisation * product size (of the aggregation level) that match the selection. At that step, APO should select only active and standard skus for CZ01 sales organisation and A, B, C, D, E product size. Afterwards the system searches for all the characteristics combinations that fit the chosen aggregation level and aggregates its values.
My question is: does APO disaggregate on the ID selection?
The characteristic combination I see in the job log are those defined on the aggregated level taking into account the sales organisation and product size restriction defined in the selection ID.
Thank you for your return.

Forecast, selection and aggregation level

Hi gourous,
I'm working on APO 4.1.
Forecast runs in background as following:
- Aggregation level: Sales organization / distribution channel / division / product size.
All these four characteristics are part of the characteristic combination.
- Selection ID is defined on: sales organisation / sales statut / standard - promo indicator / product size
Sales statut and standard - promo indicator are attributes of the characteristic material (sales view).
However there is forecasts on promo SKUs even if they aren't in the selection ID (standard - promo indicator as value egal to standard in the selection ID)
My question is: how is it possible? is there a conflict between the selection ID and the aggregation level?
I check the assignment of forecast profiles and there is no profil assigned on the ID selection.
Thank you for your return.
Sophie

Hi Datta,
Let me go further with my data model first.
Selection criteria:
Sales organisation = CZ01
Sales statut = active
Standard / promo = standard
Product size = A, B, C, D, E
Aggregation level:
Sales organisation
Distribution chanel
Division
Product size
What I understand of the 546079 OSS notes:
Distribution chanel and division are to be out of the aggregation level. Moreover in my case, there is only one value possible.
What I understand of the 374681 OSS notes:
The system searches for all the characteristics of the sales organisation * product size (of the aggregation level) that match the selection. At that step, APO should select only active and standard skus for CZ01 sales organisation and A, B, C, D, E product size. Afterwards the system searches for all the characteristics combinations that fit the chosen aggregation level and aggregates its values.
My question is: does APO disaggregate on the ID selection?
The characteristic combination I see in the job log are those defined on the aggregated level taking into account the sales organisation and product size restriction defined in the selection ID.
Thank you for your return.

Running Macros on 9AMALORE aggregation level

Hi,
I'm trying to run simple macro in SNP (5.0)
I use DP Activities and Background jobs for this.
When I create a Background job, with selection "Select All" from Aggregation level I can choose what I want - "9AMALORE".
When I create a selection in the shuffler ( I have to restrict the selection to one plant only) and use it as Background job selection, I cannot manage to run the macro on 9AMALORE level.
In this case only one selection is available based on the shuffler selection grouping criteria, and unfortunately I can do it only by 9ARE (Resource only) or 9AMALO (Material Location).
Do you know what trick I can use to achieve this?
Regards!

Hi,
I am trying to understand your requirement. Not sure if I have understood this correctly,
When I create a Background job, with selection "Select All" from Aggregation level I can choose what I want - "9AMALORE".
Question - You mean in the /sapapo/mc8d txn you are able to select 9AMALORE as your agg level? What is ur selection id in this case?
When I create a selection in the shuffler ( I have to restrict the selection to one plant only) and use it as Background job selection, I cannot manage to run the macro on 9AMALORE level.
In this case only one selection is available based on the shuffler selection grouping criteria, and unfortunately I can do it only by 9ARE (Resource only) or 9AMALO (Material Location).
Question - Again in the interactive planning, you use shuffler to create a selection id. So here, What is your "Selection characteristics" and what is your "Show Characteristics" (the one at the top). Are you using this selection id in the background job and not able to aggregate by 9AMALORE or are you trying to running the macro in interactive.
Either ways, we shud be able to achieve what you are looking for.
Sorry I am a little confused with your requirement, but I am confident that I can help you, if you can clarify what you are looking for.
Thanks
Mani

Access on aggregated levels with virtual key figures

Hi all,
I need access to the aggregated view of a BEx report within user-exit RSR00002 for processing virtual key figures. Currently I only get access to the lowest non-aggregated level.
My requirements in detail:
I get certain key-figures (250 historical values)on the lowest aggregation level - so-called folders. Then I have to aggregate this vector of values at the next hierarchy level up to the top-level, say along-side a company's business department structure. Drill-down, slice&dice should be possible. So far so good - this is done easily with standard BEx features.
Then, on each aggregation level, i.e. hierarchy node, I need to get the third lowest of the 250 aggregated values to assign this to my vkf. This is not an issue of the algorithm but of the internal data representation or access to the OLAP processor because I don't get this vector on the same aggregated level such as I could see it in my BEx report but on the lowest non-aggregated folder level.
The question is now:
a. Is data access on aggregated levels and drill-downs because of the internal representation generally not possible within this user-exit and would I have to supply the aggragation logic myself or
b. do I have overlooked something critical - did I miss the trick?
Every idea or hint is deeply welcome!!
Thanks a lot,
Michael
Message was edited by: Michael Kronenberger

First check in Technical Information in RSRT , whether the
Virtual Char/Key Fig is Y or N.

Setting aggregation level in POSDM

Hi experts
I would like to consult from you regarding SAP standard function on aggregation level to be set in POSDM.
The requirement I get is to aggregate sales in the level of day/store/article/promotion ID.
Are there any solution to this in terms of configuration?
Really appreciate your help.
BR
Dominic

Hi,
Aggregation Method plays a key role in terms of One-Step Processing Tasks.For eg.,if you want to Generate WPUTAB Idoc and there is an aggregation Method code which is specifically available to have the aggregation done based on the means of payment.
SImilarly you can have aggregation method based on material,by sales item and qualifier and also with material&Conditions combination.
You can see the difference when you choose 0000 - Code for Aggregation method for Task code 0013 - Generate Idoc WPUTAB and process.Later on change the Code for Aggregation Method to 0005 and you can see if in POS Workbench also.
NOTE : You can also custom specific Aggregation Method - for eg, Aggregation should be done based on transaction type/sales item type etc.
Thanks and Regards,
Ramesh D

Aggregation level on single level basis or multiprovider

Hello,
we use IP 7.0 and have a planning cube for CO-PA data, as well as a multiprovider combining the actual cube and the planning cube for COPA data. We need to implement a planning tool in which planning simple planning functions are needed on the single basis (copy, revaluation, multiply,manual planning ...) as well as on the multi-provider (top-down with reference data).
-> on which level(s) should we define the aggregation level? Do we need to define it on the multiprovider (in order to do the top-down) or can we split it up (single level and multi-provider) and define a workbook with a manual planning function on the single level AND including the top-down based on the multiprovider?
thanks
Dries

I agree with Gregor,
I think it is more logical to configure your Aggregation Level on top of your Multi-Provider, especially since you already have a need to view ref data from Actuals to perform calculations on your Planned. You can always restrict your 'simple' functions to the appropriate InfoProvider.
As for the FOx question, you can always restrict to each InfoProvider when writing your FOx (either inside the FOx code or using the FOx conditions).
Regards,
Zane

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

Similar Messages

Maybe you are looking for