Inserting a level in existing dimension hierarchy

hi,
I have to insert a new level in existing dimension hierarchy with out affecting other reports.
Please let me know how to do
Thanks in advance.

I fixed this problem by doing two things. Firstly I deleted
the summary slide at the end of the quiz. This stopped the error
dialog appearing, but the new slides I was trying to insert were
still overwriting an existing question. I then deleted the
questions that were being overwritten, and all subsequent inserted
questions worked correctly. Seems like something got corrupted in
the question slide.
The quiz result summary page gets regenerated so there's no
problem with deleting it if things get corrupted behind the
scenes.

Similar Messages

  • Passing values of the column in the last level of a dimension hierarchy.

    My report has two colums
    Column1 (Dimension has a hierarchy)
    Columns2 (Fact with an Aggregation Rule)
    I want to use the drill down facility in column 1 and pass the value in the last level of the hierarchy to navigate to another report. Can someone help me on this?
    [Note: The above is possible when the column that is on the last level of the drill hierarchy is in the main report]

    @ubuntupenguin Thanx for your prompt reply.
    I am currently able to store all the necessary symbols in an array. But, How do I query for multiple symbols in the SQL Query ?
    I have an array symArr[] which consists of all the symbols I need to query from the database. So, How should I write the SQL Query is my question.
    I could have created a string which looks something like this from the symArr[] array:
    XOM,AA,BAC,BB,BBC,....
    But, the problem would be when I try to query these symbols in the php data service using "SELECT * FROM TABLENAME WHERE SYMBOL IN (?)"
    where the variable $symbol is the populated string (XOM,AA,BAC,BB,BBC,.... ). So, to rephrase my question, Could I use SELECT * FROM TABLENAME WHERE SYMBOL IN (?) to query for Multiple symbols or is there a better approach.
    Thanx in advance.
    -Krishna

  • Changing the dimension hierarchy level keys in RPD online mode caused issue

    Hi,
    We tried to correct the dimension hierarchy level keys and remove prefered drill path settings in the business model layer in RPD in online mode. However this caused all the reports and dashboards based off of this subject area to show incorrect, and/or restricted data. The physical query generated by the answers requests were also incorrect.
    Even restarting the server and presentation services could not resolve the issue. Can someone please help us to understand what could have caused this issue?
    Thanks in advance

    Hi,
    I am not sure why the existing reports throw an error when I change the RPD dimension hierarchy level keys. Does anyone know how I resolve this issue.
    This is urgent. Any help will be most appreciated.
    Thanks in advance.

  • Introducing new level in existing hierarchy...

    hi experts!!
    I asked this doubt sometimes before but was unable to solve this....
    We have one hierarchy for one characteristic...now I got requirement to introduce one new level somewhere in between the existing levels....I tried to do it manually with peoples suggestion but it didnot go well....Can anyone point out where I am going wrong...
    I clicked on node under whose level I need to introduce these nodes....choose 'Insert Characteristic'...gave characteristic infoobject name and then choose the characteristic value....I succeeded so far....How can I get old nodes from old hierarchy which were in this level but pushed one level down in new hierarchy to point to this new node?
    Thanks.
    P Olin

    Hi,
      WHile adding the node there is something called adding as neighbour and adding as child. Use whatever necessary in ur case.
    Regards,
    Raghavendra.

  • Total levels on pivot with dimension hierarchy column incorrect

    Hi,
    I have a pivot table based on a single subject area, based on an Essbase cube.
    The problem I have is that some of the totals against the collapsed dimension hierarchy column are incorrect, it is as if they remember the pre-updated state, even though I have bounced the services and turned all caching off.
    When I expand the node then the totals appear correctly, but when reverted to the collapsed state it shows nothing again.
    I have turned off caching via EM.
    I have tried all flavours of totals, default, server complex aggregate et al with the same result for all.
    I have double checked the results at source with an identical query in SmartView and the upper level dimension total is populated in its own right, as well as its children carrying totals which do not sum back to zero.
    Any suggestions please??
    thanks,
    Robert.

    Can you validate the query hitting to the database and compare the results?
    Mark if helps.
    Thanks,

  • Dimension hierarchy creation

    Does exist best practices for creation of dimension hierarchy based on table like
    CAT_ID,PARENT_CAT_ID,CATEGORY_NAME where hierarchy tree might have different number of levels:
    level1-level2
    root -- level1-level2-level3
    level1

    Thaks for your answer, I already read those articles. Actually question was about creating in OBI of hierarchy which has different number of child levels like this:
    Organization - Division1-> Division1.2->Division1.3
    - Division2-> Division2.1->Division2.2->Division2.3
    Number of parent divisions under Organization is unlimited (Siebel model) and in table on which hierarchy is based not denormalized.

  • A Question Related to Dimension Hierarchy

    Hi All,
    While going through some hierarchies, i found that some columns were associated with the levels in hierarchy but these columns were not part of level keys.
    I want to know that what is difference between the result when columns that are not level keys are associated with a logical level and when such columns are not associated with a logical level ?
    Does such columns affect the result when selected in BI Answer?
    For exp -
    Suppose i have below time dimension hierarchy -
    Time
    ->Grand Total Level 0
    ---> Year Level1
    Year (Level Key)
    Year Start Date
    Year End Date
    ---> QuarterLevel2
    Quarter(Level Key)
    Quarter Start Date
    Quarter End Date
    ---> MonthLevel3
    Month(Level Key)
    Month Start Date
    Month End Date
    ---> Day Level4
    Day (Level Key)
    Day Start Date
    Day End Date
    These start date/end date columns are not part of level keys.
    The same thing i have observed in other hierarchies too.
    I want to know that what would happen, if these columns are not present at these levels?
    So When should we associate columns those are not part of level key to levels and when we should not associate ?
    Thanks,
    Ashish

    Hi ,
    The non key columns used in each of the levels help in faster retireval for that aggregate level .
    If you look closely at these columns you will find these to be unique ,now having said that another point is that these levels are also used for aggreagation
    as we all know.
    For ex at the month level the key identifies all the unique moths but if data has to be shown for one particualr month then with the start momth date and end month date the retrieval would be still better :)

  • Dimension Hierarchy

    We are in the process of creating a dimension hierarchy. We see multiple options here
    There is Logical Level. Each logical level can have multiple keys. Each key (*Logical Level Keys* ) can have multiple multiple columns. Each column has a check box. The Logical Level Key dialog shows Use for drill down option.
    What is the significance of
    keys
    Logical Level Keys
    The check boxes

    Any thoughts on this please ?

  • Navigating from detail level column in an hierarchy  to another report

    I have a requirement as folllows:
    In one report,i have a drill-down feature enabled on "TIME DIM".
    At The detail level of this dimension is "DAY" column.
    SO,from this detail level,when i click on "DAY" column, navigation should be done to another report..
    Is it possible to navigate so from detail report..
    pls let me know the solution for this requirement..
    thanks,
    seeusass

    Instead of Drill down,Give Navigation in first report to child report.But for this you need to create n reports if you are having n number of levels in hierarchy.Then at the detail level report you can give navigation at day level.
    Thanks
    Don

  • Dashboard prompt on a Dimension Hierarchy in Obiee 11g

    Hi All,
    I have created a hierarchy (parent-child) on a dimension 'A'. I am able to create a dashboard prompt for the dimension hierarchy. However I am not sure how to create a report that is to be filtered on this dashboard prompt. I tried using the attribute name that the hierarchy uses but that does not work. Can some one please let me know how i can filter a report by a hierarchy dimension prompt.
    Thanks,
    Nikita
    Edited by: user12438396 on May 8, 2011 1:16 PM

    Hi Nikita,
    For your requirement, you need to go for Selection steps pane in the analysis(report). Click on steps link and then add the hierarchy column that you want to use and expand the hierarchy to the lowest level. Now select all these and all the attributes will now appear in the other side.
    If you dont expand the hierarchy to the lowest level, then only the highest level values will appear in your selection at prompt.
    Also make sure to check the 'override' checkbox in the bottom, this helps in filtering the values.
    Hope this answers your question.
    Cheers,
    Obul

  • Listing attributes of a particular level in a dimension via API call

    Hi,
    We are using the Oracle OLAP Java api's to browse the metadata and contents of an OLAP schema. We need to be able to access an api that lists just the Attributes that are mapped to a particular Level within a dimension.
    Note the following snippet of code can be added to the OLAP Java examples. This displays a list of key value pairs. The keys are the unique level identifier in the form "HIERARCHY::LEVEL::ID", the value is the contents of the specified attribute. The result would be suitable for input to a combo box control in a JSP or similar.
    public static void getFilters(String dimension, String hierarchy, String level, String attribute) throws Exception {
    MdmPrimaryDimension mdmDimension = getMdmPrimaryDimension(dimension);
    MdmHierarchy mdmHierarchy = getContext().getHierarchyByName(mdmDimension, hierarchy);
    MdmLevel mdmLevel = getContext().getLevelByName((MdmLevelHierarchy) mdmHierarchy, level);
    MdmAttribute mdmAttribute = getContext().getAttributeByName( mdmDimension, attribute);
    StringSource levelSource = (StringSource)mdmLevel.getSource();
    StringSource attributeSource = (StringSource)mdmAttribute.getSource();
    Source querySource = attributeSource.join(levelSource);
    try {
    prepareAndCommit();
    getContext().displayResult(querySource);
    } catch (oracle.olapi.data.source.UnmatchedInputsException e) {
    System.out.println("UNMATCHED ID's " + e.getUnmatchedInputIDs());
    Prior to calling this we need a way of prompting the user to select the appropriate attribute to display in the value field of the list. We can get the full list of attributes for the Dimension with the following code snippet:
    MdmPrimaryDimension mdmDimension = getMdmPrimaryDimension(dimension);
    List attributes = mdmDimension.getAttributes();
    However calling the code below returns an empty attribute list.
    MdmPrimaryDimension mdmDimension = getMdmPrimaryDimension(dimension);
    MdmHierarchy mdmHierarchy = getContext().getHierarchyByName(mdmDimension, hierarchy);
    MdmLevel mdmLevel = getContext().getLevelByName((MdmLevelHierarchy) mdmHierarchy, level);
    List attributes = mdmLevel.getAttributes();
    What api's can we call that would let us list just the attributes mapped to the Level in question?
    Any help is appreciated.
    Regards,
    Ed

    <LINK (<IDESCENDANTS (PutMemberNameHere) AND <DIMBOTTOM (PutDimNameHere)

  • Why does OWB 9.2 generate UK's on higher levels of a dimension?

    When you specify levels in a dimension, OWB 9.2 generates unique key constraints in the table properties for every level, but only the UK on the lowest level is visible in the configuration properties. Why then are these higher level UK's generated? Is this a half baked attempt to implement the possiblility to generate a snow flake model in OWB?
    Jaap.

    Piotr, Roald and others,
    This is indeed a topic we spend a lot of our time on these past months. We are addressing this as (in my old days I had the same problem as a consultant) we know that this is a common problem.
    So the solution is one that goes in 2 directions:
    - Snowflake support
    - Advanced dimension data loading
    Snowflake is obvious, may not be desired for various reasons but we will start supporting this and loading data for it in mapping.
    If you want a star table, you will know that a completely flattened table with day at the lowest level will not be able to get you a unique entry for month. So what people tend to do is one of the following:
    - Proclaim the first of the month the Month entry point (this stays closest to the star table and simply relies on semantics on both ETL and query side).
    - Create extra day level entries which simbolize the month, so you have a day level with extra entries
    - Create views, extra tables etc to cover the extra data
    - Create a data set within the tables that solves the key problem
    We have opted for the last one. What you need to do for this is a set of records that uniquely identify any record in any level. Then you add a key which links to the dimension at the same point (a dimension key), so all facts always use this surrogate key to link (makes life in query tools easier).
    For a time dimension you will have a set of day records with their months etc in them (the regular star). Then you add a set of records with NULL in the day having months and up. And you go up the hierarchy. For this we will have the ETL logic (in other words you as a designer do not worry about this!). On the query tool you must be a little cautious on counts but this is doable and minor.
    As you can see none of the solutions are completely transparent, but we believe this is one that solves a lot of problems and gives you the best of all worlds. We will also support the same data structure in the OLAP dimensions for the database as well in the relational dimension. NOTE that there are some disclaimers with this as we are doing software here...
    In principal however we will solve your problem.
    Hope this explains some of our plans in this area.
    Jean-Pierre

  • Naming of top level in a dimension

    Hi,
    I was wondering if the naming of the top level in a dimension. Earlier I have just named the top levels whatever suited me the best, and haven't had any problems with that. A couple of days ago I came a across an article on Mark Rittmans weblog where it said that Discoverer and BI beans expect a total level.
    Should all the top levels be named total_***** ?
    What is the consequence of not naming them total_****?
    Anyone have any thoughts on this?
    Regards Ragnar

    Level names can be reused across dimensions. This is common. For example, detail level data is very often shared across levels. When is comes to summary levels, you need decide whether this makes sense. Consider two hierarchies:
    Shipping Hierarchy, with levels:
    Total Product
    Region Shipments
    Country Shipments
    Warehouse
    Item
    Product Type hierarchy, with levels:
    Total Product
    Brand
    Group
    Item
    In the above case, Total Product in each hierarchy should yield the same values because it is the aggregation of all items. So, you might decide that is ok. A different case might not be ok. Consider:
    Shipping Hierarchy, with levels:
    Total Product
    Region Shipments
    Country Shipments
    Warehouse
    Items shipped
    Product Type hierarchy, with levels:
    Total Product
    Brand
    Group
    Items sold
    Since Items Shipped and Items Sold are likely to have different values, the aggregation of each level will yield a different value. In this case, Total Product as the top of each hierarchy doesn't make sense.
    A different twist would be (note the display names):
    Shipping Hierarchy, with levels:
    Total Shipments with 'Total Product' as display name
    Region Shipments
    Country Shipments
    Warehouse
    Items shipped
    Product Type hierarchy, with levels:
    Total Product Types with 'Total Product' as display name
    Brand
    Group
    Items sold
    In this case there will be different levels with different values, but the user will see each as 'Total Product'. Only your user community can tell you if this is want they want.

  • 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

  • Number of Elements at this level --------------( 1 for Dimension Total)' ?

    Hi All,
    If we check the Dimension Hierarchy Property ..there is option like ‘Number of Elements at this level --------------( 1 for Dimension Total)’
    ‘Number of Elements at this level --------------( 1 for Dimension Total)’ ? in Dimension Hierarchy
    What is the use of it ?

    Number of Elements - What is it?

Maybe you are looking for