START WITH and CONNECT BY in Oracle SQL ( hierarchical relationship)

Question

Hi, the original table as below
Customer_ID         Account_ID          Paying_Account_ID         Parent_Account_ID          Company_ID
158                    158                    158                         158                     0
159                    159                    158                         158                     0
160                    160                    158                         158                     0
181                    181                    181                         181                     0
183                    183                    183                         183                     0
24669                  24669                  24669                       24669                   0        
24671                  24671                  24671                       24669                   0
24670                  24670                  24670                       24669                   0    
3385127                3385127                3385127                     24670                   0To identify the hierarchical relationship of the data, which are PARENT_ACCOUNT_ID & ACCOUNT_ID, below is the query that I was used.
select  lpad(' ', 2*level) || A.ACCOUNT_ID AS LEVEL_LABEL, CONNECT_BY_ISCYCLE "Cycle", LEVEL, A.* from ACCOUNT A
START WITH parent_account_id = account_id
CONNECT BY NOCYCLE  PRIOR A.ACCOUNT_ID = A.PARENT_ACCOUNT_ID
AND account_id != parent_account_id
;This is the result from the query
Level_Label              Level          Cycle        Customer_ID             Account_ID        Paying_Account_ID      Parent_Account_ID      Company_ID
158                         1             0              158                     158              158                   158                     0
   159                      2             0              159                     159              158                   158                     0
   160                      2             0              160                     160              158                   158                     0
181                         1             0              181                     181              181                   181                     0
183                         1             0              183                     183              183                   183                     0
24669                       1             0              24669                   24669            24669                 24669                   0      
    24671                   2             0              24671                   24671            24671                 24669                   0
    24670                   2             0              24670                   24670            24670                 24669                   0
        3385127             3             0              3385127                 3385127          3385127               24670                   0My questions is how can I modified the query in order to calcuate the values for:
My_Total_PR - Number of my child PR accounts which doest not include itself.
Total_PR - Total number of PR accounts in the overall structure
My_Total_NPR - Number of my child NPR accounts which doest not include itself.
Total_NPR - Total number of NPR accounts in the overall structure
*PR stand for payment responsible, for instance the payment responsible for Account 158 is 158 (Paying_Account_ID), so the Total_PR for 158 is 3 (158, 159, 160)
*NPR stand for Non payment responsible, for instance the payment responsible for Account 159 is 158 (Paying_Account_ID), so the Total_NPR for 159 is 1
This is the expected result, Any advice much appreciated. Thanks
Level_Label                     Level           Cycle           My_Total_PR     Total_PR     My_Total_NPR     Total_NPR     Paying_Account
158                               1                0                  2              3          0              0              158
    159                           2                0                  0              0          0              1              158
    160                           2                0                  0              0          0              1              158
181                               1                0                  0              1          0              0              181
183                               1                0                  0              1          0              0              183
24669                             1                0                  0              1          3              3              24669                  
    24671                         2                0                  0              1          0              0              24671
    24670                         2                0                  0              1          1              1              24670
        3385127                   3                0                  0              1          0              0              3385127Edited by: user11432758 on 14-Feb-2012 01:00
Edited by: user11432758 on 14-Feb-2012 07:05

Answer 1

Hi,
user11432758 wrote:
Hi below is the DDL statment, thanks
CREATE TABLE "SYSTEM"."ACCOUNT" ...
Don't create your own objects in the SYSTEM schema, or any schema that comes with the database. Create a separate schema, and put your objects into it. You'll have fewer security problems, and migrating to a new database will be easier.
Here's one way to can get the aggregates that you want:
WITH     got_descendants          AS
     SELECT     CONNECT_BY_ROOT account_id     AS ancestor_id
     ,     paying_account_id
     ,     LEVEL                    AS lvl
     FROM     account
     CONNECT BY NOCYCLE     PRIOR account_id     = parent_account_id
          AND          account_id          != parent_account_id
SELECT       ancestor_id
,       COUNT (CASE WHEN lvl             > 1
                  AND  ancestor_id  = paying_account_id THEN 1 END)     AS my_total_pr
,       COUNT (CASE WHEN ancestor_id  = paying_account_id THEN 1 END)     AS total_pr
,       COUNT (CASE WHEN lvl             > 1
                  AND  ancestor_id != paying_account_id THEN 1 END)     AS my_total_npr
,       COUNT (CASE WHEN ancestor_id != paying_account_id THEN 1 END)     AS total_npr
FROM       got_descendants
GROUP BY  ancestor_id
;Output:
`             MY_         MY_
            TOTAL TOTAL TOTAL TOTAL
ANCESTOR_ID   _PR   _PR  _NPR  _NPR
        158     2     3     0     0
        159     0     0     0     1
        160     0     0     0     1
        181     0     1     0     0
        183     0     1     0     0
      24669     0     1     3     3
      24670     0     1     1     1
      24671     0     1     0     0
    3385217     0     1     0     0This gives you the right numbers, but how can we get them in an order that reflects the hierarchy, with the columns (such as lvl) that are derived from the hierarchy?
One way would be to do two CONNECT BY queries; one without a START WITH clause (like the one above) that gets the aggregates, and the other with a START WITH clause (like your original query), that is in the right order, and has columns such as level_label and level. We could join the result sets and get exactly what we want. I'll leave that as an exercise.
Here's another way, that gets the right results with only one CONNECT BY query:
WITH     got_descendants          AS
     SELECT     CONNECT_BY_ROOT account_id     AS ancestor_id
     ,     paying_account_id
     ,     account_id
     ,     LEVEL                    AS lvl
     ,     CONNECT_BY_ISCYCLE          AS cycle
     ,     CASE
              WHEN  CONNECT_BY_ROOT account_id
                  = CONNECT_BY_ROOT parent_account_id
              THEN  ROWNUM
          END                    AS r_num
     FROM     account
     CONNECT BY NOCYCLE     PRIOR account_id     = parent_account_id
          AND          account_id          != parent_account_id
     ORDER SIBLINGS BY     account_id     -- Optional
,     got_o_num     AS
     SELECT     got_descendants.*
     ,     MIN (r_num) OVER (PARTITION BY  account_id)     AS o_num
     ,     MAX (lvl)   OVER (PARTITION BY  account_id)      AS max_lvl
     FROM     got_descendants
SELECT       LPAD ( ' '
            , 2 * (MIN (max_lvl) - 1)
            )  || ancestor_id                         AS level_label
,       MIN (max_lvl)                                AS "Level"
,       MIN (cycle)                                   AS "Cycle"
,       COUNT (CASE WHEN lvl             > 1
                  AND  ancestor_id  = paying_account_id THEN 1 END)     AS my_total_pr
,       COUNT (CASE WHEN ancestor_id  = paying_account_id THEN 1 END)     AS total_pr
,       COUNT (CASE WHEN lvl             > 1
                  AND  ancestor_id != paying_account_id THEN 1 END)     AS my_total_npr
,       COUNT (CASE WHEN ancestor_id != paying_account_id THEN 1 END)     AS total_npr
,       MIN (paying_account_id)                                    AS paying_account
FROM       got_o_num
GROUP BY  ancestor_id
ORDER BY  MIN (o_num)
;Output:
`                             MY_         MY_
                            TOTAL TOTAL TOTAL TOTAL  PAYING_
LEVEL_LABEL     Level Cycle   _PR   _PR  _NPR  _NPR  ACCOUNT
158                 1     0     2     3     0     0      158
  159               2     0     0     0     0     1      158
  160               2     0     0     0     0     1      158
181                 1     0     0     1     0     0      181
183                 1     0     0     1     0     0      183
24669               1     0     0     1     3     3    24669
  24670             2     0     0     1     1     1    24670
    3385217         3     0     0     1     0     0  3385217
  24671             2     0     0     1     0     0    24671This is exactly what you requested, except that you posted the row with level_label='  24671' before the row with level_label='  24671'. You may not care which of those comes first, but if that's important, explain why those rows need to be in descending order by account_id, while '159 and '160' are in ascending order. You'll need to change the ORDER SIBLINGS BY clause accordingly.