Multiple Hierarchies display in BW report

Hi All,
I am having issue regarding multiple hierarchies display in BW report, not all levels are displayed, but i can see them in their respective hierarchy maintenance.
i have a report like project definition hierarchy then WBS hierarchy then followed by Order info object into rows and then some KFs in colums.
when i drill down project  definition hierarchy i coudn't able to see some middle nodes, but few at the bottom which have orders in next WBS hierarchies. and same as in WBS hierarchy i can see ony few WBS which have orders.
But i want to display all project definition nodes and WBS hierarchy nodes. even though there are no ordes for WBS elements.
there are no zero supressions neither in Hierarchy attributes nor in KF structures.
what could be the problem, how can i resolve it. I have been searching in SDN but couldnt find suitable solutions. Please let me know the earliest.
Thanks
Robyn.

Hi,
The problem that you have explained generally comes because of two problems.
1. If you do check for zero suppression
2. You don't go for full expansion level of heirarchy.
Any way you mentioned first case is not applicable for you, check for second case. Expand heirarchy upto maximum level. Your problem will be resolved.

Similar Messages

  • Multiple hierarchies single dimension single report

    I am trying to add multiple hierarchies from a single dimension in a single report. To create the hierarchy in BI admin I followed the instructions found here
    Oracle BI EE 10.1.3.3/2 – One Dimension – Multiple Hierarchies « Business Intelligence &am…
    and here
    https://forums.oracle.com/thread/2440305
    My Patient hierarchy looks like the this
    All Patients->Gender->Patient ID
    All Patients->Age Group->Patient ID
    When I drag and drop the second hierarchy in the Criteria Oracle BI Answers says the following "...you can only add one hierarchy per dimension to a report". I deduct that what I am trying to do is not possible!:-)
    Q1: Is this feature indeed not supported or am I doing something wrong?
    Q2: If this is not supported can someone explain why?
    Version Oracle Business Intelligence 11.1.1.6.0

    a) Reporting across levels of 2 hierarchies is not supported. As explained below, you cannot use OLAP to get aggregate values at cross combination of levels from hierarchies: H1 and H2.
    However if you wish to, you can report at the lowest level, Patient, common to both hierarchies and display the Age Group as well as Gender attributes corresponding to each patient. This becomes reporting at Patient/lowest level. You can of course use the capabilities of the reporting tool like obiee to use a Pivot object (say) and exclude Patient columns like Id, name etc. and get obiee to perform localized summaries within the reporting layer and get summarizations of interest. OBIEE Pivot measures allow for aggregation using Min, Max, Sum, Count, Running Sum etc. OLAP facilitates this solution but does not particularly help in the aggregation (since aggregation is now being done in obiee and not as per cube definition rules in olap aw). It acts as a source for information at the lowest level stored in the cube. Some performance degradation would result but it may be acceptable/manageable depending on the data volumes/report criteria.
    NOTE: For workaround/solution, use the regular fields, not hierarchical columns, from OBIEE presentation layer.
    b) Not supported: OLAP Cubes contain pre-calculated (or dynamically calculated) summaries at various level of each hierarchy. This aids in faster reporting performance. Allowing 2 hierarchies at the same time defeats this feature/goal. A cross combination of levels across different hierarchies requires a dynamic recalculation of the detail records to get the right values for, say, Age Group: 30-39 and Gender: Male. H1 summaries at AgeGroup level for Age Group: 30-39 cover all genders and cannot be split up into male/female w/o recalculation. Similarly H2 summaries at Gender level for Gender: Male cover all age groups. Splitting it up is not possible except via workaround/ solution explained in (a).
    Hope that helps.

  • How can i display Value in Report which i select from Multiple select list

    Dear All,
    i am using multiple select List in form with report page.
    When i create new Entry with select Multiple value in Multiple Select List then in report Value display me in below format
    my SQL Query are
    select NAME D, CODE R from  COUNTRY_MAS WHERE ACTIVE_FLG ='Y' order by NAME
    AS:AI:AG:AM these are return value .i want to display NAME in report .
    How can i do this ?
    Thanks
    Edited by: Vedant on Apr 25, 2012 11:14 PM

    Short answer, use the apex_util.string_to_table to convert to a table; then you can either iterate through the table to generate a string of names, or accomplish the same with a bulk operation.
    http://docs.oracle.com/cd/E23903_01/doc/doc.41/e21676/apex_util.htm#CHDFEEJD
    Encapsulate all this within a pl/sql function.

  • BEx hierarchies not displayed in Crystal report parameters

    Hi All,
    I am trying to using a Bex query that has a cost center hierarchy with a variable that allows users to select specific nodes or even cost centers. In BEx reports, this query works fine and gives the users the view of the cost centres in a hierarchial manner. However, in Crystal reports, the query provides a drop down menu displaying a simple list of all the cost centres (not in a hierarchial manner). This confuses the user as to which element is a node and which is a cost centre
    Kindly suggest how can we achieve the cost centre hierarchy to appear in the parameters in Crystal.
    Thanks

    Hi,
    this is a duplicate to this entry:
    key figures are not displayed in crystal report
    Please do not post the same problem multiple times
    regards
    Ingo Hilgefort

  • Reporting on Multiple Hierarchies (with EvDRE)

    Hi all,
    I have a question regarding multiple hierarchies in one dimension. So if we have one member that belongs to different hierarchies:
    1) can we access it with EvDRE? (I've tried it without success).
    2) if not, how can we report accessing the appropriate value (that is, accessing the appropriate hierarchy?)
    I would like to be able to access its value and setting up an expansion based on both hierarchies.
    Regards,
    Rafa

    Dear All,
    I am New to SAP-BPC.
    I am working on financial budget Appication. I created dimensions and uploaded successfully.
    I and generated reports.
    Now iam prolbem is. I am preparing below reports in BPC-Excel-->Drag & Drop EvDRE Grid.
    My report is showing something like below:
    BudgetItems   |    Yr-2007 |  Yr-2008  |
    Publice_Sector|    200     |   220     |
    Pvt_Sector      |    400     |   440     |
    But i need some thing like below
    BudgetItems    |    Yr-2007 |  Yr-2008  | Change  | % Change |
    Publice_Sector |     200     |     220     |      20       |           |
    Pvt_Sector       |     400     |     440     |      40       |            |
    Here i think i have to write formulas with EvDRE.
    Can anyone help me...
    Thanks a lot in Advacne..!
    MyGmail: satish.mba.sap
    Thanks & Regards,
    Satish.

  • Multiple Hierarchies on single characteristic in BEx

    In BEx 3.5 Is there a way to display multiple hierarchies/groups on one characteristic? For example, reporting by a Cost Element with several child hierarchy subgroups from differnt parents. An orphanage if you will.
    I try that and the fisrt group displays but the rest are in Not Assigned area.

    Thanks. That's what I was afraid of. I'm finding that to be true as well. I tried building a custom hierarchy based on sub-groups of other hierarchies. Not possible either. That would be a nice feature to have, so that the sub-groups are maintianed as they are from the source.

  • Discoverer support for multiple hierarchies

    Hi all,
    is it true that Discoverer supports only a single hierarchy per Analytic Workspace dimension?
    If this is true what is the recommended work-around:
    - create an AW dimension per hierarchy?
    - forget about analytic workspaces and take a ROLAP approach?
    - other?
    thank you in advance for any hints
    Nikos

    I'm not a discoverer user, so what I say might not apply, but in general it usually doesn't make sense to select members from multiple hierarchies. This would give end users of a report the ability to select values that don't accurately represent the total levels displayed.
    I guess my questions would be:
    a) what business value does picking dim values from multiple hierarchies serve?
    and
    b) it is possible in discoverer to simply not select any hierarchy and just choose the dimension values without one? Would that solve your problem?
    I guess high level this doesn't sound like either a bug or non-functional support issue, it sounds more like intended functionality.
    Let us know what your needs are! Maybe we can give a better answer if we know what business problem you are trying to solve.
    Thx,
    Scott

  • Using HLEVEL Property with Multiple Hierarchies

    Hello,
    I am trying to use the HLEVEL property on a dimension to indent the rows different amounts. Easy stuff, except I'm doing a row expansion on hierarchy 3 (H3).  Using EVPRO(AppName, MemberID, "HLEVEL") always returns the HLEVEL from H1.  If you select the same member ID in the member selector under different hierarchies and click the Properties button you can see a different value for HLEVEL, but I can't figure out how to get that in a report using EVPRO.
    Is there a way to tell EVPRO specifically which hierarchy to use when returning the value for HLEVEL?
    Thanks!
    Paul Petersen
    Akili

    Mike,
    please check the answer in this other post:
    EVPRO with multiple hierarchies
    It's for the MS platform, but it's the same for Netweaver.
    EVPRO can only retrieve the HLEVEL for the first hierarchy. You need to maintain further custom properties if you want to get the level of a member within multiple hierarchies.
    Regards,
    Simmaco

  • Exporting to multiple PDF's from one report

    I have a requirement to create multiple PDF's from one report.
    My thought is that I can I can create a foreach loop that cycles through one of my groups.  I would then like to have each file have the name of that group. 
    If anyone could help me on how to code this in C# that would be great.  I need to know where I should be putting this code (program.cs or crystalreport.cs) and how I run it.  I am assuming I don't need the viewer for this function, since this is all on my end and no users need to have access to it. 
    My other requirement is to have each of these reports be put into their own folders at C:\.  Thanks for the help in advance!

    OK. Yup, you should be able to do this. When I was reading the initial post it looked like you might have ben wanting to export only a certain section of a report (which is a no go).
    Anyhow, first thing you want to do is apply Service pack 3:
    https://smpdl.sap-ag.de/~sapidp/012002523100007123572010E/cr2008_sp3.exe
    Next, you want to look at a few sample apps and go over some docs. What you want to achieve can be done by using parameters or selection formulas.
    A good coding resources is the [Crystal Reports for Visual Studio 2005 Walkthroughs|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/2081b4d9-6864-2b10-f49d-918baefc7a23]. Don't worry about the title, it will apply to CR 2008 also.
    Next, sample apps can be downloaded from here:
    https://wiki.sdn.sap.com/wiki/display/BOBJ/CrystalReportsfor.NETSDK+Samples
    [CR 2008 developer library|http://help.sap.com/businessobject/product_guides/boexir31/en/crsdk_net_dg_12_en.chm]
    [API reference|http://help.sap.com/businessobject/product_guides/boexir31/en/crsdk_net_apiRef_12_en.chm]
    Not sure if you are thinking of this being a web app, but here are some resources for that:
    [Interactivity and Reports in Web Applications|http://www.sdn.sap.com/irj/boc/index?rid=/library/uuid/208edbbf-671e-2b10-d7b5-9b57a832e427&overridelayout=true]
    Before starting your project, you should have a look at [this|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/40bccdfd-88a6-2b10-1da1-c47a54b625a7] to make sure you are using the right SDK for your purposes.
    Finally, the following are links to 3rd party resources and I'm adding htese just as an FYI:
    http://www.emoreau.com/Entries/Articles/2006/09/Feeding-Crystal-Reports-from-your-application.aspx
    http://msdn.microsoft.com/en-us/magazine/cc301570.aspx
    Ludek
    Follow us on Twitter http://twitter.com/SAPCRNetSup

  • Drill with multiple Hierarchies

    Hi,
    I have defined multiple hierarchies in an OLAP universe (like state>region>customer>product or state>region>customer segmentation>Product or state>region>product ...) in order to use the drill functionnality in webi.
    In our scenario, each webi report should use only one hierarchy and we don't want the user to have the choice between the different hierarchies when he drills down. So is there a way to define in a webi report what hierarchy should be used?
    Thanks,
    Gabriel

    hi,
    As 'State' object is the starting point for both the Hierarchies,
    Please duplicate the state object and place it in other class. (as two objects with same name shouldn't exist in same class)
    Now edit  the second hierarchy such that new State Object will be the starting point.
    Also , please ensure that 2nd WEBI report uses new State Object in Query Pane.
    This will prevent 1st hierarchy in 2nd webi report.
    I tried this out and it's working.
    Regards,
    Vamsee

  • Using HLEVEL with multiple hierarchies

    Hi all,
    Is there a way to pass a parameter to the HLEVEL keyword to specifiy which hierarchy (Parent H1,H2, H3, etc.) to use when pulling the HLEVEL?
    We would like to use HLEVEL for report formatting however we need the ability to choose the hiearchy.
    Thanks!
    Mike

    Mike,
    please check the answer in this other post:
    EVPRO with multiple hierarchies
    It's for the MS platform, but it's the same for Netweaver.
    EVPRO can only retrieve the HLEVEL for the first hierarchy. You need to maintain further custom properties if you want to get the level of a member within multiple hierarchies.
    Regards,
    Simmaco

  • Multiple hierarchies with a shared higher level in OBIEE

    Hello all,
    I'm trying to create multiple hierarchies for a shared dimension in OBIEE. I have gotten these to work in the past when each hierarchy for the dimension all shares the common “grand total” level at the top, but I now I'd like multiple hierarchies that share a common higher level that isn't the grand total level.
    Here's what I'm trying to do with a Customer Geography hierarchy. I want to give the user the option to drill from the customer "Country" and go either into "Cities" or "States":
    Grand Total level
    --->Country level
    ------> State level
    ---------> Customer detail level
    ------> City level
    ---------> Customer detail level
    So "Country" is the common parent of "State" and "City", and "State" and "City" each have" Customer detail" as the lowest level. The Admin Tool let's me build exactly this in my RPD (with no errors/warnings), but when I go to drill on Country in an Answers report, I don't get the option to navigate down to State or City; it just automatically drills into the underlying states -- never shows cities.
    I guess I was hoping there'd be a pop up option to ask the user which path I wanted to drill down on (kind of like what shows up for multiple navigation targets in an Answers request).
    Am I missing a setup step in my RPD for this multiple hierarchy? Is a shared higher level multiple hierarchy even possible in OBIEE?
    Thanks,
    Jeremy
    Edited by: OBI Wan on Mar 19, 2009 3:29 PM
    Edited by: OBI Wan on Mar 19, 2009 3:30 PM
    Edited by: OBI Wan on Mar 19, 2009 11:20 PM

    Thanks mma for the help. I thought I saw in your reply this link as well to RittmanMead, but it's not showing up now?
    http://www.rittmanmead.com/files/Advanced%20Development%20using%20OBIEE%20(ODTUG%202008).pdf
    Anyway, on slide 37 of Rittman's presentation, that screen shot he has of Country, City, and State is exactly what I am attempting to do. I was hoping my issue would be a bit more straightforward than the recommended ragged hierarchy work arounds, but I may still have to do something like that in the end.
    This issue just seems more simple than ragged hierarchies, because I start from the same level and end up back at the exact same level (instead of different destination levels as can be the case in ragged hierarchies). I don't know -- maybe my example is ragged as well.
    If Rittman got that hierarchy in his screen shot on slide 37 to work like I'm trying to, then that would be perfect. :)

  • Hierarchical treeview structure in Reports

    Hi,
    I am working with an MNC, can anybody help me out by valuable guidelines in doing an hierarchical treeview structure in Reports.
    Your early response would b helpful to me.
    Bye
    Pavan

    HI
    see this site you wil find lots of examples
    http://www.sapdev.co.uk/reporting/alv/alvtree.htm
    The ALV tree report produces uses OBJECT METHOD functionality in-order to produce a
    tree structured ALV output.
    The creation of an ALVtree report first requires the creation of a simple program to build the ALV
    details such as the fieldcatalog and to call a screen which will be used to display the ALVTree.
    The screen should be created with a 'custom control' where you wish the ALVtree report to appear.
    For the following example it will have the name 'SCREEN_CONTAINER'.
    <b>Creation of Main Program code, Data declaration and screen call</b>
    *& Report  ZDEMO_ALVTREE                                               *
    *& Example of a simple ALV Grid Report                                 *
    *& The basic requirement for this demo is to display a number of       *
    *& fields from the EKPO and EKKO table in a tree structure.            *
                             Amendment History                           *
    REPORT  zdemo_alvgrid                 .
    *Data Declaration
    TABLES:     ekko.
    TYPE-POOLS: slis.                                 "ALV Declarations
    TYPES: BEGIN OF t_ekko,
      ebeln TYPE ekpo-ebeln,
      ebelp TYPE ekpo-ebelp,
      statu TYPE ekpo-statu,
      aedat TYPE ekpo-aedat,
      matnr TYPE ekpo-matnr,
      menge TYPE ekpo-menge,
      meins TYPE ekpo-meins,
      netpr TYPE ekpo-netpr,
      peinh TYPE ekpo-peinh,
    END OF t_ekko.
    DATA: it_ekko     TYPE STANDARD TABLE OF t_ekko INITIAL SIZE 0,
          it_ekpo     TYPE STANDARD TABLE OF t_ekko INITIAL SIZE 0,
          it_emptytab TYPE STANDARD TABLE OF t_ekko INITIAL SIZE 0,
          wa_ekko     TYPE t_ekko,
          wa_ekpo     TYPE t_ekko.
    DATA: ok_code like sy-ucomm,           "OK-Code
          save_ok like sy-ucomm.
    *ALV data declarations
    DATA: fieldcatalog  TYPE lvc_t_fcat WITH HEADER LINE.
    DATA: gd_fieldcat   TYPE lvc_t_fcat,
          gd_tab_group  TYPE slis_t_sp_group_alv,
          gd_layout     TYPE slis_layout_alv.
    *ALVtree data declarations
    CLASS cl_gui_column_tree DEFINITION LOAD.
    CLASS cl_gui_cfw DEFINITION LOAD.
    DATA: gd_tree             TYPE REF TO cl_gui_alv_tree,
          gd_hierarchy_header TYPE treev_hhdr,
          gd_report_title     TYPE slis_t_listheader,
          gd_logo             TYPE sdydo_value,
          gd_variant          TYPE disvariant.
    *Create container for alv-tree
    DATA: l_tree_container_name(30) TYPE c,
          l_custom_container        TYPE REF TO cl_gui_custom_container.
    *Includes
    *INCLUDE ZDEMO_ALVTREEO01. "Screen PBO Modules
    *INCLUDE ZDEMO_ALVTREEI01. "Screen PAI Modules
    *INCLUDE ZDEMO_ALVTREEF01. "ABAP Subroutines(FORMS)
    *Start-of-selection.
    START-OF-SELECTION.
    ALVtree setup data
        PERFORM data_retrieval.
        PERFORM build_fieldcatalog.
        PERFORM build_layout.
        PERFORM build_hierarchy_header CHANGING gd_hierarchy_header.
        PERFORM build_report_title USING gd_report_title gd_logo.
        PERFORM build_variant.
    Display ALVtree report
      call screen 100.
    *&      Form  DATA_RETRIEVAL
          Retrieve data into Internal tables
    FORM data_retrieval.
      SELECT ebeln
       UP TO 10 ROWS
        FROM ekko
        INTO corresponding fields of TABLE it_ekko.
      loop at it_ekko into wa_ekko.
        SELECT ebeln ebelp statu aedat matnr menge meins netpr peinh
          FROM ekpo
          appending TABLE it_ekpo
         where ebeln eq wa_ekko-ebeln.
      endloop.
    ENDFORM.                    " DATA_RETRIEVAL
    *&      Form  BUILD_FIELDCATALOG
          Build Fieldcatalog for ALV Report
    FORM build_fieldcatalog.
    Please not there are a number of differences between the structure of
    ALVtree fieldcatalogs and ALVgrid fieldcatalogs.
    For example the field seltext_m is replace by scrtext_m in ALVtree.
      fieldcatalog-fieldname   = 'EBELN'.           "Field name in itab
      fieldcatalog-scrtext_m   = 'Purchase Order'.  "Column text
      fieldcatalog-col_pos     = 0.                 "Column position
      fieldcatalog-outputlen   = 15.                "Column width
      fieldcatalog-emphasize   = 'X'.               "Emphasize  (X or SPACE)
      fieldcatalog-key         = 'X'.               "Key Field? (X or SPACE)
    fieldcatalog-do_sum      = 'X'.              "Sum Column?
    fieldcatalog-no_zero     = 'X'.              "Don't display if zero
      APPEND fieldcatalog TO gd_fieldcat.
      CLEAR  fieldcatalog.
      fieldcatalog-fieldname   = 'EBELP'.
      fieldcatalog-scrtext_m   = 'PO Iten'.
      fieldcatalog-outputlen   = 15.
      fieldcatalog-col_pos     = 1.
      APPEND fieldcatalog TO gd_fieldcat..
      CLEAR  fieldcatalog.
      fieldcatalog-fieldname   = 'STATU'.
      fieldcatalog-scrtext_m   = 'Status'.
      fieldcatalog-outputlen   = 15.
      fieldcatalog-col_pos     = 2.
      APPEND fieldcatalog TO gd_fieldcat..
      CLEAR  fieldcatalog.
      fieldcatalog-fieldname   = 'AEDAT'.
      fieldcatalog-scrtext_m   = 'Item change date'.
      fieldcatalog-outputlen   = 15.
      fieldcatalog-col_pos     = 3.
      APPEND fieldcatalog TO gd_fieldcat..
      CLEAR  fieldcatalog.
      fieldcatalog-fieldname   = 'MATNR'.
      fieldcatalog-scrtext_m   = 'Material Number'.
      fieldcatalog-outputlen   = 15.
      fieldcatalog-col_pos     = 4.
      APPEND fieldcatalog TO gd_fieldcat..
      CLEAR  fieldcatalog.
      fieldcatalog-fieldname   = 'MENGE'.
      fieldcatalog-scrtext_m   = 'PO quantity'.
      fieldcatalog-outputlen   = 15.
      fieldcatalog-col_pos     = 5.
      APPEND fieldcatalog TO gd_fieldcat..
      CLEAR  fieldcatalog.
      fieldcatalog-fieldname   = 'MEINS'.
      fieldcatalog-scrtext_m   = 'Order Unit'.
      fieldcatalog-outputlen   = 15.
      fieldcatalog-col_pos     = 6.
      APPEND fieldcatalog TO gd_fieldcat..
      CLEAR  fieldcatalog.
      fieldcatalog-fieldname   = 'NETPR'.
      fieldcatalog-scrtext_m   = 'Net Price'.
      fieldcatalog-outputlen   = 15.
      fieldcatalog-col_pos     = 7.
      fieldcatalog-datatype     = 'CURR'.
      APPEND fieldcatalog TO gd_fieldcat..
      CLEAR  fieldcatalog.
      fieldcatalog-fieldname   = 'PEINH'.
      fieldcatalog-scrtext_m   = 'Price Unit'.
      fieldcatalog-outputlen   = 15.
      fieldcatalog-col_pos     = 8.
      APPEND fieldcatalog TO gd_fieldcat..
      CLEAR  fieldcatalog.
    ENDFORM.                    " BUILD_FIELDCATALOG
    *&      Form  BUILD_LAYOUT
          Build layout for ALV grid report
    FORM build_layout.
      gd_layout-no_input          = 'X'.
      gd_layout-colwidth_optimize = 'X'.
      gd_layout-totals_text       = 'Totals'(201).
    gd_layout-totals_only        = 'X'.
    gd_layout-f2code            = 'DISP'.  "Sets fcode for when double
                                            "click(press f2)
    gd_layout-zebra             = 'X'.
    gd_layout-group_change_edit = 'X'.
    gd_layout-header_text       = 'helllllo'.
    ENDFORM.                    " BUILD_LAYOUT
    *&      Form  build_hierarchy_header
          build hierarchy-header-information
         -->P_L_HIERARCHY_HEADER  structure for hierarchy-header
    FORM build_hierarchy_header CHANGING
                                   p_hierarchy_header TYPE treev_hhdr.
      p_hierarchy_header-heading = 'Hierarchy Header'(013).
      p_hierarchy_header-tooltip = 'This is the Hierarchy Header !'(014).
      p_hierarchy_header-width = 30.
      p_hierarchy_header-width_pix = ''.
    ENDFORM.                               " build_hierarchy_header
    *&      Form  BUILD_REPORT_TITLE
          Build table for ALVtree header
    <->  p1        Header details
    <->  p2        Logo value
    FORM build_report_title CHANGING
          pt_report_title  TYPE slis_t_listheader
          pa_logo             TYPE sdydo_value.
      DATA: ls_line TYPE slis_listheader,
            ld_date(10) TYPE c.
    List Heading Line(TYPE H)
      CLEAR ls_line.
      ls_line-typ  = 'H'.
    ls_line-key     "Not Used For This Type(H)
      ls_line-info = 'PO ALVTree Display'.
      APPEND ls_line TO pt_report_title.
    Status Line(TYPE S)
      ld_date(2) = sy-datum+6(2).
      ld_date+2(1) = '/'.
      ld_date3(2) = sy-datum4(2).
      ld_date+5(1) = '/'.
      ld_date+6(4) = sy-datum(4).
      ls_line-typ  = 'S'.
      ls_line-key  = 'Date'.
      ls_line-info = ld_date.
      APPEND ls_line TO pt_report_title.
    Action Line(TYPE A)
      CLEAR ls_line.
      ls_line-typ  = 'A'.
      CONCATENATE 'Report: ' sy-repid INTO ls_line-info  SEPARATED BY space.
      APPEND ls_line TO pt_report_title.
    ENDFORM.
    *&      Form  BUILD_VARIANT
          Build variant
    form build_variant.
    Set repid for storing variants
      gd_variant-report = sy-repid.
    endform.                    " BUILD_VARIANT
    <b>Creation of 'INCLUDES' to store ALVtree code</b>
    Three includes need to be created in-order to store the ABAP code required for the ALVtree report.
    Typically these will be one for the PBO modules, one for PAI modules and one for the subroutines(FORMs):
       *Includes
        include zdemo_alvtreeo01. "Screen PBO Modules
        include zdemo_alvtreei01. "Screen PAI Modules
        include zdemo_alvtreef01. "ABAP Subroutines(FORMS)
    If you are using the code provide within the ALVtree section of this web site simply create the includes by
    un-commenting the 'Includes' section within the code(see below) and double clicking on the name
    i.e. 'zdemo_alvtreeo01'. Obviously these can be renamed.
    *Includes
    *include zdemo_alvtreeo01. "Screen PBO Modules
    *include zdemo_alvtreei01. "Screen PAI Modules
    *include zdemo_alvtreef01. "ABAP Subroutines(FORMS)
    *Start-of-selection.
    start-of-selection.
    <b>Create Screen along with PBO and PAI modules for screen</b>
    The next step is to create screen 100, to do this double click on the '100' within the call screen
    command(Call screen 100.). Enter short description and select 'Normal' as screen type.
    To create the PBO and PAI modules insert that code below into the screen's flow logic. Much of this code
    should automatically have been inserted during screen creation but with the module lines commented out.
    Simple remove the comments and double click the module name(STATUS_0100 and
    USER_COMMAND_0100) in-order to create them, this will display the perform/module creation screen.
    The MODULES are usually created within two includes one ending in 'O01' for PBO modules and
    one ending in 'I01' for PAI modules(See code below).
    Please note in order for these includes to be displayed on the creation screen they need to have be
    created along with the following lines of code added to the main prog(see previous step):
                                     INCLUDE ZDEMO_ALVTREEO01. "Screen PBO Modules
                                     INCLUDE ZDEMO_ALVTREEI01. "Screen PAI Modules
    Otherwise use the 'New Include' entry and SAP will add the necassary line for you.
    Screen flow logic code
    PROCESS BEFORE OUTPUT.
    MODULE STATUS_0100.
    PROCESS AFTER INPUT.
    MODULE USER_COMMAND_0100.
    ***INCLUDE Z......O01 .
    *&      Module  STATUS_0100  OUTPUT
          PBO Module
    module status_0100 output.
    SET PF-STATUS 'xxxxxxxx'.
    SET TITLEBAR 'xxx'.
    endmodule.                 " STATUS_0100  OUTPUT
    ***INCLUDE Z......I01 .
    *&      Module  USER_COMMAND_0100  INPUT
          PAI Module
    module user_command_0100 input.
    endmodule.                 " USER_COMMAND_0100  INPUT
    <b>Define OK CODE(SY-UCOMM) variable</b>
    In order to define the OK CODE you must fist declare a variable of type SY-UCOM and then insert this
    variable into the OK code declaration within the element list (see screen shot below). If you have used
    the code contained on the iwebsite the ok code should already have been declared as OK_CODE.
              i.e. OK_CODE like sy-ucom.
    Note: there is also a variable called SAVE_OK, it is good practice to store the returned ok code into
    a work area as soon as you enter the PAI processing.
    <b>Add screen control to PAI module(INCLUDE Z......I01)</b>
    The following code adds simple screen control to the report and whenever the user presses the cancel,
    exit or back icon they will exit from the report. It also processes the ALVtree user interactions within the
    'others' case statement
       INCLUDE Z......I01                                                *
    *&      Module  USER_COMMAND_0100  INPUT
          text
    module user_command_0100 input.
      DATA return TYPE REF TO cl_gui_event.
      save_ok = ok_code.
      case ok_code.
        when 'BACK' or '%EX' or 'RW'.
        Exit program
          leave to screen 0.
      Process ALVtree user actions
        when others.
          call method cl_gui_cfw=>get_current_event_object
                  receiving
                     event_object = return.
          call method cl_gui_cfw=>dispatch.
      endcase.
    endmodule.                 " USER_COMMAND_0100  INPUT
    <b>Create pf-status</b>
    In order to created the pf-status for the screen you need to un-comment '*  SET PF-STATUS 'xxxxxxxx'
    and give it a name.
                   i.e.   SET PF-STATUS 'STATUS1'.
    Step 1
    Now double click on 'STATUS1' in-order  to create the pf-status. Enter short text, select status type as
    'Online status' and click save.
    Step2
    You should now be presented with the status creation screen. Choose 'Adjust template' from the Extras menu
    (4.6 onwards only).
    Step 3
    Now select 'List status' and click the green tick (see below).
    Step 3
    All the basic menu bars/buttons should now have been entered. Now click save then activate. The
    pf-status has now been completed.
    Once you have the main program code in place to call the screen which will display the
    ALVtree, you now need to setup the actual ALVtree and populate it. As this is screen
    based(dialog) the display coding will be performed within the PBO screen module.
    Therefor you need to add the following processes to the PBO(STATUS_0100) module
    of the screen.
    <b>Create Custom control</b>
    Via screen painter insert 'custom control' on to screen and give it the name 'SCREEN_CONTAINER'. This is
    the possition the ALVtree will appear so align appropriately.
    http://www.sapdev.co.uk/reporting/alv/alvtree/alvtree_basic.htm
    see this site you wil find lots of examples
    http://www.sapdev.co.uk/reporting/alv/alvtree.htm
    <b>Reward if usefull</b>

  • Query selected levels of multiple hierarchies of one dimension

    Hi to all.
    I have created through AWM 11 a customer dimension with two hierarchies as follows.
    SLM_HIER: All Customers -> Salesman -> Customer
    GEO_HIER: All Customers -> State -> City -> Customer
    I have also created a SALES_CUBE (measures: QUANTITY, VALUE, aggregation: SUM) that is dimensioned with Customer dim.
    I'm using OBIEE to query the OLAP engine (through the relational views that AWM created automatically). I have followed the OTN OBE tutorials.
    I would like to have the following query on the cube:
    Give me QUANTITY where SALESMAN=S1 and CITY in ('Athens','Rome').
    Is it possible to have such a query? As far as I understand there are no ready aggregated data for selected levels of both hierarchies.
    Thank you very much.
    Chris

    I think OBIEE would also give you your answer from OLAP.
    This query has filters defined from both the hierarchies and hence OBIEE would (should) automatically service this query from the highest common level b/w the hierarchies (in this case: base/leaf level - Customer). As a result of this, if CUST is your Customer dimension, OBIEE (at least, the older style of obiee modeling with olap) would introduce the security filter CUST_LEVEL = 'Customer'. Granularity of the resultset returned would be per individual Customer. 1 record per Customer satisfying the criteria SALESMAN='S1' and CITY in ('Athens','Rome').
    Ideally you should include the Cust Id, Quantity columns in your obiee answers report and use an internal answers object/view like a Pivot View to hide Customer details column and get a localized aggregation performed over the resultset returned from OLAP to get the consolidated Quantity. Answers table has data at Customer level, Answers Pivot can show the required result.
    Note1: The Cube cannot have this result pre-calculated since its a contradictory combination of filters across hierarchies. Level specific aggregate values calculated (or pre-calculated) in the cube for Salesman level (h1) would contain Customers from all cities (h2) and similarly City level (h2) Aggregates would contain Customers of all Salesmen (h1).
    Note2: I believe OBIEE modeling with OLAP suffers from some issues relating to multiple hierarchies (e.g: if you have filter from non-default hierarchy CITY in ('Athens','Rome') alone, i think it would still fetch the results from lowest common level Customer instead of from City level directly).
    HTH
    Shankar

  • Multiple hierarchies in one dimesion

    Hi all,
    I am new in using AWM. I have problem when using two hierarchies in one dimension. This is sample of dimension.
    A
    ---+B
    -----+B1
    -------+B2
    ---------+B3
    ---+C
    -----+C1
    -------+C2
    ---------+C3
    Dimension is A and it has two hierarchies B and C. Maintaining the cube is succesfull. But when "add" this cube in OBIEE and try to make request using B1 and C1 we are getting error. How we can have mulitple hierarchies in one dimension and combine columns from hierarchies? We are using database 11g, AWM 11.2.0.2 and OBIEE 10.1.3.4.
    Thanks all

    Maybe you need to join the generic dimension view A_VIEW with the fact-cube view in the physical layer of rpd on the basis of the key corresponding to the (common) lowest level of the dimension.
    Regd your dimension hierarchy setup:
    A
    ---+B
    -----+B1
    -------+B2
    ---------+B3
    ---+C
    -----+C1
    -------+C2
    ---------+C3It looks like you have column/level B3 as leaf level of hierarchy B and C3 as leaf level of hierarchy C.
    Is this distinction piurely logical and the same physical column is used to represent both B3 and C3?
    Then A_VIEW and Fact view should be joined on basis of this single common level key column.
    Generally a dimension A with multiple hierarchies B and C will work fine when you have a common lowest level D, say, which acts as the leaf level for both hierarchies of the dimension.
    Can you model the hierarchy as
    A
    ---+B
    -----+B1
    -------+B2
    ---------+B3
    -----------+D
    ---+C
    -----+C1
    -------+C2
    ---------+C3
    -----------+D                             NOTE1: Same level/column D acts as leaf level of Hierarchy B as well as Hierarchy C. We should not use 2 different columns D1 and D2 even if they contain the same data
    NOTE2: Dimension A is joined to Fact F1 via level/column D.
    In that case, you can issue a query against Fact F1 which uses both level columns B and C from different hierarchies of A against a measure defined in Fact table F1.
    You can even add a filter (where clause) on columns B/C/both B and C as required.
    Result will be at the granularity of level D (not summarized to either level B along HI_B hierarchy or level C along HI_C hierarchy) -- 1 record per distinct member at Level D of default hierarchy with the corresponding values for columns B and C available as part of the output since they are ancestor fields and availble at level D. A smart reporting tool like OBIEE or BO can even exclude the column corresponding to D locally within a pivot and create ad-hoc, report level, pivot table based local summaries (aggregated results for each combination of values in columns B and C).
    HTH

Maybe you are looking for