Aggregate Level

Hi all,
I am trying to create a aggregate for an infocube. Is it possible to create 2 different aggregate level for same Infoobject?
Say for exampl, i have infobject 0CO_AREA, i need to use it aggregation level 1 as well as aggregation level 2.
Please give me a suggestion,
Ill assign pionts,
Thanks in advance
Regards
Pooja

Not sure I understand the question.
You can certainly have multiple aggregates, with 0CO_AREA in each aggregate. You can have one aggregate be a more summarized aggregate. You can also create different aggregates with each on e specifying different fixed values for 0CO_AREA.
Or are you trying to create an aggregate that includes 0CO_AREA hierarchy levels?
Providing more details would help me understand what you want to do.

Similar Messages

Key figure fixing in aggregate level partially locking

Hi Guys,
When fix the cell in the planning book, getting "One or more cells could not be completely fixed" message.
1. If a material having only one CVC in the MPOS those quantity can be fixed correctly without any issues.
2. If a material having more than 1 CVC combination and try to fix one of the CVC combination quantity, it is fixing partially and getting the above message.
3. Even, it is not allowing to fix the quantity in aggregate level also.
We are in SCM 7.0.
Is there precondition that need to fix the material having only one CVC combination.
Even a material having multiple CVC combination why it is not allowing to fix one CVC combination in detail level.
Is aggregate level key figure fixing is not allowed ?
Please clarify.
Thanks
Saravanan V

Hi,
It is not mandatory to assign Standard KF to be able to fix. However your custom infoobject that you created must be of type APO KF and not BW KF.
That said, Let us try and address your first problem.
You can fix at an aggregate level. However there a few points to remember.
Let us consider a couple of scenarios.
1) In your selection id, it is showing a number of products. You are selecting all the products at one go and load the data and try to fix at this level. This is not possible.
2) In your selection id, you have selected a product division. For a single product division you are loading data and try to fix at this level. This is the true aggregate level and it should be possible at this level.
Hope this helps.
Thanks
Mani Suresh

Keyfigure fixing at aggregate level

HI,
I am using APO V4,
1. I am planning to fix my keyfigure only at aggregate level, My keyfigure is open at all levels like plant or material group or material, i can enter the data at any point manually. but when come to keyfigure fixing, i want to fix the keyfigure only at aggregate level, i mean if the keyfigure is at material level i need fix, any other level it should not allow me to fix.
I was thinking for a drill down macro, but my keyfigure should open at all levels irrespective of keyfigure fixing, is it manageable any how that keyfigure can only be fixed at material level?
2. this is a different issue from above, i have fixed the keyfigure for a month, after that i had run a copy macro to the fixed key figure, but the fixed values are overwritten once the copy job is completed, and when i check in the planning book, it is visible as fixed agian. do i need to have any macro specific setting for this during the copy macro?
Thanks in Advance
ARUN R Y

Hi Gurus,
I am having some problems with Key Figure Fix.
The business requirement:
Some fields must be kept fixed and locked during the interactive planning performed in tc /SAPAPO/SDP94.
What was done in order to do it:
We created macros using standard features in order to fix and block some cells in accordance with the business requirements. The first macro disaggregates the planning to the last level available for collaboration. Another macro using FIX_CALC and ROW_INPUT functionalities fixes and locks some cells (3 levels). After these activities the planning view is aggregated and it will be ready for collaboration.
These macros run automatically every time that the user open an specific planning view.
The problem:
After the aggregation when the disaggregated level is called again all cells have been showed fixed and locked. If we perform the fix and lock manually the system run correctly, i.e., only the cells fixed and locked are kept in this status after an aggregating and disaggregating processes.
Step-by-step
u2022 Set the macro in /SAPAPO/ADVM u2013 MacroBuilder. To use the macro FIX_CALC in aggregated level. The first attribute set with ROW ATRIBUTES, the second attribute set with VALUES. FIX_CALC (Cota de Vendas; Cota de Vendas). With this setting, the aggregated line will be fixed.
u2022 Set the macro in /SAPAPO/ADVM u2013 MacroBuilder. To use the macro FIX_CALC in level 1. The first attribute set with ROW ATRIBUTES, the second attribute set with VALUES. FIX_CALC (Cota de Vendas; Cota de Vendas). With this setting, the level 1 line will be fixed.
u2022 Set the macro in /SAPAPO/ADVM u2013 MacroBuilder. To use the macro ROW_INPUT in aggregated level. Cota de vendas = ROW_INPUT ( 0 ). With this setting, the aggregated line will be locked.
u2022 Set the macro in /SAPAPO/ADVM u2013 MacroBuilder. To use the macro ROW_INPUT in level 1. Cota de vendas = ROW_INPUT ( 0 ). With this setting, the level 1 line will be locked.
u2022 Now, go to in /SAPAPO/SDP94.
u2022 Disaggregated the planning view.
u2022 Run the FIX_CALC and ROW_INPUT macros.
u2022 Aggregated the planning view.
u2022 Disaggregated the planning view again. You can see the problem.
Thanks,

Whats Need of Multiple Aggregate Levels

Hi Gurus,
Can some one say whats the need of Multiple Aggregate Levels on a Multi provider?
Is it some thing Aggregate Levels are just to determine your level of Granularity you want to report upon?
If really ie the case cant we get it in the query it self by Free Characterstics, Drill Down, Slice and Dice Options?
Is any other strong reason for one need to go for Multiple Aggregate Levels or Aggregate Levels itself for that matter.
Thanks for clarification.
I am trying to understand things better as Iam very new to this area.
Regards,
BI-IP Guest

Manyak,
Really Thanks for your explanation. Though not completely but mostly I think I understand. Especially Iam really gtill time not aware of an Aggregate Level can supports Planning only at Lowest Granularity.
I read before that we cant change values at SUM, MIN/MAX Values. But now reading this I understand that we cant change values at Totals Level but only at items Level.
But again in your example can we change values at indepndent Line Item Level or For Region's Total Level at the end.
What in this Case if client wants to see both Country and Region under one Layout and both want to changeble for planning?
One more Last Question if that does not bother you..
What happens when one go for Input Read Query designed over the Multi-Provider (Contains a realtime Cube for Plan) it self instead of going to Multiple Aggregate levels or for that matter even a Single Aggregate Level also...All I want to know what difference it really makes for me in designing a Input ready Query or else in Getting my Layout or else in Planning Things.
Might be too many questions on Aggregate Levels but still I request to make me clear.
Thanks,
BI-IP Guest

Forecasting in DP: At aggregate level or at detailed level?

Hello All,
I have selection ID in APO DP 4.0 comprising of may products. I forecast them as a whole using some forecast method (may be seasonality method). How SAP DP forecasts? Does it individually forecast for each product or does it forecast at aggregate level? Has someone analyzed and come across such situation?
Thanks and Best Regards, Manoj

Dear Manoj,
The concept of selection and aggregation is very impotant in APO. Take an example:
You have a selection for packsize "Display SKU's under packsize A. Say there are 10 SKU's. Now when you run the forecast in the background, you need to define the selection and aggregation level. So for the same selection, if you have defnied the aggregation as SKU, the forecast job will for each SKU. However if "packsize" is selected in aggregation, the forecast will run at packsize level.
In the case of the interactive planning, the selection defines the aggregation level. Suppose you have loaded the selection described above and loaded for all SKU, the forecast will run for the entire packsize (aggregation across all SKU's). However to forecast individually in interactive planning, you need to load the SKU's one by one and run the forecast.
Regards,
Kedar

0PS_C04 (CONTROLLING) aggregate level

Hi,
I want to know if it's posible make to these extrators:
0PS_CSH_NWA: Payments in Network Activities
0PS_CSH_NTW: Network Payments
0PS_CSH_WBS: Payments in WBS Elements
More aggregate level, adding the doc_item field to them.
That it's posible? Or we have to make another extractors?
Thanks for your help.
Victoria

Check :
0CCA_C11 Delta and Full upload datasources.
0PS_C04 controlling - from which whcih data source should fill this cube
/thread/664877 [original link is broken]

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.

Unable to create Aggregate Level on Multi Provider ( Real and Standard)

Hi all ,
I am not able to create a " Aggregate Level " on a Multi Provider. When i say create i can't see any info Objects for selections and everything is grayed out i can't select the check boxes . Any idea on what i am doing wrong ?
Is this an authorization issue ?

Hi Suresh,
Are you trying to create an aggregate on the multiprovider? This is not possible...multiprovider itself does not contain any data..

0FISCPER defaults automatically in the Aggregate level

Hi guys,
I have a strange situation where I have 0FISCPER, 0FISCPER3, and 0FISCYEAR in my planning cube, but I only want 0FISCPER3, and 0FISCYEAR in my aggregate level.
For some reason, when I enter the 0FISCPER3 and 0FISCYEAR in the aggregate, the system automatically inserts the 0FISCPER characteristic in there as well. The quick solution is obviously to take the 0FISCPER out of the planning cube, but I want it in the planning so it can derive the value from 0FISCPER3 and 0FISCYEAR.
If I leave 0FISCPER in the aggregate level, then the system will need a value for it during the query design (or my cells will be locked), however, I do not want it in my Query.
So how can I make the system to stop inserting 0FISCPER in my aggregate, so I only have 0FISCPER3 and 0FISCYEAR in my aggregate.
Thanks
Edited by: Ehab Mansour on Sep 18, 2008 9:43 AM

Hi,
Thanks so much for your information Gregor.
But this is all very confusing for me, this is the first time I've come across this concept of "Exception aggregation".
My situation is as follows, and let me know if you have any suggestions:
I have a IP planning cube, which is a copy of the Cost Center Activity cube. With this copy, the only time characteristics I required and kept in my planning cube, was 0FISCPER3, 0FISCYEAR, and 0FISCVARIANT, but I took OUT of the cube 0CALDAY, and 0FISCPER.
Then I created my Aggregate level in IP based on this cube. Then I did a check, and it said everything was consistent, and activated it.
Then using query designer I created a query Key figures were Activity Quantity, and row characteristics were Cost Center and Activity type. Time characteristics used were 0FISCPER3, 0FISCYEAR, and 0FISCVARIANT.
When I executed my query, I got the following message:
"Exception aggregation reference characteristic 0CALDAY not in info provider", and it seems like my query is locked, maybe as a result of this.
1) Does this mean I need 0CALDAY in the cube?
2) if the above is yes, then it will prompt me to put it in the Aggregation level as well, and if it's in the aggregation level, then it's going to expect me to give it a value in the query (otherwise it will lock), which I don't want to do.
Why does it need the 0CALDAY in the cube?
Can you suggest some options for this. Is there a way I can avoid having 0CALDAY in the cube and aggregate level? OR do I just leave it in the query, and find an SAP Exit variable that will just automatically populate this for me?
Sorry if I've repeated myself.

Aggregates (Levels)

Hi, Somebody know if exist a Table where I can get the level of an aggregate?
I have many Cubes with many aggregates (e.g. Aggregate 100100 Parent / 100101 Child / 100102 Grandson, etc..)
I need to separate all aggregates Parents, and childs.
**I know I can get this in RSA1 IN "Aggregates Tree" icon; but I need get its level for all Aggregatescubes.
Tanks so much
P.S. I triend in SE16 Table: RSDDAGGRDIR, but I not view a field with agregate tree level.

Thanks Manga,
I need to know the the same information I get in RSA1 / Aggregate Maitenance / Aggregate Tree "icon":
e.g. This leves in the tree:
100001                            (Level 1)
      100506                      (Level 2)
            100989                (Level 3)
Thansk

Allocation check at aggregate level

hi,
The scenario is this :
Allocations are maintained at sales organization level. Allocation check is working fine.
The requirement is that the check should happen at sales org. group level.
e.g. sorg 'a1' and 'a2' belong to sorg group 'A'. Allocations to be maintained at level A. User to enter sorg a1 at the time of sales order creation in ECC but the allocation should be checked at A.
Regards,
RS

RS,
Here the expectation is that even if char combination is found at lower level at which no allocations are maintained, system should check allocations at collective level.
Well, that may be your expectation, but that is not how it works.
The system searches from the most specific to the least specific CVCs. If it finds a hit at the 400555 a1
CVC, it stops searching, and uses the allocation quantity that exists in 400555 a1. If the qty is zero, then you get no confirmation.
In this particular context, the '####' means 'any sales org that has not been specifically mentioned as a CVC'. So, if your sales docs contain the following combinations:
Sales Doc A 400555/a1 100pc
Sales Doc B 400555/a2 100pc
Sales Doc C 400555/a3 100pc
Sales Doc D 400555/a4 100pc
and all you had in your CVCs are
400555 a1 quantity 0
400555 #### quantity 1000
Then Sales doc A would find 400555 a1, and the order would not be confirmed. Sales Docs B, C, D would find 400555 ####, and would be confirmed.
Relating this to original query, this check should happen at sales org superset level.
So to achieve this, allocations in combination with aggregation in DP is must ?
Hold on. You haven't yet told me where this superset characteristic is coming from. How do you identify in a Sales order that this 'sales org group' is relevant for this sales order? Where is the grouping maintained in ERP?
Best regards,
DB49

The accumulation at the aggregate level

Hi,
in the web form, I entered data in the first 3 months (January, February, March) ...I recorded ... but the accumulation does not occur at the Q1. Q1 take just the values of the March.

Is this a Classic Planning Application? If yes, here are the steps version 11.1.1.3: http://download.oracle.com/docs/cd/E12825_01/epm.111/hp_admin/mem_prop.html

LAG function doesn't works correctly changing aggregates level

Hello there,
I'm trying to use the function in Discoverer Desktop but i'm experiencing some problems.
First of all i will explain what i'm trying to do.
I've to treat data from a typical business datawarehouse and i want to show in the same worksheet both the totals,year fixed (calculated partitioning by months and other fields of dimensions ) for the current year and for the passed year.
I've done this by making a summary table that calculates SUM(import) grouping by some fields and a LAG(SUM(Import),1)over (partition by <fields> order by year ASC).
This last expression effectively returns the sum of the passed year.
The problem is from now on: if i want to roll up over a hierarchy i noticed that some values of the totals of the passed year are different from the import calculated by the simple SUM (of course changing the year... :-) ) ... Mining inside the data i discovered that some there were some rows filled in the SUM column that were empty on the LAG column. This is because running the query, if there isn't any row resulting by aggregating on a certain year and month, it cannot be any calculation for the LAG, and the result is an empty entry for the LAG (but it's not correct).
Does someone know a workaround or some function like LAG that is not affected by this problem?
Many thanks in advance for any kind of help
Greetings to all

You might want to user NVL() before SUM()
Ex:
LAG(SUM(NVL(Import,0)),1) over()
Use NVL wherever you use SUM, because:
1+NULL = NULL
Hope this helps :)

Phase out settings at a higher level such as brand or major customer

Have any of you ever setup phase out assignments at a higher level than product and had it work correctly? For example, we want to phase out a brand for a major customer. In other words, a customer is dropping a brand and we don't want statistical forecast generated for that brand customer combination any longer. I am able to setup the fields in phase out lifecycle settings for product, brand, major account but when i enter the brand and major account I am still getting forecast generated. It appears to stop for some products within the brand but not all. Another example is if a customer quits ordering from us I want to setup the major customer to phase out so no forecast is generated.
If you have done this successfully please let me know. Or if you would handle these situations in a different manner other than phase out please let me know. We can do historical adjustments each period but that is a lot of maintenance to do after each period before statistical forecast is generated.
Thanks
Steve

Hi Stephen,
Life cycle planning works only at the detail level (each CVC), the option of aggregate planning is helpful if you want to phase in or out a certain CVC when you are forecasting at the aggregate level.
One option is that you should have all products in the "profile assignment for life cycle " section which falls under that brand and customer. you can maintain a file and then automate the upload process in to the "assignment"
or
you can try to use the copy functionality in the realignment (/SAPAPO/RLGCOPY) , where you maintain copy factor as NIL and when the stat fcst is generated, you can use this as the next step to zero out -but you would need to maintain them manually.
or
easiest and safest wayy would be create a selection for those combination and do not include them in the planning job for stat fcst.
or
you can build a customised program to access the PA, PB, Data view and input the selection to zero out the stat fcst KF for that particular selection after the stat fcst run. here you would need to check if the diaggregated values are good enough.
hope it helps.

Content Level

I have a fact table with 11 million rows that joins with 8 dimesion tables to form a perfect star schema.
The client said that he can reduce the row size to 6 million if we remove 3 dimensions from the joins. So he created a materialized view with 6 million rows joining with 5 dimesnions which he is going to use the most in the reports.
The client requires the previous model as well because there are 2 reports out of the 7 reports that will be based on the 11 million rows fact and the 8 dimension tables.
if I convert this scenario to the aggregate and detail level Fact. I will have 2 models (5 Dimesnion model lets say it as aggregate and 8 dimesnion model as detail). Now i will create a BMM layer subject area and promote the detailed level model to the BMM layer. For Aggregate I will start mapping each of the objects in BMM layer except for thr 3 dimension tables that are nor present in AGG model with the Agg model (5 dimesnions) of the physical layer.
While Aggregate navigation and creating dimension hierarchies we set the content level navigation for each logical table source to the level at which the lowest granularity exists. However in my scenario. The granularity for both the model will be same. So how will the query from OBIEE recognize which model to use when a report is built as both the models are built at the same content level with the exception of 3 dimsion tables.
Please help it is urgent. How should I implement this scenario?

For your "fact" table in the BMM, you should have two LTS - one for the detail level data, one for the aggregate level data.
For each of your dimension tables, you should set up a hierarchy (sorry, using standard accepted terms of objects here...not Oracle's non-standard ones....) Each dimension should have at least a "total" and "detail" level, more if there are a proper hierarchy.
Then when you set up your LTS, for the detail one - each of your eight dimensions will have content level set to the detail levels. For your aggregate LTS, on the three dimensions that aren't present, set the content level to the "total" level. I'd also set the PRIORITY GROUP so that the aggregate gets chosen first instead of the detail.
Hope this helps!
Scott

Aggregate Level

Similar Messages

Maybe you are looking for