Macro-Caculation values lowest level

Hello,
I have e question. I want calculate values of different key figures. Is it possible that I calculate the values on the lowest lovel of each key figure. Is there any function in apo dp?
Kind Regards

Hi Christian,
You can use a drill down macro and then perform calculations of key figures.
In your activity use the drill down macro in the first action and key fig calculation in the next. Use this activity in the job as per your selection ID.
Regards
JB

Similar Messages

Macro DP_Transfer values lowest level in a new kew figure

Hello,
i hope everyone can help me. I have 3 key figures with the same characteristic value combinations. According a specific logic, values has to transfer in a fourth key figure. It is possible to transfer values (only detail Level) in the 4 key figures independant of each other.
The logic should be: Is there a value for the characteristic value combinations in one of the 3 key figures => Transfer in the fourth key figure. Is there no value for the characteristic value combinations in a key figure => Do nothing.
Kind Regards

Hi Christian,
If you want to check all the key-figure for INITIAL values the logic could be as below:
if KF1 eq intial AND KF2 eq initial AND KF3 eq initial.
Do nothing.
else.
logic.
Endif.
If you want to check ANY ONE of the key-figure for INITIAL values the logic could be as below:
if KF1 eq intial OR KF2 eq initial OR KF3 eq initial.
Do nothing.
else.
logic.
Endif.
Hope this will help.
Regards,
Mukesh Pandey

How to return list of lowest level elements in a hierarchy given the node o

We would like to return a list of the lowest level Elements in a Hierarchy from a given node of the hierarchy. The level of the node that is given to us is unknown, but regardless, we need the ability to return the lowest level elements. We are trying to find a non-ABAP solution to our needs and trying to use a BEx query as a source for our APD.
In query designer we are able to obtain the correct list when using the Hierarchy and Condition with a Leaf value of '1' to return the lowest level. However, We have come to learn APDs do no support the BEx hierarchies. When we de-selected the 'Activate Hierarchy' display in the query, the entire structure under the given node is returned.
Does anybody know of a way to return just the lowest level elements in a hierarchy so we can feed our APD?
Thanks,
Andrea

expac works only with official and unofficial repos, not with the AUR, but it's very nice.
Adding '-q' should help, grep to weed out false positives.
yaourt -Sa $(yaourt -Ssaq pulse)
works, but
$ yaourt -Sa $(yaourt -Ssaq chrome)
resolving dependencies...
looking for inter-conflicts...
warning: removing 'chromium' from target list because it conflicts with 'chromium-no-sse2'
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: chromium-no-sse2 and chromium-scroll-pixelGs are in conflict
so at least
$ yaourt -Sa $(yaourt -Ssaq chrome|grep google)
is needed.
Edit: Also:
$ LC_ALL=C TZ=GMT0 diff -Naur /usr/bin/pacsearch /usr/local/bin/pacsearch
--- /usr/bin/pacsearch 2014-11-21 11:20:37.000000000 +0000
+++ /usr/local/bin/pacsearch 2014-12-21 08:21:14.758856006 +0000
@@ -84,7 +84,7 @@
my %allpkgs = ();
-my $syncout = `pacman -Ss '@ARGV'`;
+my $syncout = `pacman -Ssq '@ARGV'`;
# split each sync search entry into its own array entry
my @syncpkgs = split(/\n^(?=\w)/m, $syncout);
# remove the extra \n from the last desc entry
@@ -110,7 +110,7 @@
$allpkgs{$pkgfields[1]} = [ @pkgfields ];
-my $queryout = `pacman -Qs '@ARGV'`;
+my $queryout = `pacman -Qqs '@ARGV'`;
# split each querysearch entry into its own array entry
my @querypkgs = split(/\n^(?=\w)/m, $queryout);
# remove the extra \n from the last desc entry
$ /usr/local/bin/pacsearch pulse
libpulse
pulseaudio
libao
libcanberra-pulse
libpulse
paprefs
pavucontrol
pulseaudio
pulseaudio-alsa
floyd
libcec
mate-media-pulseaudio
mate-settings-daemon-pulseaudio
ponymix
projectm-pulseaudio
Although why not simply use pacman or expac?
Last edited by karol (2014-12-21 08:26:48)

Aggregation at the lowest level in the cube

Hi guys
I designed very simple test cube with one dimension (both MOLAP driven).
The dimension PRODUCT consists of three levels:
- Group
- Category
- Product_detail
PRODUCT_SRC table to load PRODUCT dimension:
PR_GROUP_NAME PR_GROUP_ID PR_CATEGORY_NAME PR_CATEGORY_ID PR_DETAIL_NAME PRODUCT_DETAIL_ID
dairy 1000 yoghurts 1000000 yoghurt_1 1000000000
dairy 1000 yoghurts 1000000 yoghurt_2 1000000001
dairy 1000 yoghurts 1000000 yoghurt_3 1000000002
candy 1001 cookies 1000001 cookies_1 1000000003
candy 1001 cookies 1000001 cookies_2 1000000004
candy 1001 cookies 1000001 cookies_3 1000000005
beverages 1002 juices 1000002 juice_1 1000000006
beverages 1002 mineral water 1000003 mineral_water_1 1000000007
beverage 1002 energy drink 1000004 energy_drink_1 1000000008
The cube SALES has one measure:
- Value_of_sales (sum aggr)
SALES_SRC table to load SALES cube:
VALUE PROD_ID ID
1236 1000000002 2
115 1000000006 3
1697 1000000005 4
12 1000000004 5
168 1000000008 6
1984 1000000005 7
9684 1000000004 8
84 1000000002 9
8 1000000007 10
498 1000000006 11
4894 1000000008 12
4984 1000000004 13
448 1000000003 14
4489 1000000004 15
13 1000000001 16
879 1000000004 17
896 1000000006 18
4646 1000000007 20
I created the dimension PRODUCT and a mapping which loaded the data into the dimension. It worked perfectly. The hierarchy was created as I expected.
Then I created cube SALES and a mapping which should load the data into the cube. It is very very simple mapping - there were just only two items on the canvas:
- SALES_SRC table
and
- SALES cube
and two lines:
- from SALES_SRC.VALUE to SALES.VALUE_OF_SALES
- from SALES_SRC.PROD_ID to SALES.PRODUCT_NAME
Then I deployed everything and ran mapping, which loaded cube. But in my opinion the cube was not populated in a proper way, because it was no aggregation performed at the lowest level of product hierarchy - there was only a value of the first occurence of certain product. I mean:
In SALES.SRC we have for instance:
VALUE PROD_ID ID
1236 1000000002 2
84 1000000002 9
For me the the value in the cube should be 1236 + 84 = 1320, but the value in the cube at PRODUCT_DETAIL_LEVEL for yoghurt_3 is only 1236 - first occurence of this product in SALES.SRC.
Why hasn't been the data aggregated at lowest level of PRODUCT dimension hierarchy - is it the way OWB does such things?
Should I manually aggregate the data before loading to cube (just to use Aggregator to aggregate the data at lowest level)? If yes - what about incremental loading of data to cube (the old value value is simply replaced by new one and not summed in the cube)
In data warehouse solutions of other vendors the cube in such situation is loaded as I expected here.
I really don't know what to do. I do really appreciate any help from you.
Thank you in advance
Peter

Hi David
Thank you very much.
Now I'm sure that I have to aggregate facts by myself at the lowest level of hierarchy in a dimension.
Regards
Peter

How to include non-joining records from level one in the lowest level?

As an example the dimension has three levels with data coming from three source tables. The relationships between these tables are zero to many. As a result of this e.g. there are records at the first level that do not join to the second table for level two, i.e. there is a customer entry but the customer has not acquired any products. However, we would like to see in the query for the lowest level also the customers that didn't acquire any products. They are there when there is no filter for the lowest level, but that returns duplicate data. I was hoping I could accomplish this by using outer joins when loading the dimension, but it loads the same as without the outer joins. Hopefully, this trivalized example describes what I am trying to accomplish.

You won't be able to have a true "default" value in the various cascading levels, since there aren't default values in a dynamic cascading parameter. That being said, I've created a sample report in Crystal Reports 2008 that has a Command-driven DCP with '*' values for the 2nd and 3rd levels of my 3-tier DCP and have accounted for them in the record selection criteria. You can find the sample here at https://www.box.net/shared/mav5qp337j

Why do we need to plan promotions at the lowest level of aggregation

Hi,
The documentation says that we need to plan the promotions at the lowest level of aggregation i.e., the material level. Why? Is there a specific reason for this? Can we plan at other levels of aggregation as well? What happens if we plan at higher level;s of aggregation?
Thanks.

I think it is possible to do it in an aggregated level however you need to define your distribution rules in order to get the desired result, you need also to consider that if distribution rules changes and the value after promotional planning returns the same value, it is possible that detailed level are not realigned to the new distribution rule (e.g. regarding another ratio).
Maybe this is one of several causes.
Regards,
Carlos

Assign WBS AVAC not in the lowest level of WBS elements

Dear SAP Community,
Our client has requirement to have budget availability control in WBS element level 3 while the WBS structure is until level 5 and the actual posting will occurred in WBS element level 5.
Our current setting is to have WBS element level 5 as Planning Element and Account Assignment Element. So, user can upload their WBS planning data from the lowest level of WBS structure. Then we copy the Planning Data as Budget through CJ30 and release it through CJ32.
If we set the value of Budget Data in CJ30 and CJ32 until the level 5, the system check AVAC in WBS level 5 instead of the amount rolled up in WBS level 3. If we set the value of Budget Data in CJ30 and CJ32 in WBS level 3, the system will check AVAC in WBS level 3 (as we expected) but the consequence is comparison of actual vs budget in WBS level 5 will have variance 100%.
Is there any way to define the budget data until WBS level 5 but the AVAC control is in WBS level 3?
Appreciate your inputs
Thank you and best regards,
Fitria

Hi,
>If we set the value of Budget Data in CJ30 and CJ32 in WBS level 3, the system will check AVAC in WBS level 3 (as we >expected) but the consequence is comparison of actual vs budget in WBS level 5 will have variance 100%.
We had similar kind of requirement, we had followed the above process. THis will provide the required functionality except the variance in reports. Try and convince the client to settle for this if this meets your requirements.
As AVAC can't be managed at WBS levels.
Regards,
Harsh.

Lowest Level in Dimension

HI guys
i have rdbms 9.0.4
can i define lowest level of dimension that is not the primary key of the dim table ( this field has unique values)
or the lowest level of dimension should be the primary key of the dimension table.
thanks alot.
Brad

Hi Matt!
Glad to read you again!
I agree with you that in this simple example, I should be able to make this a star schema.
but :
- on a functional point of view, this date is an attribute of a vehicle, not of an invoice. But let's ignore this.
- this problem is the same as one we have in another part of the BM, which is much more complex. In this complex BM, I can't use star schemas because it removes some joins we need in order to perform some reports.
This is why I'm looking for another way to proceed.
If you have time to spend on the complex BM, here is a simplified description :
* in the physical layer, I have:
- a calendar table with multiple aliases to be used with each dates in the following,
- an invoice header table
- an invoice detail table
with
some header date -> header table -> detail table
some detail table -> detail table
* in the logical layer (stars), i have:
- my calendar dates with their dimensions
- an invoice dimension table with the two sources (header + detail) + its dimension
- an invoice header fact table
- an invoice detail fact table
header date -> header fact
invoice dim -> header facts
invoice dim -> detail facts
detail date -> detail facts
I mus be able to query details facts while showing or filtering the header date. In such a configuration, you'll understand it isn't possible as there isn't any relationship between the detail facts and the header date. This is why the header date should be kept as a dimension of the invoice dimension, which is similar to my basic example.
Unless I went wrong somewhere?
Thanks!
Ced.
Message was edited by:
ced

Lowest Level in APO DP Heirarchy

In APO DP, how would a charecteristic is identified or noted as the lowest level in a heirarchy. I mean, if i have a product heirarchy as Main Grp -> Sub Grp -> SKU and SKU is my lowest level, how do i inform APO about the same. While creating POS there is no option of specifying the lowest level.
Thanks & Regards,
Ganesh

There is no way to specify a characteristic to be lowest level. Unline R/3 Product Hierarchy, APO CVCs are flat.
Notionally SKU is lowest level because the CVCs will be something like the exmaple below where you can see SKU Chacateristic is having unique value not the other characateristics.
CVC   : Product Family         - Product Sub Family    - SKU
CVC1   Home Entertainment - DVD Player                - Model A
CVC2   Home Entertainment - DVD Player                - Model B
CVC3   Home Entertainment - DVD Player                - Model C
CVC4   Home Entertainment - Blu Ray Player           - Model D
CVC5   Home Entertainment - Blu Ray Player           - Model E
and like wise for other product family
CVC6   Personal Entertainment - MP3 Player                - Model XX
CVC7   Personal Entertainment - MP3 Player                - Model XY
The same SKU cannot belong to different Product Family / Sub Family. This is the Product Dimension.
You should have Location Dimension where you define similar notional Hierarchy for Location where the lowest level would be SoldTo or ShipTo which can be part of a Sales Office, Region etc. characteristics.
Hope this helps.
Somnath

Top 10 lowest level dimension members based on measure

Hi,
I'm trying to create a condition with JDeveloper to show the top 10 dimension members based on a measure for the lowest level of the hierarchy, but doesn't work.
All other conditions are working well, including top 10 dimension members in other levels of the hierarchy (not in the lowest).
Any suggestion??
I think the dimension is defined ok, all other conditions are working well and the lowest level could be shown with other conditions and drills.
Thanks in advanced....

Hi,
First, my BI Beans version is 9.0.3.5 and my database version is 9.2.0.2.1
I will try to clarify my problem. I am trying to create a graph to show the top10 members of a dimension based on my measure. When I define this condition
to show the top 10 members of a middle level (not de low level), it works fine, I mean, it shows the top 10 members of that level. But, when I define the condition
to show the top 10 members of the low level, it displays me that there is no data to display (The data has an insufficient number of columns and rows).
I have been testing this case, and I have seen that if I change the low level column (number type) of the dimension to a varchar type column, it works. This low level is
the primary key of the dimension table, and it's referenced by a foreign key in the fact table.
Which could be the problem?? Is it not possible to define a level of a dimension with a number column??
I have a demo sample to see this problem (two simple dimensionS with three levels and a fact table). It's a bit large to post it complete, so I post here an extract of it.
-- Dimension and fact tables
CREATE TABLE PR_DIM_A (DIM_A_KEY NUMBER,
               LOW_A_LEVEL_NAME VARCHAR2(50),
               ALL_A_LEVEL_ID VARCHAR2(50), ALL_A_LEVEL_NAME VARCHAR2(50),
               GROUP_A_LEVEL_ID VARCHAR2(50), GROUP_A_LEVEL_NAME VARCHAR2(50),
               CONSTRAINT PK_DIM_A PRIMARY KEY (DIM_A_KEY));
CREATE TABLE PR_DIM_B (DIM_B_KEY NUMBER,
               LOW_B_LEVEL_NAME VARCHAR2(50),
               ALL_B_LEVEL_ID VARCHAR2(50), ALL_B_LEVEL_NAME VARCHAR2(50),
               GROUP_B_LEVEL_ID VARCHAR2(50), GROUP_B_LEVEL_NAME VARCHAR2(50),
               CONSTRAINT PK_DIM_B PRIMARY KEY (DIM_B_KEY));
CREATE TABLE PR_FACTS (FACT_KEY NUMBER, DIM_A_KEY NUMBER, DIM_B_KEY NUMBER,
               MEASURE_1 NUMBER, MEASURE_2 NUMBER,
               CONSTRAINT PK_FACTS PRIMARY KEY (FACT_KEY));
ALTER TABLE PR_FACTS ADD CONSTRAINT FK_DIM_A FOREIGN KEY (DIM_A_KEY)
               REFERENCES PR_DIM_A (DIM_A_KEY);
ALTER TABLE PR_FACTS ADD CONSTRAINT FK_DIM_B FOREIGN KEY (DIM_B_KEY)
               REFERENCES PR_DIM_B (DIM_B_KEY);
-- Data inserts in the dimensions
INSERT INTO PR_DIM_A VALUES (1,'ALL','ALL_NAMEa','GROUP1a','GROUP1_NAMEa','LOW1a','LOW_NAME1a');
INSERT INTO PR_DIM_A VALUES (2,'ALL','ALL_NAMEa','GROUP1a','GROUP1_NAMEa','LOW2a','LOW_NAME2a');
-- ......... dimension B is the same kind of data.
-- OLAP dimension A creation script
cwm2_olap_dimension.create_dimension('BI02', 'PR_A_DIM', 'DimA Diaplay name', 'DimA Plural name', 'DimA Short Description','DimA Description');
cwm2_olap_dimension_attribute.create_dimension_attribute('BI02', 'PR_A_DIM', 'Short Description', 'Short Descriptions', 'Short Desc', 'Description', TRUE);
cwm2_olap_hierarchy.create_hierarchy('BI02', 'PR_A_DIM', 'HIER_DIM_A', 'HIER_DIM_A Display name', 'HIER_DIM_A ShortDesc', 'HIER_DIM_A Desc','Unsolved Level-Based');
cwm2_olap_dimension.set_default_display_hierarchy( 'BI02', 'PR_A_DIM', 'HIER_DIM_A' );
cwm2_olap_level.create_level('BI02', 'PR_A_DIM', 'ALL_LEVEL_A', 'ALL_LEVEL_A DisplayName', 'ALL_LEVEL_A PluralName', 'ALL_LEVEL_A ShortDesc', 'ALL_LEVEL_A Desc');
cwm2_olap_level.create_level('BI02', 'PR_A_DIM', 'GROUP_LEVEL_A', 'GROUP_LEVEL_A DisplayName', 'GROUP_LEVEL_A PluralName', 'GROUP_LEVEL_A ShortDesc', 'GROUP_LEVEL_A Desc' );
cwm2_olap_level.create_level('BI02', 'PR_A_DIM', 'LOW_LEVEL_A', 'LOW_LEVEL_A DisplayName', 'LOW_LEVEL_A PluralName', 'LOW_LEVEL_A ShortDesc', 'LOW_LEVEL_A Desc' );
cwm2_olap_level_attribute.create_level_attribute('BI02', 'PR_A_DIM', 'Short Description', 'ALL_LEVEL_A', 'Short Description', 'All_LEVEL_A DisplayName', 'ALL_LEVEL_A ShortDesc', 'ALL_LABEL Desc', TRUE );
cwm2_olap_level_attribute.create_level_attribute('BI02', 'PR_A_DIM', 'Short Description', 'GROUP_LEVEL_A', 'Short Description', 'GROUP_LEVEL_A DisplayName', 'GROUP_LEVEL_A ShortDesc', 'GROUP_LEVEL_A Desc', TRUE );
cwm2_olap_level_attribute.create_level_attribute('BI02', 'PR_A_DIM', 'Short Description', 'LOW_LEVEL_A', 'Short Description', 'LOW_LEVEL_A DisplayName', 'LOW_LEVEL_A ShortDesc', 'LOW_LEVEL_A Desc', TRUE );
cwm2_olap_level.add_level_to_hierarchy('BI02', 'PR_A_DIM', 'HIER_DIM_A', 'LOW_LEVEL_A', 'GROUP_LEVEL_A' );
cwm2_olap_level.add_level_to_hierarchy('BI02', 'PR_A_DIM', 'HIER_DIM_A', 'GROUP_LEVEL_A', 'ALL_LEVEL_A' );
cwm2_olap_level.add_level_to_hierarchy('BI02', 'PR_A_DIM', 'HIER_DIM_A', 'ALL_LEVEL_A' );
cwm2_olap_table_map.map_dimtbl_hierlevel('BI02', 'PR_A_DIM', 'HIER_DIM_A', 'ALL_LEVEL_A', 'BI02', dim_table, 'ALL_A_LEVEL_ID' );
cwm2_olap_table_map.map_dimtbl_hierlevel('BI02', 'PR_A_DIM', 'HIER_DIM_A', 'GROUP_LEVEL_A', 'BI02', dim_table, 'GROUP_A_LEVEL_ID' );
cwm2_olap_table_map.map_dimtbl_hierlevel('BI02', 'PR_A_DIM', 'HIER_DIM_A', 'LOW_LEVEL_A', 'BI02', dim_table, 'DIM_A_KEY' );
cwm2_olap_table_map.map_dimtbl_hierlevelattr('BI02', 'PR_A_DIM', 'Short Description', 'HIER_DIM_A', 'ALL_LEVEL_A', 'Short Description', 'BI02', dim_table, 'ALL_A_LEVEL_NAME' );
cwm2_olap_table_map.map_dimtbl_hierlevelattr('BI02', 'PR_A_DIM', 'Short Description', 'HIER_DIM_A', 'GROUP_LEVEL_A', 'Short Description', 'BI02', dim_table, 'GROUP_A_LEVEL_NAME' );
cwm2_olap_table_map.map_dimtbl_hierlevelattr('BI02', 'PR_A_DIM', 'Short Description', 'HIER_DIM_A', 'LOW_LEVEL_A', 'Short Description', 'BI02', dim_table, 'LOW_A_LEVEL_NAME' );
-- OLAP dimension B creation script is similar than A.
-- OLAP CUBE creation script
cwm2_olap_cube.create_cube( 'BI02', 'PR_CUBE', 'Sample Cube', 'Sample Cube', 'Sample Cube' );
cwm2_olap_measure.create_measure('BI02', 'PR_CUBE', 'MEAS1', 'MES1 DisplayName', 'MES1 ShortDesc', 'MES1 Desc');
cwm2_olap_measure.create_measure('BI02', 'PR_CUBE', 'MEAS2', 'MES2 DisplayName', 'MES2 ShortDesc', 'MES2 Desc');
cwm2_olap_cube.add_dimension_to_cube( 'BI02', 'PR_CUBE', 'BI02', 'PR_A_DIM' );
cwm2_olap_cube.add_dimension_to_cube( 'BI02', 'PR_CUBE', 'BI02', 'PR_B_DIM' );
dimkeymap :=
     'DIM:'
|| 'BI02'
|| '.PR_A_DIM/HIER:HIER_DIM_A/LVL:LOW_LEVEL_A/COL:DIM_A_KEY;DIM:'
|| 'BI02'
|| '.PR_B_DIM/HIER:HIER_DIM_B/LVL:LOW_LEVEL_B/COL:DIM_B_KEY;';
cwm2_olap_table_map.map_facttbl_levelkey( 'BI02', 'PR_CUBE', 'BI02', fact_t, /*'ET'*/ 'LOWESTLEVEL', dimkeymap );
cwm2_olap_table_map.map_facttbl_measure( 'BI02', 'PR_CUBE', 'MEAS1', 'BI02', fact_t, 'MEASURE_1', dimkeymap );
cwm2_olap_table_map.map_facttbl_measure( 'BI02', 'PR_CUBE', 'MEAS2', 'BI02', fact_t, 'MEASURE_2', dimkeymap );
Thanks a lot for your help....

Exluding lowest level dimensionmembers from a total report.

Hi,
I know this thread might belong in the Discover part of the forum, but based on previous experience it seems that Discoverer for OLAP help is difficult to come by in that part. Also I think this quickly might end up with being a bit more OLAP technical.
To the issue:
Say that you have a sales cube with 3 dimensions, time, product and customer.
The customer dimension has three levels with one standard hierarchy in the following order: Total, customerclass and customertype.
For the lowest level there is a customertype member thats named "internal". This means that all employees buying from their own company with a special discount is placed under this member.
Now to the report:
Using discoverer for Olap, management want two total reports. One where the Internal member is included, and one where it is excluded. This meaning that the initial report should just show the total levels for all dimensions, just with different totals.
Now I thought of just not include the internal member when you choose different dimensions in the query builder, but as far as I know this would only work for the lowest level. Total and customerclass would still show sums that include the internal level since the cube has aggregated these levels in advance.
Does anyone a way to work around this?
some cube facts:
database version 10.2.0.3. with the OLAP A patch
cube compressed and partitioned along month, fully aggregated for all levels(except year).
regards Ragnar

Rangar,
Simplicity is in the eye of the beholder, but you should be able to make it work. The details will depend on your source mapping, but I will assume that you have a single dimension star table with three columns, one per level.
CREATE TABLE CUST
Total varchar2,
CustomerClass varchar2,
CustomerType varchar2
I'll assume further that the member 'INTERNAL' appears as CustomerType. Define a VIEW on top of the table like this.
CREATE VIEW CUST_VIEW AS
SELECT *
FROM CUST
WHERE CustomerType != 'INTERNAL'
Now create two new levels
TOTAL_EXTERNAL
CUST_CLASS_EXTERNAL
Create a new level hierarchy, EXTERNAL_HIER say, that includes the two new levels along with the existing CustomerType level.
TOTAL_EXTERNAL
CUST_CLASS_EXTERNAL
CUSTOMER_TYPE
Note that even though the CUSTOMER_TYPE level appears in two hierarchies, the members in that level can vary be hierarchy. This is important since it means you do not have to reload the leaf data for the cube.
Now map the new hierarchy to the three key columns in CUST_VIEW. To do this correctly you need to switch to the "Snowflake Schema" view on the AWM mappings tab. This allows you to explicitly set the parent column for each hierarchy. So, in your new EXTERNAL_HIER hierarchy the parent of CUSTOMER_TYPE is CUST_VIEW.CustomerClass. In your old hierarchy, INTERNAL_HIER say, the parent of CUSTOMER_TYPE is CUST.CustomerClass. If you don't switch to the "Snowflake Schema" view then you will end up with null values for the parent dimension. (I just wasted 45 minutes discovering this fact.)
You now have two hierarchies and five levels. Your aggregation strategy for the cube should reflect this in some way. If you want full pre-aggregation, then you will need to add the two new levels to the cube. If not, then you are probably set.
David

Lowest level planning ???

hi sir
What is the lowest level of planning???
2. Smoothing u2013 How do you do time period wise ???

Hi Dallyanusha,
1) The Lowest level of planning is planning or forecasting at the product level.
2) Smoothing:- You need to maintain alpha, beta, gamma values, seasonal
periods etc.,
Regards
R. Senthil Mareeswaran.

Lowest Level of Details

Hello All,
I have one planning area which containts 33 Characteristics.Can any one please let me know how to find the lowest level of details out of the above 33 characteristics combinations ?
For example out of these 33 characteristics, there could be some 7 characteristics which are at the most detailed or lowest level and my problem is how to find these 7 characteristics combinations ?
Thanks in advance !!
Regards,
Pawan.

Hello Srinivas,
Thanks for the solution. Need one more clarification. In my last mail, i have just mentioned as an example of 7. Lets say i do not know how many characteristics out of the 33 form my most detailed level. Is there any way to find the number of characteristics out of 33 which make the detailed level and then apply the logic u have mentioned. I have tried to find but iam not sure of the result. As you said i have dumped all the possible CVC from planning area using remote infocube in excel. I applied advanced filter of unique records for all of the above CVC excluding time and KF columns. i got 1750 unique records. Then i tried generating same 1750 unique records using different combination of characteristics.I was able to get these 1750 records using as few as 10 char combinations values and also using 13 char combinations values. Then in this case does my 10 char combinations values are the most detailed level or 13 CVC ? Also this most detailed level char combinations remains constant through out the entire forecast horizon.??
I really appreciate your last prompt reply of my question. Thats what makes you the highest contributor in the last month.
Thanks,
Pawan.

On deleting lowest level members

Hi, Why is it that some upper level member data is lost when I delete its lowest level members? I don't have dynamic calculation members in my cube. Is this because of the restructuring after the outline has been changed?

Is this only occurring on one-to-one relationships? i.e - a parent with only one child?If this is the case this is due to an implicit share (the data is only stored once, not in both members) and when you delete the child the value disappears from the parent also.Hope this helpsDavid Cooper, Analitica Ltdwww.analitica.co.uk

My battery life at a full 100% charge is about 2 hours 22 minutes (backlight and key lights at lowest level). Should I go complaining to Apple or do I just need different software?

My battery life at a full 100% charge is about 2 hours 22 minutes (backlight and key lights at lowest level). Should I go complaining to Apple or do I just need different software? I've only had my mac book since August 2011. The battery dies in 2 to 3 hours with some web surfing (little video play) and photo editing etc. I really don't feel like taking my computer all the way to the apple store to wait there for 5 hours to hear that I need to call someone blah blah blah. Any advice? (BTW Safari hasn't been working since I last updated my mac, WHYYYY?)

emsavage1127 wrote:
Should I go complaining to Apple or do I just need different software?
emsavage1127 wrote:
I really don't feel like taking my computer all the way to the apple store to wait there for 5 hours to hear that I need to call someone blah blah blah.
Make an appointment at the genius bar, that way, you wont have to wait. http://www.apple.com/retail/geniusbar/

Macro-Caculation values lowest level

Similar Messages

Maybe you are looking for