Manager - Sales-rep drill down report

Question

[code]
SELECT 
FSU.parentsystemuseridname AS Manager
, FSU.fullname AS 'Sales Rep'
, FSU3.fullname AS 'Level 3'
FROM FilteredSystemUser AS FSU
LEFT JOIN FilteredSystemUser AS FSU3
ON FSU.fullname = FSU3.parentsystemuseridname
[\/code]
There are multiple levels in the hierarchy but i am showing 3 levels only in the sample query above. I am trying to create a drill down SSRS report which shows the hierarchy. It works fine with a small problem.
Problem:
1.) Manager is a sales rep himself so in the "sales rep " column manager should be shown along with his associates with a null value for the "Level 3 " column.
2.) In the same way Sales rep should also be present along with his associates in "Level 3 " column.
Please help me with your ideas for the query. Thanks in advance.
Oracle 11g database.

Answer 1

Hi,
If you can show what you need to do using commonly available tables, such as those in the scott schema, then you don't need to post any sample data; just the results you want from the given data, and an explanation of how you get those results from that data.
For example, using the scott.emp table (where the relevant raw data, which you can get from this query:
SELECT    empno, ename, mgr
FROM   scott.emp
ORDER BY  empno;
is
     EMPNO ENAME             MGR
      7369 SMITH            7902
      7499 ALLEN            7698
      7521 WARD             7698
      7566 JONES            7839
      7654 MARTIN           7698
      7698 BLAKE            7839
      7782 CLARK            7839
      7788 SCOTT            7566
      7839 KING
      7844 TURNER           7698
      7876 ADAMS            7788
      7900 JAMES            7698
      7902 FORD             7566
      7934 MILLER           7782
that is:
KING is the parent of JONES, BLAKE and CLARK,
JONES is the parent of SCOTT and FORD, and
SCOTT is the parent of ADAMS, and
you can get output like this:
CHAIN_O_COMMAND
KING
KING      JONES
KING      JONES     SCOTT
KING      JONES     SCOTT     ADAMS
KING      JONES     FORD
KING      JONES     FORD      SMITH
KING      BLAKE
KING      BLAKE     ALLEN
KING      BLAKE     WARD
KING      BLAKE     MARTIN
KING      BLAKE     TURNER
KING      BLAKE     JAMES
KING      CLARK
KING      CLARK     MILLER
using a query like this:
SELECT  REPLACE ( SYS_CONNECT_BY_PATH ( RPAD (ename, 10)
                )         AS chain_o_command
FROM    scott.emp
START WITH  mgr  IS NULL
CONNECT BY  mgr  = PRIOR empno
Notice that the result set only has 1 long column, but it's formatted to look like multiple short columns.  That's because the number of columns in the result set must be hard-coded in the query.  If you don't know how many columns you'll need (because you don't know how many levels will be in the tree) this is one way to avoid dynamic SQL.