Level Based vs. Value Based hier: advantages, disadvantages and limitations

Could someone give an overview about the advantages, disadvantages and limitations when comparing OLAP Level to Value based hierarchies?
Thanks,
Marcio

OLAP can handle both types of hierarchies. No performance advantage using one over the other (while loading cube or querying).
If you are "pushing" dimensional-security inside OLAP, in that case also it does not matter.
Cube-based MVs (with query-rewrite) can only be created if the hierarchies are level-based. Are you going to need that?
Generally there are other "non-olap" factors:
(#1). Which reporting tool will be used. Does it provide better reporting capabilities if the source is parent-child or level-based?
(#2). Are there any reporting requirements that will need "level" information when selecting data.
(#3). Are there are any security requirements that will be handled in "reporting-layer" which will need level-based information.
Although in case of (#1) and (#2), you can "expose" an olap's parent-child hierarchy as "level-based" hierarchy to the reporting tool using internal GID (grouping-id) information.
OBIEE 11.1.1.5 (and future versions) works well with OLAP metadata, and with any type of hierarchy in olap.
For other reporting tools, you have to see what features are available.
In short, its the source system, the reporting tool and the reporting requirements that will dictate what type of hierarchy should be stored in OLAP.

Similar Messages

Value based hierarchies, Skip Level Hierarchies

Hello,
I need to create hierarchy based on column value , Please give me some details on implementing value based hierarchies and skip level hierarchies in obiee 10.1.3.
Thank you

With 10.3 i do not think we have a inbuilt solution to build value based hierarchies, you have to flatten the hierarchy and build a level based hierarchy.
OBIEE 11g has value based hierarchies feature.
refer this one for 11g.
http://sandybi.wordpress.com/2010/08/17/hierarchies-in-obiee-11g-part-1/
- Madan
Edited by: Madan Thota on Sep 14, 2010 11:15 AM

Is there any process to convert an value-based hierarchy to level-based one

Hi Experts,
Is there any automated or manual process to convert the value-based hierarchy to the level-based hierarchy.
Thanks
VR

Using SQL's "CONNECT BY" clause and PL/SQL programming we can convert a value-based hierarchy to a level based. I have not done this myself but I am positive we can get it to work.

Preaggregation across value based hierarchy dimension in 11g

Hi All,
I have created a cube with 6 dimensions in olap 11g. One of those six dimensions has only one hierarchy which is value based hierarchy. I have chosen level based aggregation as I know at what levels exactly users are going to query. When I was going through the dimensions to choose levels to preaggregate I noticed there were no options available for my value based hierarchy dimension ( I could see "all" option for the same case in 10g) then I tried to look for definitions of underlying objects just to make sure it will preaggregate data across my value based hierarchy dimension.
I found value set corresponding to my value based hierarchy dimension in <CUBE NAME>SOLVEAGGMAP object , which AWM uses to decide which dimension values to preaggregate but if I do rpr on that value set (rp r<CUBE NAME>SOLVE<DIMENSION NAME>_PVSET) it shows NA so my question is can I pre aggregate across value based hierarchy dimension in olap 11g?
Olap Version: 11.2.0.1
AWM version: 11.2.0.1
Thanks

Even if you know exactly which levels your users will query, percent based precompute (e.g. 30%) may still be faster in practice because queries are returned using 'sparse looping' instead of 'dense looping'. This was the single biggest performance advantage of 11g over 10g.
But if you still want to use level based precompute, then you should look at the XML template for the cube (as saved by AWM, for example). In it you should find something called PrecomputeCondition. This defines the set of members that are precomputed. Here is an example I just created using the GLOBAL schema
<PrecomputeCondition>
<![CDATA[
"TIME" LEVELS ("TIME"."MONTH", "TIME".CALENDAR_QUARTER, "TIME".CALENDAR_YEAR),
CHANNEL LEVELS (CHANNEL.TOTAL_CHANNEL, CHANNEL.CHANNEL),
CUSTOMER LEVELS (CUSTOMER.MARKET_SEGMENT, CUSTOMER.REGION, CUSTOMER.SHIP_TO),
PRODUCT LEVELS (PRODUCT.CLASS, PRODUCT.FAMILY, PRODUCT.ITEM)]]>
</PrecomputeCondition>The PrecomputeCondition is also visible through the USER_CUBES view.
SELECT PRECOMPUTE_CONDITION
FROM USER_CUBES
WHERE CUBE_NAME = 'MY_CUBE';You can hand modify this condition in the XML to specify an alternative 'non level based' precompute condition for any dimension. For example, if you define an attribute named 'SHOULD_PRECOMPUTE' on your PRODUCT dimension that is 1 for members to be precomputed and 0 for all others, then you can change the condition as follows.
<PrecomputeCondition>
<![CDATA[
"TIME" LEVELS ("TIME"."MONTH", "TIME".CALENDAR_QUARTER, "TIME".CALENDAR_YEAR),
CHANNEL LEVELS (CHANNEL.TOTAL_CHANNEL, CHANNEL.CHANNEL),
CUSTOMER LEVELS (CUSTOMER.MARKET_SEGMENT, CUSTOMER.REGION, CUSTOMER.SHIP_TO),
PRODUCT WHERE PRODUCT.SHOULD_PRECOMPUTE = 1]]>
</PrecomputeCondition>If you recreate the cube from the XML with this condition, then the PVSET valueset you discovered should contain all dimension members for which the attribute value is 1. This gives you complete control over what is precomputed. Note that AWM doesn't support this form of condition, so it won't show up if you go to the Precompute tab, but it is valid for the server. The PL/SQL below will modify the PrecomputeCondition (for the cube named MYCUBE) without going through AWM.
begin
dbms_cube.import_xml(q'!
<Metadata
Version="1.3"
MinimumDatabaseVersion="11.2.0.2">
<Cube Name="MY_CUBE">
 <Organization>
 <AWCubeOrganization>
 <PrecomputeCondition>
 <![CDATA[
 "TIME" LEVELS ("TIME"."MONTH","TIME".CALENDAR_QUARTER, "TIME".CALENDAR_YEAR),
 CHANNEL LEVELS (CHANNEL.TOTAL_CHANNEL,CHANNEL.CHANNEL),
 CUSTOMER LEVELS (CUSTOMER.MARKET_SEGMENT,CUSTOMER.REGION,CUSTOMER.SHIP_TO),
 PRODUCT WHERE PRODUCT.SHOULD_PRECOMPUTE = 1]]>
 </PrecomputeCondition>
 </AWCubeOrganization>
 </Organization>
</Cube>
</Metadata>
end;
/

Problem when querying OLAP for Value based hierarchy

Hi I have problem when querying OLAP for value based hierarchy , for level based dimension it work fine
the strange part is if I only put one value, it will work perfectly
for example if I put only 1 value for that value base hierarchy like CF_HIER::426362, then it will get the correct value for that id 426362
but if I put multiple value to the list
CF_HIER::426362
CF_HIER::424470
CF_HIER::429073
CF_HIER::424230
then only some value will come out correctly, some of them will be 0, I wonder why because if I query using each value, then it show correct value
for multiple value usually only the top in hirarchy give correct value, but the leaf will give 0, but if I query only the leaf, the leaf will give correct value
this problem only happen for my value based hierarchy, for the level based hierarchy it work fine both for each value or multiple value in the list
this is the code how I guery
////the "elementIdList" is where the value is (CF_HIER::426362,CF_HIER::424470,CF_HIER::429073,CF_HIER::424230), if I only put single value in this list the query work fine, but if I put multiple value then some value give correct result, some will give 0
String[] elementIdArr = new String[elementIdList.size()];
          int i = 0;
          for (Long elementId: elementIdList) {
               String elementIdStr ="";
               if (hierarchy instanceof MdmLevelHierarchy)
                    elementIdStr = hierarchy.getName()+dimension.getValueSeparationString()+
                                        level.getName()+dimension.getValueSeparationString()+
                                        level.getName()+"_"+elementId;
               else
                    elementIdStr = hierarchy.getName()+dimension.getValueSeparationString()+
                                        elementId;
               elementIdArr[i++] = elementIdStr;
          Source myList = dp.createListSource(elementIdArr);
          result = hierarchy.getSource().selectValues(myList);
     Source joinedSource = measure.getSource();
          joinedSource = joinedSource.join(result );
is there any suggestion where I'm doing wrong?or is it different between querying value based hier with level based hier?
thanks

Hi I have problem when querying OLAP for value based hierarchy , for level based dimension it work fine
the strange part is if I only put one value, it will work perfectly
for example if I put only 1 value for that value base hierarchy like CF_HIER::426362, then it will get the correct value for that id 426362
but if I put multiple value to the list
CF_HIER::426362
CF_HIER::424470
CF_HIER::429073
CF_HIER::424230
then only some value will come out correctly, some of them will be 0, I wonder why because if I query using each value, then it show correct value
for multiple value usually only the top in hirarchy give correct value, but the leaf will give 0, but if I query only the leaf, the leaf will give correct value
this problem only happen for my value based hierarchy, for the level based hierarchy it work fine both for each value or multiple value in the list
this is the code how I guery
////the "elementIdList" is where the value is (CF_HIER::426362,CF_HIER::424470,CF_HIER::429073,CF_HIER::424230), if I only put single value in this list the query work fine, but if I put multiple value then some value give correct result, some will give 0
String[] elementIdArr = new String[elementIdList.size()];
          int i = 0;
          for (Long elementId: elementIdList) {
               String elementIdStr ="";
               if (hierarchy instanceof MdmLevelHierarchy)
                    elementIdStr = hierarchy.getName()+dimension.getValueSeparationString()+
                                        level.getName()+dimension.getValueSeparationString()+
                                        level.getName()+"_"+elementId;
               else
                    elementIdStr = hierarchy.getName()+dimension.getValueSeparationString()+
                                        elementId;
               elementIdArr[i++] = elementIdStr;
          Source myList = dp.createListSource(elementIdArr);
          result = hierarchy.getSource().selectValues(myList);
     Source joinedSource = measure.getSource();
          joinedSource = joinedSource.join(result );
is there any suggestion where I'm doing wrong?or is it different between querying value based hier with level based hier?
thanks

Security for value based hierarchy + OLAP

Hi,
I am using row-level security mechanism described here: http://www.rittmanmead.com/2012/03/obiee-11g-security-week-row-level-security/
It works well for level based hierarchies... but is there a way to apply it to value based OLAP hierarchy in OBIEE 11.1.1.6?
My case is:
- I have parent-child value based hierarchy representing management structure with various depth.
- of course facts are always linked to leaf members of hierarchy
- I need to apply security at different levels. E.g. Office manager should have access to one/multiple offices information (basically all employees he manage currently + his previous office before he was moved)
- In report I display presentation hierarchy that starts at country level and then manager drill to his offices
- At country level, manager should see a measure aggregate only for his offices (not whole country)
In relational database there is no problem:
- I follow rittman blog
- create session variable that store list of all leaf members of hierarchy (employees) managed by manager
- with OBIEE "Manage"->"Identity" I apply filter on fact table and get right measure aggregates at all levels of hierarchy
Issue for OLAP:
- with OBIEE "Manage"->"Identity" I apply filter on OLAP value based hierarchy
- in case of filter "MY_BMM"."Org Str"."Org Str Key" = VALUEOF(NQ_SESSION."LEAFS_LIST") -> when manager include hierarchy column to report there are no results because hierarchy starts at country level and he have no access to country data
- to workaround it I tried: "MY_BMM"."Org Str"."Org Str Key" = VALUEOF(NQ_SESSION."LEAFS_LIST_AND_ALL_ANCESTORS") -> manager can see all aggregates at country level because he have access to country, and OLAP just use country level aggregate
- IsDescendant("MY_BMM"."Org Str" , VALUEOF(NQ_SESSION."OFFICE_ID")) will work only for single office as we can not use row wise variables here
One solution I can imagine is to create additional level based dimension that have only 2 levels: "All"->"Org Str Leaf". Then apply filter on this "artifitial" dimension. It is not perfect solution to duplicate dimensions only for security purposes... that's why I ask you for advice if you know better way?
Regards,
mudi

Here is an example, how to set security in OBIEE 11.1.1.5 (or future versions) against Oracle OLAP dimensions.
*(1). Create the Oracle OLAP Hierarchy Descendant View against Value-based hierarchy*
These views return a row for each ancestor-descendent relationship in the hierarchy. As you can see how easy it is.
CREATE OR REPLACE VIEW DEPT_DESCENDANTS
AS
SELECT 'DEPT' "DIMENSION", 'DEPTHIER' "HIER", ancestor, descendant
FROM TABLE(OLAP_TABLE('BAWOLAP.BNSOLAP DURATION QUERY', null, 'LIMIT DEPT_HIERLIST TO 'DEPTHIER''',
'DMNS DESCENDANT AS VARCHAR2(60) FROM DEPT
DMNS GID_VAL AS NUMBER FROM ___AW_GID_DIMENSION
MSR ANCESTOR AS VARCHAR2(60) FROM DEPT_FAMILYRELVAL'
where ancestor is not null
*(2). Create the User ACL Tables and Populate with Data*
Create an Access Control list test table by user and Dept. Later this will be populated with production data.
create table user_dept_acls
username varchar2(30),
dept varchar2(60)
insert into user_dept_acls(username, dept) values ('user1', 'GWM');
insert into user_dept_acls(username, dept) values ('user1', 'GT');
insert into user_dept_acls(username, dept) values ('user1', 'SC');
insert into user_dept_acls(username, dept) values ('user2', 'GWM');
insert into user_dept_acls(username, dept) values ('user2', 'GT');
insert into user_dept_acls(username, dept) values ('user3', 'SC');
commit;
*(3). Create an Init Block Connection Pool*
Oracle BI EE requires a separate Connect Pool for Init blocks. It does not allow the default query connection pool to be reused for init blocks. So, we need to create a new init block.
*(4). Create the ACL Session Variables*
These session variables hold the list of all members that the user may access.
Example Session Variable: DEPT_ACL
Init Block: "Init DEPT_ACL"
SQL:
select 'DEPT_ACL', account from user_DEPT_acls where username = ':USER'
union all
select 'DEPT_ACL', descendant
from DEPT_descendants
where ancestor in (select account from user_DEPT_acls where username = ':USER')
union all
select 'DEPT_ACL', ancestor
from DEPT_descendants
where descendant in (select account from user_DEPT_acls where username = ':USER')
The first query block of the init block SQL just selects the members explicitly entered into the ACL table. The second block selects all the descendants of those members from the descendants view. The third block selects all the ancestors to ensure that the user has access to all the members in the drill path starting from the root member.
Make sure that row-wise initialization is checked in the Variable Target section of the init block.
*(5). Add the Data Filters*
In our test case we assigned the data filters to the BIAuthor role, but the filters should be added to whatever role makes the most sense.
Data filter on "BNSGL"."Department":
"BNSGL"."Department"."Dept" = VALUEOF(NQ_SESSION."DEPT_ACL")
*(6). Log in as a Normal User and Query the Hierarchy*
The user can only see to the members to which they are granted access in the ACL table plus all ancestors and descendants of those members.
Drill down to the bottom of the hierarchy.
*(7). Look at the Query Log*
In the nqquery.log we see that the session variable is expanded into an IN list in the physical SQL query. The BI Server breaks the IN list into two IN lists to avoid the Oracle SQL limit of 1,000 items per IN list.
Edited by: Nasar Ali-Khan on Jul 2, 2012 8:14 AM

Value based hierarchy 11g question

Hi,
in my BMM i've created a level based hierarchy composed of two levels: TOTAL and Audiologist
Total level is setted as Grand Total level and doesn't have logical columns.
At audiologist level insted i drag and drop two logical columns: Audiologist Code and Audiologist Name
Then i created two keys.
First Key: Audiologist Code - Use to display: None
Second Key: Audiologist Code and Audiologist Name - Use to display : YES
Graphically my hierarchy is as follow:
Total-----
Audiologist
Audiologist Code
Audiologist Name
Now i would like that if i drill down Total appear simultaneously two columns: Audiologist Code and Audiologist Name.
Is it possible? I remember that in 10 it was.
It's quite urgent.
Thanks

Based on my experience of OWB10gR2 the option to create a "Value Based" hierarchy is only enabled if you create an AW based OLAP model. If you want to create a ROLAP model then I do not think this is possible.
Question is why create a ROLAP model when you could get better performance and more powerful analytical features by using a multidimensional model within an analytic workspace.
Keith

Query on DSO, KF value +/- based on flag value in DSO

Hi Experts,
I have a query on DSO and it is running fine.
Current Query output :
CHAR1 | CHAR2 | KF1
1111       S            100
1111       H            100
I want to put + or - sign for KF based on value of CHAR 2 (Flag) in query output.
So
Desired Query output :
CHAR1 | CHAR2 | KF1
1111       S            -100
1111       H             100
I can Add CHAR3 in DSO and based on CHAR2 value CHAR3 will store +1 or -1. Add it can be used to get + or -Value of KF using CKF.
But without doing it (CHAR3), can I do it directly at query level ?
Regards,
Vinod

Try this:
RKF1: KF restricted on S
RKF2: KF restricted on H
CKF: (-1)*RKF1 + RKF2
This should give you what you are looking for.
Regards,
Gaurav

Populate 2nd combo box based on value selected in 1st combo box

I am still using Acrobat 6 though I may be upgrading soon to Acrobat 8. I have a form with two combo boxes, the first "state" has values of MN and WI. Based on which value the user picks I would like to populate a "county" combo box with lists of counties that we deal with.
Thanks,
Gene

One can set the option and export value using an arry: // document level script // Master List of Lists // Each entry in this object listeral is the name of a State //Manually enter the State Names into the state field combo box // The associated value is the item list, where each item is a name value pair, [<County> and [county code, zip code]] // state: ["county name", ["county code", "zip code"]] var oStateNames = {MN: [["-", ["", ""] ], ["St. Louis", ["MNStl", "55001"] ], ["Carlton", ["MNSCrl", "55002"] ], ["Pine", ["MNPin", "55003"] ], ["Cook", ["MNCok", "55004"] ] ], WI: [["-", [" ", " "] ], ["Douglas", ["WIDou", "55005"] ] , ["Bayfield", ["WIBay", "55006"] ], ["Burnette", ["WIBur", "55007"] ], ["Ashland", ["WIAsh", "55008"] ] ] }; //SetCountyEntries() on keystroke entry in state field function SetCountyEntries() { if(event.willCommit) { // Get the new counties list from the Master List // Since the selection is being committed, // event.value contains the State name var lst = oStateNames[event.value]; // Clear the county list if there are no counties for the selected state this.getField("ee.address.county").clearItems(); this.resetForm(["ee.address.code", "ee.address.zip"]); if( (lst != null) && (lst.length > 0) ) this.getField("ee.address.county").setItems(lst); // set opiton and export value } } // end document level script For the combo box "ee.address.county" one can create an array from the export value to populate the county code and zip code // custom keystroke for county combo box if(event.willCommit & event.value != "") { // split county and zip codes var aCodes = this.getField(event.target.name).value.split(","); this.getField("ee.address.code").value = aCodes[0]; this.getField("ee.address.zip").value = aCodes[1]; } // end custom key stroke code

Populate Value B based on Value A in Web UI

Hi Friends,
I have requirement to populate a field value based on other field value.
I have a view and it consist 2 context nodes.
When User enters the value in field A ( context node A ), we need to populate the field B ( Context node B ). But the main thing is that get property method of field B is triggering before then get property method of B.
Kindly suggest how do we achive this.
Regards,
Narendra Goyal

As mentioned before the DO_PREPARE_OUTPUT is a place that will work.
A little bit more on the background:
Do not code such stuff in the SET_ methods, as they will be called in the order of the data that is send to the server in the request. You noticed now that GET_A was called after GET_B, but it could change any time depending on the placement of fields on the view. Have a look at the DO_HANDLE_DATA for the FORM_FIELDS.
An approach I like to take for more time consuming operations on field change:
Create an event on context node CN1 and register the view controller to react on it. Then in the SET_A fire the event populating the new value as an input parameter.
Now the handler in the view controller can set a global variable containing the passed value.
In the DO_PREPARE_OUTPUT I can simply check if the global variable is set and directly work on it. Then clear it.
It is more work then the method described before, which is really fine and I have used it lots of times. The advantage is that you do less access for fetching the value from the context node every roundtrip.
cheers Carsten

Parent-child hierarchy (Value based hierarchy)

As anyone created a parent-child hierarchy using Oracle Warehouse Builder or Analytic Workspace Manager. I am using Oracle 10g Rel2 (and AWM) and OWB 10g Rel2.
The values in the dimension table defines the hierarchy.
I don't see an option of creating a value-based hierarchy in OWB though it is mentioned that it supports this particular hierarchy.
In AWM, I am able to create the hierarchy but when I try to view the data in the dimension it gives an error BIB-9531 Invalid hierarchy specified.
Can you please let me know if I am missing something.
Thanks a lot in advance!
Regards,
Maruthi

I've done some work with this, and it hasn't been easy going. There is no built-in ability to form a hierarchy of measure columns, at least nothing that can be predefined as the drill for a fact column. For example: I have 220 details of expense that have an exact arrangement with 5 levels and subtotals. Besides the expense detail there are say 4 dimensions, so the expense detail would be the 5th dimension. I have both arrangements in my rpd: 4D and 5D. They can be used together or separately. The 4D basically has 1000's of measures and there is no relationship between them besides the display arrangement in Answers. The 5D has a 5 column dimension that can drill the expense column from Total_Expense down to the 220 rows of detail expense.

Value based hierarchy (parent-child)

Does anybody have any experience in modeling a parent-child dimension ( value based hierarchy instead of level based ) in OBIEE?
Swapan.

I've done some work with this, and it hasn't been easy going. There is no built-in ability to form a hierarchy of measure columns, at least nothing that can be predefined as the drill for a fact column. For example: I have 220 details of expense that have an exact arrangement with 5 levels and subtotals. Besides the expense detail there are say 4 dimensions, so the expense detail would be the 5th dimension. I have both arrangements in my rpd: 4D and 5D. They can be used together or separately. The 4D basically has 1000's of measures and there is no relationship between them besides the display arrangement in Answers. The 5D has a 5 column dimension that can drill the expense column from Total_Expense down to the 220 rows of detail expense.

Value based Hierarchies

Hello,
Has anyone created a parent-child hierarchy using Oracle Warehouse Builder or Analytic Workspace Manager. I am using Oracle 10g Rel2 (and AWM) and OWB 10g Rel2.
The values in the dimension table defines the hierarchy.
I don't see an option of creating a value-based hierarchy in OWB though it is mentioned that it supports this particular hierarchy.
In AWM, I am able to create the hierarchy but when I try to view the data in the dimension it gives an error BIB-9531 Invalid hierarchy specified.
Can you please let me know if I am missing something.
Thanks a lot in advance!
Regards,
Maruthi

To create a value based hierarchy:
define the storage as MOLAP, as a minimum create 2 attributes one for the dimension member (define as business in Identifier column), one for the parent member referenece (define as parent in Identifier column), the hierarchy will have no levels. If you add this dimension into a map, you should have a mapping port for both the dimension member and the parent reference. The dimension will use 'Use natural keys from data source'.
There is an expert for simplifying some of this, not sure on when it will be made available on OTN, it drives the creation of the dimensional objects from tables/views etc..

Problems with value-based hierarchies in Oracle 11gR2

Hello,
I have the following problem:
I want to cereate a dimension with 2 hierarchies.
These hierarchies have to be value-based.
It's no problem to fill and display one of them, but when I fill both and try to display them, at the lowest level, the parent-child relevancy is now incorrect.
Let's display this in OLAP Worksheet for Cube Type OLAP 11g :
lcolwidth=20
rpr down nim_2 w 25 NIM_2_PARENTREL
                          ------------------NIM_2_PARENTREL------------------
                          ------------------NIM_2_HIERLIST-------------------
NIM_2                                KON                       AGT
L1_Total_AGT_A            NA                        NA
L1_Total_KONZ_K           NA                        NA
L2_AGT_A_A                NA                        L1_Total_AGT_A
L2_AGT_B_A                NA                        L1_Total_AGT_A
L2_AGT_C_A                NA                        L1_Total_AGT_A
L2_KONZ_1_K               L1_Total_KONZ_K           NA
L2_KONZ_2_K               L1_Total_KONZ_K           NA
L3_100_A                  NA                        L2_AGT_A_A
L3_100_K                  L2_KONZ_1_K               NA
L3_200_A                  NA                        L2_AGT_B_A
L3_200_K                  L2_KONZ_1_K               NA
L3_300_A                  NA                        L2_AGT_C_A
L3_300_K                  L2_KONZ_2_K               NA
L4_101_A                  NA                        L3_100_A
L4_101_K                  L3_100_K                  NA
L4_301_A                  NA                        L3_300_A
L4_301_K                  L3_300_K                  NA
L5_302_A                  NA                        L4_301_A
L5_302_K                  L4_301_K                  NA
100                       NA                        L3_100_A
101                       L4_101_K                  NA
102                       NA                        L4_101_A
200                       NA                        L3_200_A
201                       L3_200_K                  NA
300                       L3_300_K                  NA
301                       NA                        L4_301_A
302                       NA                        L5_302_A
303                       NA                        L5_302_A
304                       NA                        L5_302_AAs you see, the lowest level items are only connectet with one of the hierachies, instead connected with both. (100, 101, e.g)
If I build the same dimension in a 10g Cube, the result is now correct.
Let's display this in OLAP Worksheet for Cube Type OLAP 10g :
lcolwidth=20
rpr down nim w 25 NIM_PARENTREL
                     -------------------NIM_PARENTREL-------------------
                     -------------------NIM_HIERLIST--------------------
NIM                             AGT                       KON
L1_Total_AGT_A       NA                        NA
L1_Total_KONZ_K      NA                        NA
L2_AGT_A_A           L1_Total_AGT_A            NA
L2_AGT_B_A           L1_Total_AGT_A            NA
L2_AGT_C_A           L1_Total_AGT_A            NA
L2_KONZ_1_K          NA                        L1_Total_KONZ_K
L2_KONZ_2_K          NA                        L1_Total_KONZ_K
L3_100_A             L2_AGT_A_A                NA
L3_100_K             NA                        L2_KONZ_1_K
L3_200_A             L2_AGT_B_A                NA
L3_200_K             NA                        L2_KONZ_1_K
L3_300_A             L2_AGT_C_A                NA
L3_300_K             NA                        L2_KONZ_2_K
L4_101_A             L3_100_A                  NA
L4_101_K             NA                        L3_100_K
L4_301_A             L3_300_A                  NA
L4_301_K             NA                        L3_300_K
L5_302_A             L4_301_A                  NA
L5_302_K             NA                        L4_301_K
100                  L3_100_A                  L3_100_K
101                  L4_101_A                  L4_101_K
102                  L4_101_A                  L4_101_K
200                  L3_200_A                  L3_200_K
201                  L3_200_A                  L3_200_K
300                  L3_300_A                  L3_300_K
301                  L4_301_A                  L4_301_K
303                  L5_302_A                  L5_302_K
304                  L5_302_A                  L5_302_K
302                  L5_302_A                  L5_302_K-----
We are using the latest Version of AWM: Version 11.2.0.1.0A
Database:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
PL/SQL Release 11.2.0.1.0 - Production
"CORE     11.2.0.1.0     Production"
TNS for IBM/AIX RISC System/6000: Version 11.2.0.1.0 - Production
NLSRTL Version 11.2.0.1.0 - Production
Thank you verry much for any help.

11.2.0.2 for AIX was announced in October 2010. See DOC ID 1249584.1
What is being announced?
We are pleased announce the October 19, 2010 release of Oracle Database 11g Release 2 Patchset 1 (11.2.0.2) on HP-UX > Itanium and IBM AIX on POWER Systems.Patchset 10098816
Description 11.2.0.2.0 PATCH SET FOR ORACLE DATABASE SERVER
Product Oracle Database Family
I have looked, but I cannot find a formal bug for this problem. My hunch is that it was fixed as a side effect of other changes, and I know there were several in this area. My simple test case did work in 11.2.0.2, so I hope it is all fixed. But feel free to enter an SR if you want. (If you mention my name in the SR then support should contact me.) You should certainly do this if moving on to 11.2.0.2 does not resolve the issue.

Calculate BED & relevant duties based on value @ PO for a particular vendor

Dear experts,
Is it possible to calculate excise duties and other relevant pricing elements at purchase order level based on VALUE and capture the same (part1 - MIGO and part11-J1IEX) for a PARTICULAR VENDOR INVOICE?
The business process is like this. First we r receiving invoice from vendor and based on that we r creating PO and do other transaction activities.
We r using ECC6.we r maintaining tax details through tax codes based on percentage and pricing procedure(TAXINJ) is activated and pricing elements are managed through cond.types(gross is value base and others are managed by %).
I find difficulty to capture excise data (cin) through % in j1iex and manual value adjustment is tedious process for multiple line items.
If it is possible, kindly suggest.
Regards,
Vimalan.

This is nothing but Trading process...
u will not know what amount of excise the vendor is passing on u..
just follow the below steps
hi
create material master with HAWA material type..
maintain material chapter id combination in J1ID
create tax code with zero excise and some vat/cst in FTXP
maintain condition records for tax code in FV11
Assign tax code to company code in tax on goods movement
create PO in ME21N with the tax code created.
During MIGO change the base amount
Base amount = Base amount(PO) - Excise(bed, ecess, secess)
enter the bed ecess secess in excise item details
In excise header tab click on additional data (pencil icon) there in miscellaneous tab check mrp indicator
post the document.
in MIRO change the base amount to base amount - excise.
During Purchase the RG23 A reg will Update..
During Sales RG1 willl update..

Level Based vs. Value Based hier: advantages, disadvantages and limitations

Similar Messages

Maybe you are looking for