Lowest Level in Prod Hierarchy
Hi All,
I have a situation wherein i have to get to the lowest level match of the product hirearchy for the best fit.
I have a custom table which maintains Prod. Hier as part of the Key. I need to get down to the best fit of that to the lowest level possible.
Any sample code appreciated..!
Thanks in advance..!
More Clarification on the situation:Ineed to get to the lowest level match of the product hirearchy for the best fit. I have a table which has Prod. Hier, Matnr, and Platform.
I have to check if a particular material Number exists in this Table, If yes then take that corresponding platform. If material doesn't exist then i have to check for the Best possible fit to the lowest level on the Prod. hier and take that corresponding platform.
let's say the table is something like this.
Prod. Hier Matnr Platform
5012EF 010001 ABC
5012 BCD
50 DEF
Now, if i have a material 010001 with Prod. Hier 5012EF: Then i should collect platform ABC.
If i have a material 012120 with Prod. Hier 5012DE : then i should collect platform BCD, as it is the best possible lowest level fit.
Hope i made this clear..!
Thanks in advance.
Similar Messages
-
Hierarchy drill down issue at the lowest level
Hi,
In OBIEE 11.1.1.5 I face an issue with drill down to lowest level of presentation hierarchy (expanded by "+" in report). It happens only for combination of 2 dimensions presentation hierarchies in analytics report (parent-child organizational structure + level based product categorization). Aggregated date comes from OLAP but lowest level product information comes from relational database and this details are not displayed.
First I drill to particular sales rep in organizational structure. Then for that sales rep I need to drill down product hierarchy and it works except lowest level of details. At the lowest level of product hierarchy, query sent to database (I have it from logs) return proper results (checked directly in db) but report behaves the way like there are no details at the lowest level and product details are not displayed.
Both (Organizational structure, Product) dimension presentation hierarchies works ok at all levels when used separately. Also product hierarchy works well at all levels (including OLAP->relational drill) when used togather with other level-based hierarchies in subject area.
I am wondering what I could have done wrong...
Advices are very welcome!Hierarchy keys are set properly and "use for display" is checked.
Dimension presentation hierarchies does not work only when I use particular two hierarchies togather in one report table. When each of hierarchies is displayed separately it works ok. -
Cannot drill down from 2nd lowest level to lowest level of hierarchy
In my item master hierarchy, I cannot drill down from the 2nd lowest level (Product Class) to the lowest level (Item Detail).
When I add another level between these 2 levels, then I can drill down from Product Class to this new level, but I cannot drill down from this new level to the lowest level.
Also, if I set the preferred drill path at any level to drill down to the lowest level, it instead drills down to next level down intead of of drilling to the lowest level.
Any thoughts as to why I would not be able to drill to the lowest level of this hierarchy?
Thanks,
TravisOK, next check, any security in place on the presentation columns which would make the lowest level column unavailable to the user account?
Are you running the report as Administrator? -
Modify Chart Legend Data Behaviour to show only lowest level of drill
I have a chart with a legend in OBIEE 11g.
When I click on chart data or legend it drills to the next level of the hierarchy which is what I want.
However the legend show all levels of the hierarchy in the legend data like this:
"Level 1"."Level 2"."Level 3".
This is very cluttered and redundant as Level 1 & Level 2 are the same for all items.
What I want is that it only shows the lowest level of a hierarchy that has been drilled to eg.
"Level 3"
Is it possible to do this? I've already tried the user guide, on this forum or on google search.
Thanks in advance.Not sure its doable out the box,
You could hack the popchart JS files I guess, John Minkjan's blog describes some changes , in particular on mouse-hover activity but they should show where to start. -
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
PeterHi 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 -
Hide the last level of a hierarchy in bex
HI experts,
In a query I use a hierarchy based on 0account (characteristic based hierarchy, every node is also an account...)only leaves have figures in the cube (meaning no direct posting on nodes).
This hierarchy doesn't have flat / equal levels, and final accounts are sometimes located on level X, sometimes on level X+1 etc...therefore, I can't use the standard fonctionnality "expand to level X"
see below a simple exemple
(in fact my hierarchy contain more than 10 levels):
level1..|..level2..|..level3
..node 1-1
.........|.node 1-2 ("R"account)
.......................|.<b>account</b>
..node 2-1 ("R"account)
.........|.<b>account</b>
My users want to be able to simply navigate in the hierarchy on specific nodes(which have specific properties through the usage of an navigational attribute used on my 0account characteristic), whitout having to expand to the last level: example the "R" level wich is the level before. Again, this R level resides in different levels of my hierarchy.
So I have to find a way to stop the expand of the hierarchy to this specific level, hide the levels below(account), but include the amount of the lower levels in this specific specified level ("R").
If you have any ideas/clues or suggestions on how to resolve this issue (navigational attribute, exits, restricted key figures, hidden columns...)...this would really be much appreciated.
thanks a lot!
Ps: I work on BW 3.5
Message was edited by: Agathe LE LAMERHi Agathe LE LAMER
I know this thread is a little old now, but I would be interested to know if you had found a way of doing this. I am also trying to supress the lowest level in a hierarchy which are not all the same levels.
Thanks
Ben -
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.... -
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,
Andreaexpac 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) -
RETRIEVE LOWEST LEVEL OF HIERARCHY (OMB+)
Hi all,
How can I get the name of lowest level in the primary hierarchy of a dimension through OMB+?
OMBRETRIEVE DIMENSION_TABLE 'SALES_REP' GET LEVELS
gives me following result:
LOCATION COUNTRY EMPLOYEE REGION DEPARTMENT
while the original hierarchy is like
REGION COUNTRY LOCATION DEPARTMENT EMPLOYEE
how can i retrieve 'EMPLOYEE' level?
regards,
Zahid NaseerHello Zahid,
You have to specify which hierarchy to use to get levels sorted top to bottom, eg:
OMBRETRIEVE DIMENSION_TABLE 'SALES_REP' HIERARCHY 'MY_HIER' GET LEVELS
will probably give you the expected result.
Regards, Hans Henrik -
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,
GaneshThere 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 -
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 RagnarRangar,
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 -
Promotion planning and lowest level KF
Hai,
The promotion key figure has to be the lowest level of detail, which means the KF has to be the lowest in the hierarchy. This means, I can only assign promotions at the lowest level?
For example, a product called DOW white color soaps and a group level called DOW soaps. So as per the promotion planning, I can only set promotions at the DOW white color soaps and not at the group level of DOW soaps? is that true? What if I have a case that I have to specify a promotion at group.
Thank you.Hi Vishu ,
Firstly let me clear you that Promotion Key figure is the key figure in which the data for the promotion is to be stored and the Promotion level is the characteristic at which level the promotion is maintained ,this may be the Locaion or the Product .Yes you need to assign promotion to the lowest level but this does not mean that you can not add promotions at higher level like product grp or Brand .
In promotion base you can define Characteristics (Grp/Brand etc) on which you want to plan promotion.
For more clarification go thro.
<a href="http://help.sap.com/saphelp_scm40/helpdata/en/0d/429ba838ee11d3982b0000e8a49608/frameset.htm">Creating a Promotion</a>[url
Regds //Digs... -
Lowest Level Call X64 and what need to be preserved?
Hi,
Our team- recently had a problem regarding a lowest level function in x64 bit machines in Windows - and what needs to be preserved in order to safely handle the event and pass it on to Windows Kernel. I am not too experienced in handling functions this deep
into Usermode (Ring3).
Can someone please answer my doubts?
ThanksHi,
The lowest level function which runs into x64 bit mode is Wow64ServicesEx
it is 4 layers\level below X86SwitchTo64BitMode (can be found in FS[0xC0] call hierarchy as it passes on to while changing it's code segment to 0x33 CpupReturnFromSimulatedCode,
then it passes on to TurboDispatchJumpAddressEnd finally jumping to
Wow64ServicesEx.
As for the 2nd sub-question, you need to preserve EAX register and ESP register because EAX, contains the caller function ID for example
NtOpenProcess's ID is 23h. As shown in the first few bytes of it's prologue:
mov eax, 23h
xor ecx, ecx
lea edx, DWORD PTR SS:[esp+0x04]
If you understand the assembly above you can see that the eax is being filled with it's ID 23h, as for esp it is being filled with the parameters, then it will be passed to the next call in the Windows Call hierarchy. As all functions need parameters you
need to save EAX, ESP you can use PUSPAD and POPAD combinations in the handle callback.
Regards Rohan Vijjhalwar -
Prod.hierarchy field in basic data
hi
can anybody please explain me what is a use of prod.hierarchy field in basic data tab page in material master and how to create these hierarchy levels
i have gone through field help but not able to understand
client is asking about this field
please help me out
its urgentHi
This product hierarchy are used mainly by SD side.
You also post this in SD forum
Regards
Ranga -
Why I can not find field:Level in Project Hierarchy in BAPI_BUS2054_NEW?
Dear experts,
Why I can not find the field of "Level in Project Hierarchy" in structure BAPI_BUS2054_NEW?
I only define the data to upload wbs:
PROJECT DEFINITION
PROJECT DESCRIPTION
PROJECT PROFILE
WBS Element
WBS description
Can you tell me which fields must to upload?
Looking forward to your reply.
Many thanks.
MerryzhangAnyone can help me ?I need the field "Level" in BAPI_BUS2054_NEW,But I can not find it.
Maybe you are looking for
-
Is there a way that I can reset my iphone 5 to select "Restore from iTunes Backup" so that I can have all my data from my old phone to be transferred to the new one? thanks
-
Too low resolution on a picture
I am trying to create a holiday card on a website and am told the photo has too low resolution. They said I can change this on my computer. Can I?????
-
Add in to view 360 degree Panoramas in PSE
Does anyone know the add on for PSE to view pannos in different formats ie jpg or png
-
Huge Number of Deps when Upgrading KDE packages from 4.14 to 14.12
Hi, I know the KDE upgrade issue is "flavor of the day" at the moment and I have read other threads on it; but so far have not found info which applies to my situation. Note: I only use a FEW KDE apps like Krusader, Yakuake, Konsole, Kcalc and do NOT
-
How much room does Time Machine take
I have a Macbook Pro with 120GB HD. I wanted to know how big of an external HD I need for Time Machine. I also want to know if I can use it as a HD for large files (imovies) and have that separate from the Time Machine application.