DimensionmemberList with value-based dimension

Hi,
I'm unable to use a DimensionMemberList with a value-based dimension. It works fine with level-based, however when I select a value-based dimension and hierarchy in the wizard and click on "Next" an Error pop-up appears with no message and I have to click on "Cancel" to get out of the wizard.
Has anyone encountered this behavior?

Hi Ankita,
As per my Understanding the VP column did't map to any LTS .
When ever u have multiple LTS in Dim Admin tool won't create Dimension Hierarchy manually we need to create that.
Follow these steps to resolve your Problem...
1) give the simple join in physical layer for that two tables.
2) Create one Dim table in to BMM layer drag all columns in 2 tables in to BMM Dim table so u can able to see all the columns is mapped in to their respective LTS.
3) Now u can create hierarchy manually step by step.Like Grand total Parent ----> Child level .
4) If u have any fact table joined with these dimension in physical layer give the logical joins in BMM layer and set the content levels properly.
Let me know need any detail clarification.
Thanks,
Satya

Similar Messages

  • Value based dimension hierarchy in OBIEE 10G

    Hi,
    I am a user of OBIEE10G. I have to create a value based dimension hierarchy in my RPD. My hierarchy should be such that when I click on any VP Name, the respective employees working under him/her should be shown. But my columns of VP Name and Employee_Name are present in separate dimensions. Hence when I drag the column of VP Name to Employee dimension and then create the dimension hierarchy, I get an error of illegal cross join .
    Is value based hierarchy possible in 10G?
    Pls reply.
    Thanks
    Ankita
    Edited by: 848789 on Sep 28, 2011 8:40 PM

    Hi Ankita,
    As per my Understanding the VP column did't map to any LTS .
    When ever u have multiple LTS in Dim Admin tool won't create Dimension Hierarchy manually we need to create that.
    Follow these steps to resolve your Problem...
    1) give the simple join in physical layer for that two tables.
    2) Create one Dim table in to BMM layer drag all columns in 2 tables in to BMM Dim table so u can able to see all the columns is mapped in to their respective LTS.
    3) Now u can create hierarchy manually step by step.Like Grand total Parent ----> Child level .
    4) If u have any fact table joined with these dimension in physical layer give the logical joins in BMM layer and set the content levels properly.
    Let me know need any detail clarification.
    Thanks,
    Satya

  • Can we precompute a value based dimension ?

    Hi,
    I do not know how to precompute/summarize a value based dimension in AWM 10g.
    One of my value based dimension in AWM 10 g (10.2.0.3A) showed pre-compute already done , but the aggmap of the cube did not show any precompute clause in relation statement for this dimension.
    1) Is AWM 10.2.0.3 A taking care of this internally ? How can i verify this ?
    2) If not, how can i set pre-compute for a value based dimension by hand ?
    (provided the precompute clause remains even after cube is maintained).
    Regards
    Chakri

    Hi All,
    Thanks for your replies.
    Let me give you a background . Iam creating a cube over some value based dimensions in OWB (10.2.0.3) and then deploying them to AW .Iam loading the cube and dimensions using OWB mappings.
    Any other changes or objects not possible through OWB are done directly in AWM (10.2.0.3A)
    Stuart,
    Yes this a duplicate thread i posted for almost the same problem statement.
    David,
    1st option - precompute valueset is defaulting to all members.
    a) Are you talking about the valueset <DIMENSION>_PARENTREL(<VSET>)
    I did an rpr on <VSET> , it just returned the hierarchy name. This vset would be there for any dimension ( even without precompute) and would just return the default heirarchy
    b) or Are you referring to PRECOMPUTE(<VSET>).
    As mentioned, this VSET is not coming up in the aggmap.
    2nd option - Modify the XML template with the PreComputeClause to say Expressiontype="INCLUDE" instead of "EXCLUDE". You can then delete the cube and recreate it from your XML.
    The Model view of AWM (10.2.0.3A) was showing the 'All' box as checked for this value based dimension, but the aggmap did not show any PRECOMPUTE clause. Also, when i checked the XML of the cube (in which the dimension is used), there was no pre-compute clause for only this dimension. This might be due to my AWM version iam using.What is your AWM version ?
    How do i check if pre-compute is working ?
    Here is the info about my cube :
    Dimensions : TIME (Levels: Year,Quarter,Month) ,LOB,CUST and FIN
    All dimension except TIME are value based.
    Settings : compressed, partitioned along TIME.MONTH
    I want to fully precompute TIME and LOB .
    CUST and FIN should not be precomputed.
    Thanks
    Chakri

  • Pre-compute for Value based dimensions in AWM 10g

    hi,
    I created a compressed partitioned MOLAP cube in OWB 10.2.0.3 based on some value based dimensions.
    I selected the hierarchy in value based dimensions for pre-compute, but it did display the hierarchy in OWB.
    I deployed the cube into Analytical workspace AWM 10g(10.2.0.3A).It created PRECOMPUTE(NA) in the relation statement for the value based dimensions.
    Is it that value based dimensions cannot be pre-computed (at the heirarchy) in AWM 10g ?
    Regards
    Chakri

    For reference, I believe this error was due to the deletion and recreation of a standard form AW formula without full restoration of the formula's PROPERTY values. AWXML (and hence 10g OWB/AWM) will not work correctly if you remove PROPERTY values from objects.

  • Has anyone setup BIEE with OLAP 10g using value-based dimension hierarchies

    I just wanted to know if it is possible to setup BIEE with 10g using multple dimensions containing multiple value-based hierarchies?
    I know this involves using the OLAP Cube View Generator to create an sql view of the cube data.
    I have been able to get this to work with nine dimensions all containing a single value-based hierarchy bar one which had four value-based hierarchies. But as soon as i have multiple hierarchies in multiple dimensions it seems to go haywire and i cannot get the sql view to return correct data.
    I thought i would post on the BI side to see if anyone has been successful in creating a BIEE setup like this?

    The simple answer to your question,
    how robust is the 11g materialised views with multiple value-based hierarchies...?is that materialized views are not supported on top of value-based hierarchies in 11g. The reason is that it is not possible to write a reasonable SQL statement that aggregates a fact over a value-based hierarchy. Such a SQL statement is necessary if we want to create a rewritable MV on top of the cube.
    But I suspect this is not what you are really asking. If you are trying to set up OBIEE on top of the cube in 10g using the view generator, then you will probably want to use the "ET VIEWS" that are generated automatically in 11g. These are generated whether or not you enable materialized views on top of your cube. I am not aware of any issues with the generated value-based hierarchy view support in 11g. Members may be shared between value hierarchies and you will not need to generate or modify limit maps.

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

  • Value Based Dimension causing Aggrega                         tion problems

    I am new to building cubes in Oracle Olap, and am having trouble with a particular cube. (I hope I get all the terminology accurate enough to describe the problem I am having). Our organization structure is hierarchical. For example, org 0001is at the top of the "tree" and has 5 children: 1000, 2000, 3000, 40000, A000. Each of those 5 orgs have children that rollup to them. The problem is that the org "tree" is uneven. For example, Org 4000 has children that go down 4 more levels where the 3000 org only has children that go to level 3. We have about 1500 total orgs in the company. The dimension table we have shows the org_number and its Parent_org. Thus, I created an org dimension in AWM and then a value_based hierarchy. I can maintain and view the dimension in AWM and it all looks fine. I can then map the org dimension in the cube and maintain it (the cube that is). The problem is that the totals for my measures (actual costs) in the cube are way too high. Any advice as to what the problem is? I have verified that every org is in the table only once and that each org only rolls up to one parent org. I should mention that costs can be incurred by any org in the structure, no matter what level the org is at. Thanks for your help.
    Edited by: rybarrus on Jun 15, 2010 1:56 PM

    Thanks for your reply. That was a helpful suggestion. I found what seems to be the problem,but don't know why it is happening. When I look at a particular leg of the Org in the cube (in AWM) I see the following totals (indented to show parent child relationship):
    ORG--------------------Total
    1000...................602.42
    -------1030............557.48
    --------------1034.....557.48
    -------1060............ 44.94
    --------------1063..... 44.94
    When I Query the fact table I see the following totals:
    1000................... 0.00
    1030................... 159.05
    1034................... 557.48
    1060...................7,800.00
    1063................... 44.94
    To me, it looks like the total amount of the child is REPLACING the total of the parent. For example, the total in the cube for org 1060 should be 7,844.94 (7,800 + 44.94). Any reason why it doesn't sum correctly?
    Also, the total for org 1030 should be 716.53 (557.48 + 159.05).
    If you look back at my first post, I said that the overall total in the cube at the top level is way over the total in the table. That is still the case. This example that I have shown happens to be the opposite. The total I get when I query the fact table is greater than the total in the cube at this level. I hope that is not confusing.
    Edited by: rybarrus on Jun 15, 2010 4:37 PM

  • Pricing problem with value based free goods!

    Hi All,
    I've got a pricing problem.....
    Can anyone can come out with a solution.
    Here is the Business Scenario....
    In a super market pricing...should be implemented in such a way that....if the customer purchases any material(all materials) for $1000 he should be given  a materisl XXX one unit free (free goods)
    How to implement this in SD R/3 Scenario...
    i have tried out with Free goods...n pricing...but was not able to implement it..can any one of you suggest me a solution for this plz..
    Regards,
    Pavan.

    Hi Pavan,
    I would suggest that you post this message in the mySAP ERP business suite solution application forum. Here is the navigation info:
    Welcome to the SAP Forums » SAP Solutions » Enterprise Resource Planning (ERP) . It is more likely that someone from the SD slide will be reading that forum than this "SAP NetWeaver integration with my SAP ERP" forum. 
    I hope this helps,
    Mike.

  • OBIEE and Oracle OLAP Value Based Hierarchies

    Hi there...
    I have a value based dimension built on Oracle OLAP and want to map it on OBIEE Administration tool.
    I've been using the above link as reference:
    http://www.oracle.com/technology/obe/olap_biee/CreateBIEEMetadata.htm
    There's no option to import from Oracle Multi-dimensional Database. Either to import/configure the view created by OLAP as an Unballanced or Ragged Dimension.
    I also checked this example, but it uses ESSBASE as the multi-dimensional source....
    http://www.rittmanmead.com/2008/08/27/ragged-hierarchy-handling-in-obiee/
    How to map this Ragged Dimension created in OLAP workspace in OBIEE? Any suggestions or directions will be highly appreciated...
    Thanks in advance
    Marcos

    Mark and others,
    You can create OLAP_TABLE views with level columns on top of value-based hierarchies. BI Beans used to do that too behind the scenes in Discoverer Plus OLAP. If you trace the Discoverer session, where you are querying data from Value-based hierarchies, you will see that it also generates OLAP_TABLE views with level columns in it.
    So the question is how to do it. Internally, even for Value-based hierarchies Oracle OLAP keeps track of the "depth" of each value by using a structure called GID_DIMENSION (i.e., Grouping Dimension). Here is an example of a view on top of a value-based hierarchy (CFC_ACCT_GAPP) for RPT_ACCOUNT dimension. You have to know how "deep" your value-based hierarchy is.
    Similar kind of a thing is done by OLAP View Generator application, which I never use - since I always prefer to define my own OLAP_TABLE views.
    This kind of a view can then be used in the RPD of OBIEE.
    select *
    FROM table(OLAP_TABLE ('AW duration session',
    *'DIMENSION RPT_ACCT_ID FROM RPT_ACCOUNT WITH*
    HIERARCHY RPT_ACCOUNT_GAAP_PARENT   FROM RPT_ACCOUNT_PARENTREL(RPT_ACCOUNT_HIERLIST ''CFC_ACCT_GAAP'') INHIERARCHY RPT_ACCOUNT_INHIER
    HATTRIBUTE RPT_ACCOUNT_GAAP_LVL_NUM FROM RPT_ACCOUNT_DEPTHVAL
    FAMILYREL RPT_ACCOUNT_GAAP_LVL1,
    RPT_ACCOUNT_GAAP_LVL2,
    RPT_ACCOUNT_GAAP_LVL3,
    RPT_ACCOUNT_GAAP_LVL4,
    RPT_ACCOUNT_GAAP_LVL5,
    RPT_ACCOUNT_GAAP_LVL6,
    RPT_ACCOUNT_GAAP_LVL7,
    RPT_ACCOUNT_GAAP_LVL8
    FROM RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 127),
    RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 63),
    RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 31),
    RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 15),
    RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 7),
    RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 3),
    RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 1),
    RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 0)
    FAMILYREL RPT_ACCOUNT_GAAP_LVL1_DSC,
    RPT_ACCOUNT_GAAP_LVL2_DSC,
    RPT_ACCOUNT_GAAP_LVL3_DSC,
    RPT_ACCOUNT_GAAP_LVL4_DSC,
    RPT_ACCOUNT_GAAP_LVL5_DSC,
    RPT_ACCOUNT_GAAP_LVL6_DSC,
    RPT_ACCOUNT_GAAP_LVL7_DSC,
    RPT_ACCOUNT_GAAP_LVL8_DSC
    FROM RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 127),
    RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 63),
    RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 31),
    RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 15),
    RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 7),
    RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 3),
    RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 1),
    RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 0)
    LABEL RPT_ACCOUNT_LONG_DESCRIPTION
    ATTRIBUTE ACCOUNT_LDSC    FROM RPT_ACCOUNT_LONG_DESCRIPTION
    ATTRIBUTE ACCOUNT_SDSC    FROM RPT_ACCOUNT_SHORT_DESCRIPTION
    ATTRIBUTE ACCOUNT_TYPE    FROM RPT_ACCOUNT_TYPE
    ATTRIBUTE SOURCE_LEVEL    FROM RPT_ACCOUNT_LEVEL
    ATTRIBUTE CALCULATION     FROM RPT_ACCOUNT_CALCULATION
    ATTRIBUTE CALC_DATA       FROM RPT_ACCOUNT_CALC_DATA
    ATTRIBUTE GAAP_SORT_ORDER FROM RPT_ACCOUNT_GAAP_SORT_ORDER
    ATTRIBUTE RATIO           FROM RPT_ACCOUNT_RATIO
    ATTRIBUTE ACCOUNT_LEVEL   FROM RPT_ACCOUNT_LEVELREL'))

  • AWM 10.2.0.1 - I can not choosing Value Based hierarchy

    I have Oracle client 10.2.0.1 software with AWM 10.2.0.1 . I want to build a dimension with value-based hierarchy . In AWM I have hierarchy editor with the two radio buttons for choosing type of hierachy : Level Based hierarchy and Value Based hierarchy . But the secod one (Value Based hierarchy) is disabled - I can not choosing this type of hierarchy . Why this?
    Thanks in advance,
    Aurel

    Hi there,
    I really would not recommend that you work with the 10.2.0.1 version of AWM. This version is fairly old now and there have been a number of important bug fixes added to more recent releases.
    What version of the Oracle database are you running? And on what operating system?
    I suggest that you consult the following link and ensure that you are working with the versions of BOTH database and AWM that are recommended by Oracle:
    http://www.oracle.com/technology/products/bi/olap/collateral/olap_certification.html
    Thanks
    Stuart

  • Aggregation On Value Based Hierarchy

    Hi
    I am having a problem with aggregation on value based hierarchy
    Well I have a table which will serve as my fact and dimension table
    It is as follows
    ID     Name     MID     Salary
    0     All          
    1     A     0     10000
    2     B     1     9000
    3     C     1     9000
    4     D     1     9000
    5     E     2     8000
    6     F     2     8000
    I created a value based dimension named EMPLOYEE , with child as ID and parent as MID
    I created a cube EMP_SALARY with a measure salary mapped to the Salary column in Employee
    My expectation here is to see the total salary at every level including the salary at that level
    So let us take employee B as an example. He is the manager for employees E and F
    So what I would like to see at level B is sal of B + sal of E + Sal of F = 9000 + 8000 + 8000 = 25000
    But what I get from the cube is 9000. Now is the above possible ? If so please so provide me suggestions
    I can achieve the same by using the following sql query
    select e1.id,rpad('*',2*level,'*') || e1.name,e1.sal,
    select sum(e2.sal)
    from test_emp e2
    start WITH e2.id = e1.id
    CONNECT by PRIOR e2.id = e2.mid
    ) sum_sal
    from test_emp e1
    start with e1.mid is null
    CONNECT by prior e1.id = e1.mid;

    The same basic problem, along with a solution, was discussed in the following thread.
    Re: Value Based Dimension causing Aggrega                         tion problems

  • 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;
    /

  • OLAP on 11g and Materialised Views with Multiple Value-Based Hierarchies

    Hello OLAPians
    I am trying to setup Orable BIEE to report on an OLAP cube with pre-aggregated data. As OBIEE is not able to hook into the OLAP directly i have to create an SQL cubeview.
    Currently i am on a 10g OLAP environment and am using the oracle sample SQL cubeview generator to create an SQLview of my cube.
    The cube itself has multiple dimensions and these dimensions have multiple VALUE-based (ragged) hierarchies and dimension members can be shared across hierarchies also.
    Initially i had a problem running the view generator plugin because there is a bug within it that does not finish if there are multiple value-based hierarchies present. I was able to get around this by manually editing the limitmap for the cubeview and manually creating the SQL view.
    The question that i want to ask is how robust is the 11g materialised views with multiple value-based hierarchies and the sharing of dimension members across different hierarchies?
    Has anyone successfully been able to create a cubeview and import it into OBIEE without the hassle of manually editing the limitmap?
    A problem arises with the value-based setup whereby if the client creates a newer depth in the ragged hierarchy, i need to manually create the limitmap and the cube-view over again, and then re-map the BI Administration mappings.

    The simple answer to your question,
    how robust is the 11g materialised views with multiple value-based hierarchies...?is that materialized views are not supported on top of value-based hierarchies in 11g. The reason is that it is not possible to write a reasonable SQL statement that aggregates a fact over a value-based hierarchy. Such a SQL statement is necessary if we want to create a rewritable MV on top of the cube.
    But I suspect this is not what you are really asking. If you are trying to set up OBIEE on top of the cube in 10g using the view generator, then you will probably want to use the "ET VIEWS" that are generated automatically in 11g. These are generated whether or not you enable materialized views on top of your cube. I am not aware of any issues with the generated value-based hierarchy view support in 11g. Members may be shared between value hierarchies and you will not need to generate or modify limit maps.

  • Value based hierarchies and Period dimension should only contain  2  monthl

    Hi,
    Can anyone tell me what is value based hierarchies. And also can anyone let me know to filter the records in AWm because in Period dimension should only contain 2 monthly values (Oct. 2008 ( 200810) and Sep. 2008 ( 200809)) it is urgent.
    Thanks
    vel

    The following definition of a value hierarchy comes from the OLAP Developers guide
    "A hierarchy defined only by the parent-child relationships among dimension members. The dimension members at a particular distance from the base level do not form a meaningful group for analysis, so the levels are not named. For example, an employee dimension might have a parent-child relation that identifies each employee's supervisor. However, levels that group together first-, second-, and third-level supervisors and so forth may not be meaningful for analysis."
    Typically this means that the source table has two columns, VALUE and PARENT, where PARENT has a (logical) foreign key relationship to VALUE. An example may be EMPLOYEE, MANAGER, where MANAGERs are also EMPLOYEEs.
    The simplest way to restrict the values loaded into the AW is to define a SQL view over the source table with an appropriate WHERE condition. You then use AWM to map the dimension to your new view. E.g.
    CREATE OR REPLACE VIEW RESTRICTED_TIME AS
    SELECT *
    FROM TIME
    WHERE MONTH IN (200810, 200809)

  • Value based on the periodic unit price (only with pr.ctrl S)

    Dear all,
    There is this field in mateial master called "Value based on the periodic unit price (only with pr.ctrl S)" in accounting view 1,
    1 - May I know what is this field about (in between our company using material ledger).
    2 - May I know why the value of this field are different between our company period 6 and period 7 for this year? what contribute to it? and is it something wrong with different value between two different period or absolutely normal?
    Thanks.
    Tuff

    Dear all,
    Does anyone know my question?
    Thanks,
    tuff

Maybe you are looking for