Reporting at different levels in a Hierarchy

Hi,
How can I report at different levels within a hierarchy? Currently within SAP and BW I have levels 1 to 7, however currently I have to go through level 1 to see any information.
Please let me know, any help much appreciated
Thanks
Bhav

Hi Riccardo,
How can I create variables for selecting nodes of the hier?
I can bring in the hierarchy, but any variables i create only allow me to select different hierarchies.
What I am trying to do is create a report to run for level/ node 1 of 7 (the top level), this would allow users to expand if necessary and also another one that only has level/node 6 & 7, without levels/nodes 1-5.
Any help would be much appreciated.
Thanks
Bhav

Similar Messages

  • Colour in different ways, rows of different level of a hierarchy in WAD 7.0

    Hi all,
    Can anybody  tell me how  to colour in different ways, rows of different level of a hierarchy, in a web template? I’m working with WAD 7.0
    Thank you,
    Best regards
    Savino Pompa

    Hi wand,
    I know but i have to use Web template and i don't understand why By WAD 3.5 it  was possible format layout through stylesheets and now by Wad BI i can't.
    Thanks Savino

  • Display different level for same hierarchy value in BO 4.0

    Hi Expert,
    I have one question for Webi for BO 4.0
    We have one hierarchy in BW side and we hope to display differet level in same report for different column
    For example, column A is for level 6. column B is for level 7.
    Do you know how to releaze this in Webi side?
    In the 3.X version, we have different dimension for different level.
    But now in BO 4, it has been combined into one\
    Thanks and best regards
    Alex yang

    Hi,
    You can still do this in BI 4.0, if you use the old 'legacy'  MDX OLAP.unv from Universe Designer tool .
    Yes, with the BICS connection,  you are getting a native hierarchy, as it would be displayed in an OLAP environment.
    Cheers,
    H

  • Report with same measure but opened by 2 different level of emp hierarchy

    Hi all, I need to have a report with columns like these:
    COLS: Region -- Employee Level 3 -- Product Class -- Forecast ($) for Emp Level 2 -- Forecast ($) for Emp Level 2
    SAMPLE: NAS -- Anthony Fernicola -- Apps -- 100 (forecast for Anthony) -- 500 (forecast for Anthony's manager which is Keith Block)
    I mean, on the report criteria I drag those columns and and from the emp hierarchy dimension I drag that EMPLOYEE LEVEL 3 column since the report must show all those employees for that level, but as you can see on the same line of the report we should show as well the forecast for the manager, in this case the EMPLOYEE LEVEL 2..
    To get that measure I tried:
    1) on the formula the SUM (forecast($)) BY EMPLOYEE LEVEL2 but the data is not matching the real data..
    2) I also tried to use the FILTER function on the formula but I don't know how to filter it since it requires a filter_expression that I cannot give, I just want to show on that "Forecast ($) for Emp Level 2" column the forecast measure by that level 2..
    3) I also tried UNION but on the results the report is showing as well the LEVEL 2 for the employee and we do not want it since we want to show all LEVEL3 only...
    do you know how to do this?
    thank you!!!!

    Are you sure the brackets are in the right location?
    This:
    SELECT
    0 s_0,
    "A - Sample Sales"."Sales Person"."E1 Sales Rep Name" s_1,
    "A - Sample Sales"."Sales Person"."E9 Manager Name" s_2,
    "A - Sample Sales"."Base Facts"."1- Revenue" s_3,
    SUM("A - Sample Sales"."Base Facts"."1- Revenue" BY "A - Sample Sales"."Sales Person"."E9  Manager Name") s_4
    FROM "A - Sample Sales"
    ORDER BY 1, 3 ASC NULLS LAST, 2 ASC NULLS LAST
    works fine for me
    Regards
    John
    http://obiee101.blogspot.com
    http://obiee11g.com

  • BEx Analyser: How can I define colours for different levels of a hierarchy?

    Hi everyone,
    I have a report in BEx Anaylser that includes a hiearchy of 9 levels.
    For a better overview, I want to define different colours for the cells of each level. In this way, the user should be able to see which numbers belong to which hierarchy level. How can I do this?
    Best regards
    Daniel

    Dear Anujit,
    Thanks for your answer.
    Seriously? I cannot do this with BEx Analyzer other than using Excel VBA macro?
    Cheers, Daniel

  • Can I map different levels of a hierarchy to different sources

    Hi,
    I want for AWM not to aggregate the upper levels of a dimension by itself. Instead, i want to feed the data for upper levels also through different sources.
    Its becauese, the measure values of my dimension can not be aggregated from lower level. The value has to be calculated separetely.
    I know that the AWM will not aggregate when i specify the dimension agg rule as 'NON ADDATIVE' or something like that. I did it and i was done too. There were the data only for base level for that particular dimension. The other levels were empty.
    Now i want to feed the data for other empty levels from different source.
    Does anyone knows if it is possible in AWM 10.2.0.1 or can i do it from any other way?
    If one knows how to do it, i would be very much grateful to know it clearly.
    with regards,
    subash

    The following method assumes that you are assuming responsibility for managing all of the aggregate level data on your own:
    1. Define the cube as (a) uncompressed (the aggregate space of a compressed cube is always managed by the multidimensional engine), (b) with aggregation methods of SUM for all dimensions and (c) with only the detail levels selected on the 'Summarize To' tab of the cube definition. This will set up the cube so that it will not aggregate data when it is loaded.
    You will have a formula used to represent the measure and it will look something like this:
    DEFINE SALES_CUBE_SALES FORMULA DECIMAL <TIME CHANNEL CUSTOMER PRODUCT>
    EQ aggregate(this_aw!SALES_CUBE_SALES_STORED using this_aw!OBJ1819687276)
    You can see from the AGGREGATE command in the formula that it is set up to aggregate data at runtime if necessary. The formula reads from a variable that will look something like this:
    DEFINE SALES_CUBE_SALES_STORED VARIABLE DECIMAL WITH AGGCOUNT <SALES_CUBE_PARTITION_TEMPLATE <TIME CHANNEL CUSTOMER PRODUCT>>
    2. Load the data. You can load the base data through AWM if you wish or you can load it into the variable of the measure using OLAP DML code. You cannot map tables to summary levels using AWM, so you will need to use OLAP DML code to do this. An example program follows.
    DEFINE LOAD_SALES PROGRAM INTEGER
    PROGRAM
    vrb _errortext text
    trap on HADERROR noprint
    sql declare c1 cursor for -
    select -
    to_char(MONTH_ID), -
    to_char(ITEM_ID), -
    to_char(SHIP_TO_ID), -
    to_char(CHANNEL_ID), -
    SALES -
    from GLOBAL.SALES_FACT -
    where -
    (MONTH_ID IS NOT NULL) and -
    (ITEM_ID IS NOT NULL) and -
    (SHIP_TO_ID IS NOT NULL) and -
    (CHANNEL_ID IS NOT NULL) -
    order by -
    CHANNEL_ID, -
    SHIP_TO_ID, -
    ITEM_ID, -
    MONTH_ID
    sql open c1
    if sqlcode ne 0
    then do
    _errortext =  SQLERRM
    goto HADERROR
    doend
    sql import c1 into -
    :MATCHSKIPERR TIME_MONTH -
    :MATCHSKIPERR PRODUCT -
    :MATCHSKIPERR CUSTOMER -
    :MATCHSKIPERR CHANNEL -
    :UNITS_CUBE_PRT_TOPVAR(UNITS_CUBE_PRT_MEASDIM 'SALES')
    if sqlcode lt 0
    then do
    _errortext =  SQLERRM
    goto HADERROR
    doend
    sql close c1
    sql cleanup
    return 0
    HADERROR:
    trap on NO_ERROR noprint
    sql close c1
    NO_ERROR:
    trap off
    sql cleanup
    END
    3. Change the formula of the measure so that it does not aggregate using OLAP DML commands. E.g.,
    consider sales_cube_sales
    eq SALES_CUBE_SALES_STORED
    The formula will then simply get data from the variable rather than call the aggregate system.
    Since you are writing to the physical implementation of the AW you will need to check this code each time you upgrade the database because the physical implementation changes from time to time. (Usually major releases such as 10.1 and 10.2, not usually maintenance releases, but you never know.)

  • Displaying different levels of the same hierarchy in the different columns

    I have a parent child hierarchy and wish to display different levels of the hierarchy in different columns of the resultset eg
    level 1 level 2
    Europe UK
    Europe France
    N America US
    N America Canada
    However writing MDX like the below
    select
    {} on 0,
    ([Geo].[level 1],[Geo].Level 2] on 1
    from cube
    results in the error "The [Geo] hierarchy is used more than once in the crossjoin
    How can I get around this??

    Hi,
    You can make use of CrossJoin function in MDX, I give a sample MDX based on the AdventureWorks database:
    select {[Measures].[Reseller Sales Amount]} on 0,
    crossjoin({[Sales Territory].[Sales Territory Group].[Sales Territory Group].members},{[Sales Territory].[Sales Territory Country].[Sales Territory Country].members}) on 1
    from [Adventure Works]
    After execut the MDX you will get the result like this:
    Reseller Sales Amount
    Europe
    France
    $4,607,537.94
    Europe
    Germany
    $1,983,988.04
    Europe
    United Kingdom
    $4,279,008.83
    NA
    NA
    (null)
    North America
    Canada
    $14,377,925.60
    North America
    United States
    $53,607,801.21
    Pacific
    Australia
    $1,594,335.38
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

  • Relating facts to different levels of a dimention

    Dear All,
    I need to relate a fact to optionally different levels of a hierarchy in a dimension
    that's sales plan may be put on the level of a salesman or a distributor or a channel and so on ...
    I think that it could be implemented by adding a dummy record in a each level that represent the parent .. but i don't konw how to add this dummy record in owb ...
    can you help ..
    Regards,
    Shaimaa

    Hi Shaimaa,
    this is actually a very difficult business question. Technically, it's straightforward.
    The easy part is to create one fact table per dimension level where you have a plan. So, you would have a SalesPersonPlanFact, a SalesManagerPlanFact, and so on. That will work technically . . .
    But it won't really work. :-(
    The reason is that the way these plans are created. Typically, the Boss and his guys work out a master plan. Then it gets broken into bits, and each department does their own sub-plan. All the way down, until it gets to individual sales plans. And at every step of the way, the plan gets tweaked, modified, 'special cases' put in.
    The result is that they never add up. How you resolve that is a business issue, not a technical one.
    Me? What I do is tell people that they won't add up, and then say that it doesn't matter anyway. The reason I give is that the purpose of the plan is to measure actual sales performance against plan, and that we can do. Sales take place at the most atomic level for which there is a plan, and these we can match and consolidate plan against actuals. The consolidated results are then MVed and thus present a high-performance single picture of 'the truth'.
    Realistically, you're building a second-level snapshot (could be aggregated, could be periodic, could be both), and that's your reporting structure.
    I suspect you may need to go and have a re-think about your value chain, and do much communication with your sponsors so that they understand what's achievable and of real worth to the business. After all, your business as a data warehouse architect is to ensure you're publishing the right data.
    Cheers,
    Donna

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

    Hi 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

  • OBIEE report from multiple facts at different levels

    Currently we need to develop a report with columns from 3 different facts surrounded with conformed and non conformed dimensions at different levels.
    After setting the hierarchial levels and putting the facts into single logical table with different sources OBIEE is generating 2 different queries and does a full outer join.
    I would like to know how we can do a left outer join instead of full outer join between the 2 queries based on a common column?
    Thanks in advance.

    Hi Vinod,
    The scenario provided in the link above doesnt match to my issue.
    We need to develop a report from multiple fact tables at different levels with conformed & non conformed dimension columns.
    I have 7 dimensions D1, D2, D3, D4, D5, D6 and D7 & two fact F1 and F2 tables.
    F1 is tied to dimensions D1,D2,D3,D4,d5
    F2 is tied to dimensions D3,D4,D5, D6 and D7.
    In my report I have columns from D1, D2, D3, D4, D5, D6, D7, F1 and F2.
    So OBIEE generates 2 queries with columns from D1,D2,D3,D4,d5 & F1 measure and another query with D3,D4,D5, D6, D7 and F2 measure.
    and then does a cross fact join out of box between 2 queries.
    But I need to do a left outer join between the 2 queries on a common column instead of cross fact join. I would like to know how we can achive this.
    Thanks.

  • Dynamic reports for different access levels

    <p> </p><p>I want to create a report using Hyperion Report which will showthe data dynamically.</p><p>I have certain hierarchy in my dimesions and there are differentusers associated with different hierarchy levels.</p><p>E.g. Person1 can access only Level 0 data. Person 2 can accesslevel 1 and level 0 data. Person3 can access level 2, level 1 andlevel 0 data. Basically any user can access data of all itsdescendants.  </p><p> </p><p>All this needs to be done using same report becuase they areviewing same kind of reports , but just the different levels ofdata.</p><p> </p><p>Please guide me, how to implement this using Hyperion Reports.It would be a great help.</p><p> </p><p>Thank you.</p>

    Hi again
    Well, here's the way it may work for a compiled .CHM setup.
    If you are using compiled .CHM files, I'm guessing your software is
    modular. Meaning that at the time it is installed, the user has
    options of choosing between the following modules:
    Module 1
    Module 2 - 9
    Module 10
    In this setup, you would create help that is generic that all
    modules would need. That one would be the Master. Then you would
    create separate projects for the remaining modules. You would then
    provide it all to the person that handles the installation program
    for your application. That person would then handle configuring the
    installer application so that only help for the actually installed
    modules is installed. If a module has been excluded, help is not
    installed for that module and doesn't appear and is not available
    to the user.
    Hopefully that makes sense to you. If not, ping back and I or
    someone else will take a stab at another explanation.
    Cheers... Rick

  • Extract Data in Power Pivot from MDX with diffrentnt different Level of Hierarchy in MDX

    Hi All,
    My requirement is to extract the data form tabular model and put in power pivot,as all the measures calculation is present in model just extracting the aggregated data.
    Issue is appearing on Rolling up the data, so is there any way to extract the data so that it will display the right data on different level. As per the below example on level 2 data is getting summed up which is not correct.
    Ex:-
    Level1
    A
    10%
    B
    20%
    Level2
    30%
    Thanks Chandan

    Hi Chandan,
    According to your description, you create a SQL Server Analysis Services Tabular model and extract Data in Power Pivot from MDX, the problem is that the hierarchy data rolling up base on the hierarchy level, right?
    I have tested it on my local environment, we cannot reproduce this issue. So as per my understanding, the issue can be cause by the hierarchy setting in your tabular model. Here are some links about how to create and manage hierarchies in a tabular model,
    please refer to the links and check if the settings are correct.
    http://msdn.microsoft.com/en-in/library/hh213003.aspx
    http://www.youtube.com/watch?v=qKKNY1Vj_2c
    If the issue persists, please provide us more information about you hierarchy creation steps, so that we can make further analysis.
    Regards,
    Charlie Liao
    TechNet Community Support

  • Different elements of different levels of hierarchy

    Hi experts,
    I have a question about hierarchies obiee 11g.
    I need to do a table that contains (plain text, without '+' to drill-down) different elements of different levels of hierarchy
    I have a hierarchy Account like this:
    Level1
    -----Level2
    -------Element1Level2
    -------Element2Level2
    ------------Level3
    --------------Element1Level3
    -------Element3Level2
    My assignment is to do a table like this
    Level1---------------
    Element2Level2--
    Element1Level3--
    Element3Level2--
    So I don't want to drill-down on Element2Level2 to see Elements of Level3...
    How can I achieve this??
    Thanks!

    If I a not wrong, you basically want to flatten out a hierarchy. You should be able to do it using the Parent-child hierarchy concept newly introduced in OBIEE 11g where the RPD generates the DDL and DML for you, but you might have to build out an intermediate table to source the final flattened hierarchy table. Refer to this link which has a great example. ( http://prasadmadhasi.com/2011/11/15/hierarchies-parent-child-hierarchy-in-obiee-11g/ )
    Thanks,
    -Amith.

  • Display the technical name of the last level of the hierarchy

    Hello,
    I have a report with hierarchy. Each level of the hierarchy uses different infoObject. I want the report to display the technical name only for nodes from specific infoObject. For example if the infoObject uses 0cust_grp1 (for the first level), 0cust_grp2 (for the second level), 0cust_grp3 (for the third level) and 0customer (for the last level) and I want to show the technical name only for the 0customer infoObject. I know how to do it in WAD reports. Is there a way of doing it in the Query Designer?
    Please Advice,
    David

    David,
          Check the below possibilities.
    1. You can do that in a workbook.
    2. Create a copy of the same hierarchy and for the 0CUSTOMER object and nodes give tech names as text also.

  • OBIEE Facts at different levels.

    Hi,
    I am bringing columns from three tables: Two facts and one Dimension table to create a OBIEE Report.
    The fact tables Workforce Event Fact and Employee Daily Snap Fact are at different levels, but both of them have proper joins with Dimension Employee Dim.
    When i am pulling columns from D1 and any one of these two facts, i am not facing any problem in seeing results. But when i bring columns from all of these three tables, i am getting this error,
    State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 15018] Incorrectly defined logical table source (for fact table Workforce Event Fact) does not contain mapping for [Employee Daily Snap Fact.Exempt Indicator]. (HY000)
    Is there anything i have to do in Business Model layer to avoid this error. Many people suggesting to assign an aggregation level for these two facts. But i am not having any Dimensional Hierarchy defined.
    Thanks
    Swami

    Hi swami,
    Many people suggesting to assign an aggregation level for these two factsThis is a workaround i think where you need to create aggregate tables(not levels) and then use them for your purpose.(OR) you dint define the logical source table properly either correct it.
    Another work around i could suggest is,take the 2 fact tables columns needed into one alias table and make it as fact and join this fact table to dimension table and you can get all columns.
    Hope it helps you.
    Best Wishes,
    Kranthi.

Maybe you are looking for