BW Hierarchy Vs BO Universe Hierarchy

Hi,
Can any one tell which one is the better one to create hierarchy in BW and use it in BEX based universe or direclty creating the hierarchy in BO Universe.
Thanks in Advance for giving the answers.
Thanks,
Dru

Hi.
It depends on what you are going to do with this hierarchy.
But as I know hierarchies in BO still have no such functionality as BW hierarchy.
Regards.

Similar Messages

  • Select key date of time-dependent hierarchy before select a hierarchy node

    Hello experts!
    I have a Web Application which has a selection on 0ORGUNIT (organizational unit). The selection is on hierarchy nodes and the hierarchy is time-dependent.
    Because of the time-dependency I have to give a key date for the hierarchy. But I want to select the key date at runtime/execution of the query and additionally I want to select the hierarchy node and other selection criterias.
    Maybe there is a solution to get all this in one pop-up or maybe in two or another solution how I can implement this requirement.
    Thanks for help!
    Peter

    Hey!
    You don't have to use the same presentation-hierarchy like  the selection-hierarchy is which you use for the variable. While presentation-hierarchy always has a key-date, the selection-hierarchy has none. So you see all values for selection but just this which are valid for the presentation-hierarchy are selected. And there is a warning which you can supress over RSRT.
    This solution works for our problem, maybe not for yours, don't know.
    Best regards,
    Peter

  • Infoobject contains whole hierarchy query contains partialy hierarchy

    hi experts,
    in BI3.5 when loading hierarchy to an Infoobject I get only part of it in the BEX query
    the att/hier change run is empty
    how can i see the whole hierarchy in bex query
    thanks
    nir

    Hi Nir,
    Check the setting for expand to level  in the hierarchy property of the characteristic in the query .
    You can also check the corresponding hierarchy in RSH1 in hierarchy attributes the drill down start level.
    [ Go to Hierarchy parameter in this link for characteristic properties|http://help.sap.com/saphelp_nw70/helpdata/en/1a/25213c9cffa027e10000000a11402f/content.htm]
    Hope this helps,
    Best regards,
    Sunmit.

  • Ragged Hierarchy and Skip Level Hierarchy

    Hi all,
    I am confused with ragged and skip level hierarchy, as i read some documents related to obiee 11g.
    Will you please explain with an example the difference between ragged hierarchy and skip level hierarchy and also when to use these hierarchies?
    regards
    chandra kanth.

    Chandra Kanth,
    Hope this helps you
    http://blogs.simba.com/.a/6a00e3932f172e88340133f4d758b5970b-800wi
    Thanks,
    Saichand.v

  • Profit center hierarchy and cost center hierarchy

    Hi
    What are the things we have to consider to create Profit center hierarchy and cost center hierarchy  and what is the need to assign profit center hierarchy to profit center and cost center hierarchy to cost center. What levels does this fall into? Can some one please guide me.
    Thanks.

    As you would for any other infoobject
    Activate the business content hierarchy datasources on R3 for cost centre and profit centre
    Go into BW - replicate the metadata
    Then just connect via transformations or transfer rules the datasources to yoru infosources or master data objects
    Create an infopackage per hierarchy!!!!! - press the button available hirachies from OLTP - click the one you want on the left - fire it off
    Then repeat new infopackages for all hierachies

  • Hierarchy structure with temporal hierarchy join

    Hi guys,
    For characteristic Cost Element, I’m using a time dependant hierarchy structure with temporal hierarchy join. In the query, I’m selecting “select hierarchy” and “From data, derivation”.
    If the hierarchy is created in SAP BI or if the hierarchy is imported from Excel, query is working properly.
    If the hierarchy is imported from SAP ECC, the query giving me an error:
    ABEND BRAIN (336): Hierarchy "xx" from characteristic 0COSTELMNT can be used here
    Someone can tell me if it’s normal or if there is a way in order to correct this problem.
    Thanks in advance,
    Rubé

    Hi guys,
    For characteristic Cost Element, I’m using a time dependant hierarchy structure with temporal hierarchy join. In the query, I’m selecting “select hierarchy” and “From data, derivation”.
    If the hierarchy is created in SAP BI or if the hierarchy is imported from Excel, query is working properly.
    If the hierarchy is imported from SAP ECC, the query giving me an error:
    ABEND BRAIN (336): Hierarchy "xx" from characteristic 0COSTELMNT can be used here
    Someone can tell me if it’s normal or if there is a way in order to correct this problem.
    Thanks in advance,
    Rubé

  • Hierarchy level for Site hierarchy idoen't load in BI

    Hi gurus,
    I have created a new hierarchy level for Site hierarchy in transaction CL01 in R/3. But this level is not load in BI.
    Site hierarchy and other levels load right, but no the new one.
    Do you now anything to resolve my issue?
    Any feedback will be really appreciated.
    Thanks

    Hi,
    I think,you have to follow the old concept only.
    Gana.

  • How to: from time independent hierarchy to time dependent hierarchy in BW

    Hello goeroes outthere,
    I am facing the following problem and was wondering if some of you have faced the same issue.
    In ECC we have a time independent hierarchy on Profit Center. Our customer wants to perform time DEPENDENT reporting in BW.
    As the standard datasource does not support to be loaded via PSA in the datasource definition (only IDOC) we cannot enhance the datasource with fields such as DATEFROM and DATETO. I've tried doing so but this results in the following error message when loading : Selected number does not agree with transferred number of records.
    So I have cancelled out this as being an option.
    I am analyzing the following two options :
    1. Making the hierarchy time dependent. (globally). The idea would be to create a custom ABAP program that would copy the loaded hierarchy to a hierarchy in which we define the datefrom as the actual system date and the dateto as 31.12.9999.
    Prior to doing so the abap program should change the already loaded hierarchy by modifying the dateTO as actual system date -1 in the header of the hierarchy.
    In theory this seems to be a good option, but I am afraid of the complexity of the ABAP program to be created by looking in debug how the copying process is handled in SAP. 
    2. Making the hierarchy structure TIme dependant. THis has as a consequence that the table  /BI0/HPROFIT_CTR is adjusted to include DATETO and DATEFROM fields. A custom program could read the entries and perform the same activities as described above. So meaning finding and modifying the existing entries with DATETO fields with as an entry 31.12.9999 to adjust to sysdatum -1 and modfying all entries that don't have dateto and datefrom entries by putting datefrom (=sysdate) and the dateto (=31.12.9999).
    The issue here is that first we need to find the link between the hierarchy ID and the Hierarchy loaded and that I am not sure how SAP will deal with this SID wise.
    Option 1 seems feasable as the hierarchy does'nt change every single day and doesn't require to be loaded every single day. But before going in this direction, I would appreciate some confirmation of my approach.
    Thanks in advance for sharing your lights on this topic.
    Rgds,
    Bvpe

    Hi Bart,
    I just solved this very problem today in a two step process:
    In our implementation, we only want to control when a new version of the hierarchy is created.  If nothing changes, whatever is brought in from the source system will just replace the current version.  We imagine we'll only create versions at month end or major re-organization.
    1) I created a Select Options variable in tcode: stvarv called ZPROFCTR_FROMDATE.  I added a value to the low position and set the option to equals.
    2) Open the infoPackage that is used to load the hierachy from the source system.  Go to the Hierarchy Selection Tab and click on the button at the bottom of the tabbed frame "Dynamic Hierarchy Selections".
    You should see two check boxes, place a check in the second box: "Determine Using Routine"  Click on the create icon and put this in the routine
      p_s_sel_hier = l_s_presel_hier.
      data: tempfrom type tvarv_val.
      select single low
      from tvarvc
      into tempfrom
      where name = 'ZPROFCTR_FROMDATE'.
      move tempfrom to p_s_sel_hier-datefrom.
      p_s_sel_hier-dateto = '99991231'.
      clear p_subrc.
    I've include the entire subroutine for context, and so you can see the SAP generated coments in the form that attempt to explain what the form is going to do.
    Long story short, the hierarchy you have selected with the radio button on the Hierarchy Selection tab will be the one that is affected by this logic.
    form compute_hier
      tables l_t_all_hier structure rshiertrsf
      using l_s_presel_hier like rshiertrsf
            l_infopackage   type rslogdpid
      changing p_s_sel_hier like rshiertrsf
               p_subrc like sy-subrc.
    *Insert Source Code to decide which Hierarchy shall be loaded.
    *The Hierarchy you select from table l_t_all_hier and fill
    *into p_s_sel_hier will be loaded.
    *The Structure l_s_presel_hier contains the pre-selection of the
    *BW-Scheduler - just to inform you what the BW wll load
    *if you change nothing.
    *$*$ begin of routine - insert your code only below this line        *-*
      p_s_sel_hier = l_s_presel_hier.
      data: tempfrom type tvarv_val.
      select single low
      from tvarvc
      into tempfrom
      where name = 'ZPROFCTR_FROMDATE'.
      move tempfrom to p_s_sel_hier-datefrom.
      p_s_sel_hier-dateto = '99991231'.
      clear p_subrc.
    *$*$ end of routine - insert your code only before this line         *-*
    endform.                    "compute_hier
    Hope this helps,
    Quack

  • Allow user to type in the Hierarchy node value in Hierarchy node varaible

    Hi Experts,
    We are presently on NW2004s SP8 and we are moving on to SP10.
    We got the requirement in reporting...
    1.To allow the user to type in the Hierarchy node value in Hierarchy node variable manually.
    2. When user typing the Hierarchy node value into the Variable prompt, bring subtree by default.
    By default Hierarchy node variable prompt is grayed out and the user can only select the values from Input help(F4).
    I have put forward an SAP message on this topic earlier and got a reply that the manual entry of hierarchy node is not possible and there is no work around. User needs to select it from HELP. This is because the node value must be in a certain format which the users may not know.
    I just want to know from u Experts... is there any new feature available in SP09/10 or is there any other way to satisfy this requirement ?
    Thanks in Advance.
    Regards,
    Aparna

    We are able to manually enter in a hierarchy node in the selection screen.  The selection screen is not grayed out. 
    We are currently on SPS 009, but one difference could be that we are on a Bex 3.5 Patch 10 front end.

  • Create hierarchy - Don't see hierarchy node??

    Dear all,
    I am doing an example so as to create hierarchy
    I created the following:
    infoobject io_srep (sales representative id) - under the hierarchy tab -> "with hierarchies" is checked and "Hierarchy structure time-dependent" radio button is selected).
    (ii) infoobjet io_sreg (sales region) - that contains regions master data, 'East, Midwest etc)
    (iii) now right click io_srep -> chose create hierarchy -> name given as io_srep_hier with a short desc -> click contiune -> in the next screen i don't see any hierarchy node. I do see at the right hand side title column as IO_SREP hierarchy and time column but i don't see any node below that.
    I thought that i would see one node as "IO_SREP hierarchy" under the IO_SREP hierarchy column.
    What i am missing to do? How can i proceed with this?   
    I appreciate your guidance and help.
    Thanks.
    AK

    1) IN HIERARCHY TAB OF INFOOBJ IO_SREP
    CLICK EXTERNAL CHARS. IN HIERARCHIES AND Please make sure THAT IO_SREG AND IO_SOFF ARE MOVED INTO EXTERNAL CHARACTERISTICS COLUMN.
    2) IN AWB RIGHT CLICK ON IO_SREP AND SELECT CREATE HIERARCHY.
    3) IN HIERARCHY CHANGE MODE
    IN THE MENU GOTO EDIT->CREATE TEXT NODE
    PROVIDE THE DESCRIPTION IO_SREP HIERARCHY
    THE FOLDER STRUCTURE APPEARS
    RIGHT CLICK ON THE FOLDER AND SELECT INSERT CHARACTERISTIC NODE
    SELECT IO_SREG AND SELECT THE REQUIRED REGIONS.
    RIGHT CLICK ON THE SPECIFIC REGION AND SELECT INSERT CHARACTERISTIC NODE AND SELECT IO_SOFF
    hope this will be helpful.

  • Navigation to find " Employee based hierarchy or Position Based Hierarchy "

    Hi Experts,
    Please let me know
    Navigation to find Employee based hierarchy or Position Based Hierarchy.
    regds
    MRR

    Setup-->Financial Options-->Human Resources tab -->Use Approval Hierarchies check box. If you check uses approval hierarchies based on positions if not uses the employee hierarchy (supervisor in employee).
    Thanks
    Nagamohan

  • 0WBS_ELEMT hierarchy through MDX universe populating random values in WebI

    Hi Experts,
    We are facing an issue in WebI 3.1, while creating a report on top of MDX universe with 0WBS_ELEMT hierarchy - coming from BEx query. All other hierarchies in other reports are working fine, but the issue seems to be particular to 0WBS_ELEMT hierarchy.
    First of all, the WebI does not includes full project entries along with WBS hierarchy - this could be a limitation (2nd comment in https://cw.sdn.sap.com/cw/ideas/2084#comment-14280), and we found workaround as to display in seperate block.
    Now the actual issue is, even hierarchy nodes of WBS element are not coming properly in the WebI. There are 5 nodes in universe (L00 to L04). We dragged all of them into the report and found that some nodes are missing. These are the L01 nodes which are not having any subordinate nodes.
    Tried different combitions, and later found that if we are not keeping the nodes L02 to L04 in the query, all missing entries (in first report) are coming, but now some other nodes are getting dissapeared.
    Can anyone tell the reason and/or solution for the issue. Is this the known issue with 0WBS_ELEMT hierarchy? If so, what SAP is recommending for this? This is really urgent, reply.
    Regards,
    Kshiteesh

    Hi Henry,
    Thanks for reply.
    We are on BI 7.1 SP 07. We are having other hierarchies working in expected manner, but only WBS element hierarchy is having issue.
    After posting to SDN, I saw some other posts on the forum and checked the note 1446246. This note points to others notes, and 2 notes (0001562173 - flattening unbalanced hierarchies & 1432162 - MDX Flattening problems when using hierarchies) which seems to be relevant.
    It seems to be case of unbalanced hierarchies, but to be sure please suggest if we can go with these notes.
    Regards,
    Kshiteesh

  • WEBI above universe - hierarchy restriction

    Hello,
    I read that the authorization concept in WEBI above universe works if we build a universe above a query and we use authorization variable. But what is the case for restriction by a hierarchy? For this restriction in the Query designer there is no need for authorization variable. Is it also possible in the WEBI?
    Thanks,
    David

    Hi David,
    are you referring to a hierarchy node authorization ? so that should work via the query automatically as well.
    ingo

  • BW Hierarchy imported into Universe

    We are importing our PVA Cost Allocations cube into a Web Intelligence Universe. When that information comes across we have all of our data elements including the hiearchy master data for items such as cost element, cost center, etc. When you display the hierarchy, it breaks it down into 7 levels with the expansion underneath for attributes. They are not logical levels as the hierarchy is displayed in BW though. You basically have to pull in the entire thing and start drilling into it to see what is there. They group things together that fall in the same relative place in the hierarchy. This will not work. How is this typically done? I would assume hierarchies from R/3 and BW are leveraged all the time.

    Hi.
    It depends on what you are going to do with this hierarchy.
    But as I know hierarchies in BO still have no such functionality as BW hierarchy.
    Regards.

  • Dynamic hierarchy in parent child hierarchy table??

    Do you have any experience to handle the requirement of dynamic hierarchy in universe/webi?
    We have some data in parent child hierarchy as below u201CCustomeru201D table.
    Customer
    Parent          Child
    Z                  A
    Z                  B
    A                  AA
    B                  BB
    AA               AAA
    For example, Company Z is the parent company of Company A.
    Another table, Amount is the amount value of different Customers.
    Amount
    ID               Amt
    AA               10
    AAA            1
    BB                2
    Is there any functionality in Universe designer to build related Classes and objects, So that the web intelligence documents represent the following report with the drilling results?
    When we want to see the ID and Amt, the expected result should be:
    Z                13
    when we drill down Z
    the result should be:
    A                11
    B                2
    when we drill down A:
    the result should be:
    AA              11
    notes **
    the level of hierarchy is dynamic
    Any suggestion is appreciated.  Thanks.

    Hi,
    The only way to do it is to create recursive derived table that flatten you parent child hierarchy with a given maximum depth.
    Here is a sample I built a long time ago to flatten a parent-child hierarchy on Employees table in Foodmart database (SQL Server).
    Didier
    SELECT DISTINCT
         Z.employee_id,
         A.supervisor_id_1,
         A.employee_id_1,
         A.full_name_1,
         A.supervisor_id_2,
         A.employee_id_2,
         A.full_name_2,
         A.supervisor_id_3,
         A.employee_id_3,
         A.full_name_3,
         A.supervisor_id_4,
         A.employee_id_4,
         A.full_name_4,
         A.supervisor_id_5,
         A.employee_id_5,
         A.full_name_5,
         A.supervisor_id_6,
         A.employee_id_6,
         A.full_name_6,
         Z.supervisor_id AS supervisor_id_7,
         Z.employee_id AS employee_id_7,
         Z.full_name AS full_name_7
    FROM employee Z,
         SELECT DISTINCT
              A.supervisor_id_1,
              A.employee_id_1,
              A.full_name_1,
              A.supervisor_id_2,
              A.employee_id_2,
              A.full_name_2,
              A.supervisor_id_3,
              A.employee_id_3,
              A.full_name_3,
              A.supervisor_id_4,
              A.employee_id_4,
              A.full_name_4,
              A.supervisor_id_5,
              A.employee_id_5,
              A.full_name_5,
              Z.supervisor_id AS supervisor_id_6,
              Z.employee_id AS employee_id_6,
              Z.full_name AS full_name_6
         FROM employee Z,
              SELECT DISTINCT
                   A.supervisor_id_1,
                   A.employee_id_1,
                   A.full_name_1,
                   A.supervisor_id_2,
                   A.employee_id_2,
                   A.full_name_2,
                   A.supervisor_id_3,
                   A.employee_id_3,
                   A.full_name_3,
                   A.supervisor_id_4,
                   A.employee_id_4,
                   A.full_name_4,
                   Z.supervisor_id AS supervisor_id_5,
                   Z.employee_id AS employee_id_5,
                   Z.full_name AS full_name_5
              FROM employee Z,
                   SELECT DISTINCT
                        A.supervisor_id_1,
                        A.employee_id_1,
                        A.full_name_1,
                        A.supervisor_id_2,
                        A.employee_id_2,
                        A.full_name_2,
                        A.supervisor_id_3,
                        A.employee_id_3,
                        A.full_name_3,
                        Z.supervisor_id AS supervisor_id_4,
                        Z.employee_id AS employee_id_4,
                        Z.full_name AS full_name_4
                   FROM employee Z,
                        SELECT DISTINCT
                             A.supervisor_id_1,
                             A.employee_id_1,
                             A.full_name_1,
                             A.supervisor_id_2,
                             A.employee_id_2,
                             A.full_name_2,
                             Z.supervisor_id AS supervisor_id_3,
                             Z.employee_id AS employee_id_3,
                             Z.full_name AS full_name_3
                        FROM employee Z,
                             SELECT DISTINCT
                                  A.supervisor_id_1,
                                  A.employee_id_1,
                                  A.full_name_1,
                                  Z.supervisor_id AS supervisor_id_2,
                                  Z.employee_id AS employee_id_2,
                                  Z.full_name AS full_name_2
                             FROM employee Z,
                                  SELECT DISTINCT
                                       supervisor_id AS supervisor_id_1,
                                       employee_id AS employee_id_1,
                                       full_name AS full_name_1
                                   FROM employee
                                   WHERE supervisor_id = 0 OR supervisor_id IS NULL
                             ) A
                             WHERE A.employee_id_1 = Z.supervisor_id
                        ) A
                        WHERE A.employee_id_2 = Z.supervisor_id
                   ) A
                   WHERE A.employee_id_3 = Z.supervisor_id
              ) A
              WHERE A.employee_id_4 = Z.supervisor_id
         ) A
         WHERE A.employee_id_5 = Z.supervisor_id
    ) A
    WHERE A.employee_id_6 = Z.supervisor_id
    UNION
    SELECT DISTINCT
         A.employee_id_6 AS employee_id,
         A.supervisor_id_1,
         A.employee_id_1,
         A.full_name_1,
         A.supervisor_id_2,
         A.employee_id_2,
         A.full_name_2,
         A.supervisor_id_3,
         A.employee_id_3,
         A.full_name_3,
         A.supervisor_id_4,
         A.employee_id_4,
         A.full_name_4,
         A.supervisor_id_5,
         A.employee_id_5,
         A.full_name_5,
         A.supervisor_id_6,
         A.employee_id_6,
         A.full_name_6,
         NULL AS supervisor_id_7,
         NULL AS employee_id_7,
         NULL AS full_name_7
    FROM employee Z,
         SELECT DISTINCT
              A.supervisor_id_1,
              A.employee_id_1,
              A.full_name_1,
              A.supervisor_id_2,
              A.employee_id_2,
              A.full_name_2,
              A.supervisor_id_3,
              A.employee_id_3,
              A.full_name_3,
              A.supervisor_id_4,
              A.employee_id_4,
              A.full_name_4,
              A.supervisor_id_5,
              A.employee_id_5,
              A.full_name_5,
              Z.supervisor_id AS supervisor_id_6,
              Z.employee_id AS employee_id_6,
              Z.full_name AS full_name_6
         FROM employee Z,
              SELECT DISTINCT
                   A.supervisor_id_1,
                   A.employee_id_1,
                   A.full_name_1,
                   A.supervisor_id_2,
                   A.employee_id_2,
                   A.full_name_2,
                   A.supervisor_id_3,
                   A.employee_id_3,
                   A.full_name_3,
                   A.supervisor_id_4,
                   A.employee_id_4,
                   A.full_name_4,
                   Z.supervisor_id AS supervisor_id_5,
                   Z.employee_id AS employee_id_5,
                   Z.full_name AS full_name_5
              FROM employee Z,
                   SELECT DISTINCT
                        A.supervisor_id_1,
                        A.employee_id_1,
                        A.full_name_1,
                        A.supervisor_id_2,
                        A.employee_id_2,
                        A.full_name_2,
                        A.supervisor_id_3,
                        A.employee_id_3,
                        A.full_name_3,
                        Z.supervisor_id AS supervisor_id_4,
                        Z.employee_id AS employee_id_4,
                        Z.full_name AS full_name_4
                   FROM employee Z,
                        SELECT DISTINCT
                             A.supervisor_id_1,
                             A.employee_id_1,
                             A.full_name_1,
                             A.supervisor_id_2,
                             A.employee_id_2,
                             A.full_name_2,
                             Z.supervisor_id AS supervisor_id_3,
                             Z.employee_id AS employee_id_3,
                             Z.full_name AS full_name_3
                        FROM employee Z,
                             SELECT DISTINCT
                                  A.supervisor_id_1,
                                  A.employee_id_1,
                                  A.full_name_1,
                                  Z.supervisor_id AS supervisor_id_2,
                                  Z.employee_id AS employee_id_2,
                                  Z.full_name AS full_name_2
                             FROM employee Z,
                                  SELECT DISTINCT
                                       supervisor_id AS supervisor_id_1,
                                       employee_id AS employee_id_1,
                                       full_name AS full_name_1
                                   FROM employee
                                   WHERE supervisor_id = 0 OR supervisor_id IS NULL
                             ) A
                             WHERE A.employee_id_1 = Z.supervisor_id
                        ) A
                        WHERE A.employee_id_2 = Z.supervisor_id
                   ) A
                   WHERE A.employee_id_3 = Z.supervisor_id
              ) A
              WHERE A.employee_id_4 = Z.supervisor_id
         ) A
         WHERE A.employee_id_5 = Z.supervisor_id
    ) A
    UNION
    SELECT DISTINCT
         A.employee_id_5 AS employee_id,
         A.supervisor_id_1,
         A.employee_id_1,
         A.full_name_1,
         A.supervisor_id_2,
         A.employee_id_2,
         A.full_name_2,
         A.supervisor_id_3,
         A.employee_id_3,
         A.full_name_3,
         A.supervisor_id_4,
         A.employee_id_4,
         A.full_name_4,
         A.supervisor_id_5,
         A.employee_id_5,
         A.full_name_5,
         NULL AS supervisor_id_6,
         NULL AS employee_id_6,
         NULL AS full_name_6,
         NULL AS supervisor_id_7,
         NULL AS employee_id_7,
         NULL AS full_name_7
    FROM employee Z,
         SELECT DISTINCT
              A.supervisor_id_1,
              A.employee_id_1,
              A.full_name_1,
              A.supervisor_id_2,
              A.employee_id_2,
              A.full_name_2,
              A.supervisor_id_3,
              A.employee_id_3,
              A.full_name_3,
              A.supervisor_id_4,
              A.employee_id_4,
              A.full_name_4,
              Z.supervisor_id AS supervisor_id_5,
              Z.employee_id AS employee_id_5,
              Z.full_name AS full_name_5
         FROM employee Z,
              SELECT DISTINCT
                   A.supervisor_id_1,
                   A.employee_id_1,
                   A.full_name_1,
                   A.supervisor_id_2,
                   A.employee_id_2,
                   A.full_name_2,
                   A.supervisor_id_3,
                   A.employee_id_3,
                   A.full_name_3,
                   Z.supervisor_id AS supervisor_id_4,
                   Z.employee_id AS employee_id_4,
                   Z.full_name AS full_name_4
              FROM employee Z,
                   SELECT DISTINCT
                        A.supervisor_id_1,
                        A.employee_id_1,
                        A.full_name_1,
                        A.supervisor_id_2,
                        A.employee_id_2,
                        A.full_name_2,
                        Z.supervisor_id AS supervisor_id_3,
                        Z.employee_id AS employee_id_3,
                        Z.full_name AS full_name_3
                   FROM employee Z,
                        SELECT DISTINCT
                             A.supervisor_id_1,
                             A.employee_id_1,
                             A.full_name_1,
                             Z.supervisor_id AS supervisor_id_2,
                             Z.employee_id AS employee_id_2,
                             Z.full_name AS full_name_2
                        FROM employee Z,
                             SELECT DISTINCT
                                  supervisor_id AS supervisor_id_1,
                                  employee_id AS employee_id_1,
                                  full_name AS full_name_1
                              FROM employee
                              WHERE supervisor_id = 0 OR supervisor_id IS NULL
                        ) A
                        WHERE A.employee_id_1 = Z.supervisor_id
                   ) A
                   WHERE A.employee_id_2 = Z.supervisor_id
              ) A
              WHERE A.employee_id_3 = Z.supervisor_id
         ) A
         WHERE A.employee_id_4 = Z.supervisor_id
    ) A
    UNION
    SELECT DISTINCT
         A.employee_id_4 AS employee_id,
         A.supervisor_id_1,
         A.employee_id_1,
         A.full_name_1,
         A.supervisor_id_2,
         A.employee_id_2,
         A.full_name_2,
         A.supervisor_id_3,
         A.employee_id_3,
         A.full_name_3,
         A.supervisor_id_4,
         A.employee_id_4,
         A.full_name_4,
         NULL AS supervisor_id_5,
         NULL AS employee_id_5,
         NULL AS full_name_5,
         NULL AS supervisor_id_6,
         NULL AS employee_id_6,
         NULL AS full_name_6,
         NULL AS supervisor_id_7,
         NULL AS employee_id_7,
         NULL AS full_name_7
    FROM employee Z,
         SELECT DISTINCT
              A.supervisor_id_1,
              A.employee_id_1,
              A.full_name_1,
              A.supervisor_id_2,
              A.employee_id_2,
              A.full_name_2,
              A.supervisor_id_3,
              A.employee_id_3,
              A.full_name_3,
              Z.supervisor_id AS supervisor_id_4,
              Z.employee_id AS employee_id_4,
              Z.full_name AS full_name_4
         FROM employee Z,
              SELECT DISTINCT
                   A.supervisor_id_1,
                   A.employee_id_1,
                   A.full_name_1,
                   A.supervisor_id_2,
                   A.employee_id_2,
                   A.full_name_2,
                   Z.supervisor_id AS supervisor_id_3,
                   Z.employee_id AS employee_id_3,
                   Z.full_name AS full_name_3
              FROM employee Z,
                   SELECT DISTINCT
                        A.supervisor_id_1,
                        A.employee_id_1,
                        A.full_name_1,
                        Z.supervisor_id AS supervisor_id_2,
                        Z.employee_id AS employee_id_2,
                        Z.full_name AS full_name_2
                   FROM employee Z,
                        SELECT DISTINCT
                             supervisor_id AS supervisor_id_1,
                             employee_id AS employee_id_1,
                             full_name AS full_name_1
                         FROM employee
                         WHERE supervisor_id = 0 OR supervisor_id IS NULL
                   ) A
                   WHERE A.employee_id_1 = Z.supervisor_id
              ) A
              WHERE A.employee_id_2 = Z.supervisor_id
         ) A
         WHERE A.employee_id_3 = Z.supervisor_id
    ) A
    UNION
    SELECT DISTINCT
         A.employee_id_3 AS employee_id,
         A.supervisor_id_1,
         A.employee_id_1,
         A.full_name_1,
         A.supervisor_id_2,
         A.employee_id_2,
         A.full_name_2,
         A.supervisor_id_3,
         A.employee_id_3,
         A.full_name_3,
         NULL AS supervisor_id_4,
         NULL AS employee_id_4,
         NULL AS full_name_4,
         NULL AS supervisor_id_5,
         NULL AS employee_id_5,
         NULL AS full_name_5,
         NULL AS supervisor_id_6,
         NULL AS employee_id_6,
         NULL AS full_name_6,
         NULL AS supervisor_id_7,
         NULL AS employee_id_7,
         NULL AS full_name_7
    FROM employee Z,
         SELECT DISTINCT
              A.supervisor_id_1,
              A.employee_id_1,
              A.full_name_1,
              A.supervisor_id_2,
              A.employee_id_2,
              A.full_name_2,
              Z.supervisor_id AS supervisor_id_3,
              Z.employee_id AS employee_id_3,
              Z.full_name AS full_name_3
         FROM employee Z,
              SELECT DISTINCT
                   A.supervisor_id_1,
                   A.employee_id_1,
                   A.full_name_1,
                   Z.supervisor_id AS supervisor_id_2,
                   Z.employee_id AS employee_id_2,
                   Z.full_name AS full_name_2
              FROM employee Z,
                   SELECT DISTINCT
                        supervisor_id AS supervisor_id_1,
                        employee_id AS employee_id_1,
                        full_name AS full_name_1
                    FROM employee
                    WHERE supervisor_id = 0 OR supervisor_id IS NULL
              ) A
              WHERE A.employee_id_1 = Z.supervisor_id
         ) A
         WHERE A.employee_id_2 = Z.supervisor_id
    ) A
    UNION
    SELECT DISTINCT
         A.employee_id_2 AS employee_id,
         A.supervisor_id_1,
         A.employee_id_1,
         A.full_name_1,
         A.supervisor_id_2,
         A.employee_id_2,
         A.full_name_2,
         NULL AS supervisor_id_3,
         NULL AS employee_id_3,
         NULL AS full_name_3,
         NULL AS supervisor_id_4,
         NULL AS employee_id_4,
         NULL AS full_name_4,
         NULL AS supervisor_id_5,
         NULL AS employee_id_5,
         NULL AS full_name_5,
         NULL AS supervisor_id_6,
         NULL AS employee_id_6,
         NULL AS full_name_6,
         NULL AS supervisor_id_7,
         NULL AS employee_id_7,
         NULL AS full_name_7
    FROM employee Z,
         SELECT DISTINCT
              A.supervisor_id_1,
              A.employee_id_1,
              A.full_name_1,
              Z.supervisor_id AS supervisor_id_2,
              Z.employee_id AS employee_id_2,
              Z.full_name AS full_name_2
         FROM employee Z,
              SELECT DISTINCT
                   supervisor_id AS supervisor_id_1,
                   employee_id AS employee_id_1,
                   full_name AS full_name_1
               FROM employee
               WHERE supervisor_id = 0 OR supervisor_id IS NULL
         ) A
         WHERE A.employee_id_1 = Z.supervisor_id
    ) A
    UNION
    SELECT DISTINCT
         A.employee_id_1 AS employee_id,
         A.supervisor_id_1,
         A.employee_id_1,
         A.full_name_1,
         NULL AS supervisor_id_2,
         NULL AS employee_id_2,
         NULL AS full_name_2,
         NULL AS supervisor_id_3,
         NULL AS employee_id_3,
         NULL AS full_name_3,
         NULL AS supervisor_id_4,
         NULL AS employee_id_4,
         NULL AS full_name_4,
         NULL AS supervisor_id_5,
         NULL AS employee_id_5,
         NULL AS full_name_5,
         NULL AS supervisor_id_6,
         NULL AS employee_id_6,
         NULL AS full_name_6,
         NULL AS supervisor_id_7,
         NULL AS employee_id_7,
         NULL AS full_name_7
    FROM employee Z,
         SELECT DISTINCT
              supervisor_id AS supervisor_id_1,
              employee_id AS employee_id_1,
              full_name AS full_name_1
          FROM employee
          WHERE supervisor_id = 0 OR supervisor_id IS NULL
    ) A

Maybe you are looking for