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

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 - 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.

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.

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!

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 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

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

Aggregation level is locked by the Change and Transport Organizer

Dear All,
I have created aggregation level in the planning cube and transported to Production from dev, Once i transported to production i am not able to change the aggregation level in Dev, and also aggregation level is Inactive. Aggregation level YPNC2 is locked by the Change and Transport Organizer. Please suggest how to activate the aggregation level in Dev.
Thanks
Christopher

Hi,
Kindly check the following,
1. Is your aggregation level transported properly to the production system ?
2. Was your aggregation level active while you were including it in the transport request ?
3. Did you properly include the aggregation level in the request?
If you find that the answers of all the above questions is "YES", then there should not be any problem in your aggregation level.
Hope this solves your issue, if not kindly get back to me.
Regards,
Balajee

Aggregation level query "value help" = Only Values in InfoProv doesn't work

Hi,
I have a problem with Selection Variable for a BEx Query :
- I'm working with SAP BI 7.0 support package 15
- My query is an input ready query built for an "aggregation level" based on "real time infocube" (Planning);
- Characteristic, I want to filter with variable, has query property Advanced->Query Execution for Filter Value Selection = Only Values in InfoProvider
- Characteristic (info-object) has set the property: Business Explorer tab--> Query Def. Filter Value Selection as Only Values in the info-provider...
My problem is:
when I execute a query,
the Select Values for Variables screen appears
I push on the Select from List button
and Select Values For MyCharacteristic appears...
but it shows me all values in master data table of my characteristic instead of only values in the infoprovider!!!
If I build a query for the Real Time Cube it works correctly, but if the query is built for the aggregation level it doesn't work!
Could someone explain me why it doesn't work correctly?
Thanks in advanced
Fede

Thanks to Mariana Lazar
30.03.2009 - 12:30:36 CET - Risposta by SAP
Dear Fede,
Regarding the query built on aggregation level please note the following
the aggregation level is always a Virtual Provider built other
InfoProvider and hence it does not have the dimension table and hence
the F4 mode D is not supported.
Therefore when aggregation level is used in a query, F4 does not supportD-mode: 'Only Values in InfoProvider' and all master data values are
displayed in the value list.
Reference from the note
984229 F4 modes for input help as of SAP NetWeaver 2004s BI
4. Since other InfoProviders do not have a dimension table, the system
displays only posted values if you select "Only Posted Values for
Navigation". Otherwise, it displays the values from the master data
table.
Hope this should clarify your doubts. Please let me know if you have
questions else please confirm the message at your earliest convenience.
Thank you for your cooperation and kind regards,
@KR@ Mariana Lazar
Senior Support Consultant
SAP Active Global Support
Netweaver Business Warehouse

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

Analysis Authorizations - Aggregation Level ( ':' )

Dear BW Gurus,
Greetings!!!
I have a scenario of migrating the Authorizations from BW 3.5 to BI 7.0 Analysis Authorizations.
There is a report based on InfoSet. There are about 8 authorization relevant objects among which the user is authorized for 3 Authorization relevant characteristic fields. In the previous version, It was working fine when tested.
In BI 7.0 Analysis Authorization Concept, I have created the Authorization Object with these 3 Auth relevant fields and assigned to the Role using S_RS_AUTH and then assigned it to a user. When I test the query with that particular user ID, the result was NO SUFFICIENT AUTHORIZATION.
When I checked the log, there it displayed the other authorization relevant fields for Aggregation level. So, my question is whether I must include the other Authorization relevant fields and restrict them for aggregation level (Value ':') and is it mandatory?
please guide me in this regard as early as possible.
Best Regards,
Priya

Hello,
Check st01 and su53 for missing objects then assign objects accordingly in the role or in analyse authorisation .
Thanks.
With regards,
Anand Kumar

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.

DP Disaggregation and Aggregation levels

Hi all,
I have a question regarding disaggregation and aggregation levels.
KFu2019s and disaggregation setup:
KF001:
Calculation type: I (not relevant)
Disag. Key Fig.: KF000 (not relevant)
Time-Based Disaggregation: K (not relevant)
Time-Based Disag. Key Figure: (not relevant)
KF002:
Calculation type: I
Disag. Key Fig.: Keyfigure001
Time-Based Disaggregation: P
We are now interested on the KF002. KF002u2019s disaggregation is based on KF001. I am trying to copy KF001 values to KF002 with a macro that is attached to a background job. Macro doesnu2019t do anything else than copy values from KF001 to KF002.
Background job setup:
Selection:
Sales organization: 2000AB
Location: 1000EF
Product: 1 to 2000 (consists 2000 products, including products that do not belong to above location)
Excluded values:
Customer group 1: 2500AB
Aggregation level:
Sales organization
Location
Product
Customer group 1
What I try to accomplish (through background job - mass processing):
I am trying to copy values with above setup so that the most detailed level which is Customer group 2 would have values through disaggregation. I have successfully copied values to product level, location level, sales organization level but the customer group 2 level values are not as KF001u2019s. Values are right in the SUM level, but not disaggregated right to customer group 2 level.
I get right results when I choose Customer group 2 to the aggregation level but this is not something we can do as it causes way too long runtimes. What I am also interested in is that how come the disaggregation does not work properly or does it? How can I get the disaggregation work so that I only have to select the aggregation levels which are defined in the selection and get proper results through disaggregation to customer group 2 level?
Thanks in advance,
Juha

Hello Juha,
You do not need another macro, just make the above change to your original one, and the macro should work.
Your aggregation level in the job should also be OK.
Since you mentioned that the values at detailed level are not the same as key figure 1, it sounds to me that the system did a pro rata disaggregation. Do you have the key figure 2 totally cleared out before copy? Since you're using disaggregation type 'I', it only disaggregates based on another key figure when the key figure value is initial.
So my suggestion is, you can try to change the key figure's disaggregation tyep to 'P' and check if the macro works.
Or if you have to use type 'I', you should add a step in the macro before the copy step, to initialize key figure 2 first.
To initialize a key figure, just put the row in the step, and for the 'Change Mode', select 'Initialization'.
Best Regards,
Ada

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.

IP question: Aggregation Level picture icon color?

Similar Messages

Maybe you are looking for