[10g/8i] Need help calculating a hierarchical total

Question

Hi all...
I am trying to determine the total quantity of each unique part number in a bill of materials (big list of parts that go into a final product). The total needs to take into account the quantity of the parent parts--what I mean by this is, if you have final product 'A' that takes 1 x part 'B' and 2 x part 'C', and part 'C' takes 1 x part 'B' and 3 x part 'D' then the totals of all unique parts in product 'A' would be: 3 x B, 2 x C, 6 x D.
It would be nice if this query ran under 8i, but if it's much more complex than the equivalent query for 10g, don't worry about making it work for 8i.
Here is some sample data:
CREATE TABLE     BOM
(     part_nbr     CHAR(25)
,     bill_seq     VARCHAR2(140)
,     bill_level     NUMBER
,     parent_part     CHAR(25)
,     line_nbr     NUMBER(5)
,     child_part     CHAR(25)
,     qty_per          NUMBER(9,5)
INSERT INTO BOM VALUES ('12345-1','   10019970303',1,'12345-1',100,'12345-76',1);
INSERT INTO BOM VALUES ('12345-1','   20019970303',1,'12345-1',200,'12345-272',1);
INSERT INTO BOM VALUES ('12345-1','   30019970303',1,'12345-1',300,'12345-267',1);
INSERT INTO BOM VALUES ('12345-1','   30019970303   10019830901',2,'12345-267',100,'12345-268',1);
INSERT INTO BOM VALUES ('12345-1','   30019970303   10019830901   10019830901',3,'12345-268',100,'12345-268-1',1);
INSERT INTO BOM VALUES ('12345-1','   30019970303   20019830901',2,'12345-267',200,'12345-269',1);
INSERT INTO BOM VALUES ('12345-1','   30019970303   30019830901',2,'12345-267',300,'12345-270',1);
INSERT INTO BOM VALUES ('12345-1','   30019970303   40019830901',2,'12345-267',400,'HARDWARE-4',1);
INSERT INTO BOM VALUES ('12345-1','   30019970303   50019830901',2,'12345-267',500,'HARDWARE-5',1);
INSERT INTO BOM VALUES ('12345-1','   40019970303',1,'12345-1',400,'HARDWARE-6',2);
INSERT INTO BOM VALUES ('12345-1','   50019990824',1,'12345-1',500,'A12345-475',1);
INSERT INTO BOM VALUES ('12345-1','   60019970303',1,'12345-1',600,'HARDWARE-7',1);
INSERT INTO BOM VALUES ('12345-1','   70019990824',1,'12345-1',700,'A12345-476',1);
INSERT INTO BOM VALUES ('12345-1','   70019990824   10019990824',2,'A12345-476',100,'A12345-476-1',1);
INSERT INTO BOM VALUES ('12345-1','   80019970303',1,'12345-1',800,'12345-222',1);
INSERT INTO BOM VALUES ('12345-1','   90019970303',1,'12345-1',900,'12345-157',1);
INSERT INTO BOM VALUES ('12345-1','   90019970303   10119980922',2,'12345-157',101,'RAW-2',6.2);
INSERT INTO BOM VALUES ('12345-1','  100019990215',1,'12345-1',1000,'A12345-494',2);
INSERT INTO BOM VALUES ('12345-1','  100019990215   10019990216',2,'A12345-494',100,'A12345-486',1);
INSERT INTO BOM VALUES ('12345-1','  100019990215   10019990216   10019000101',3,'A12345-486',100,'12345-158',1);
INSERT INTO BOM VALUES ('12345-1','  100019990215   10019990216   10019000101   10119960118',4,'12345-158',101,'RAW-3',6.75);
INSERT INTO BOM VALUES ('12345-1','  100019990215   10019990216   10120000317',3,'A12345-486',101,'RAW-3',6.75);
INSERT INTO BOM VALUES ('12345-1','  100019990215   20019970303',2,'A12345-494',200,'12345-155',1);
INSERT INTO BOM VALUES ('12345-1','  100019990215   30019970303',2,'A12345-494',300,'12345-266',1);
INSERT INTO BOM VALUES ('12345-1','  100019990215   40019990215',2,'A12345-494',400,'A12345-493',1);
INSERT INTO BOM VALUES ('12345-1','  100019990215   50019970303',2,'A12345-494',500,'HARDWARE-8',1);
INSERT INTO BOM VALUES ('12345-1','  100019990215   60019970303',2,'A12345-494',600,'HARDWARE-9',1);
INSERT INTO BOM VALUES ('12345-1','  110019970303',1,'12345-1',1100,'HARDWARE-10',1);
INSERT INTO BOM VALUES ('12345-1','  120019970303',1,'12345-1',1200,'HARDWARE-9',1);
INSERT INTO BOM VALUES ('12345-1','  130019970303',1,'12345-1',1300,'HARDWARE-11',2);
INSERT INTO BOM VALUES ('12345-1','  140020000228',1,'12345-1',1400,'HARDWARE-12',1);
INSERT INTO BOM VALUES ('12345-1','  150020000228',1,'12345-1',1500,'HARDWARE-13',2);
INSERT INTO BOM VALUES ('12345-1','  160020000228',1,'12345-1',1600,'HARDWARE-14',2);
INSERT INTO BOM VALUES ('12345-1','  170020000228',1,'12345-1',1700,'12345-250',8);
INSERT INTO BOM VALUES ('12345-1','  180020000228',1,'12345-1',1800,'FLUID1',0.00001);
INSERT INTO BOM VALUES ('ABC-123','   10019000101',1,'ABC-123',100,'ABC-123-1',1);
INSERT INTO BOM VALUES ('ABC-123','   10019000101   10019000101',2,'ABC-123-1',100,'AYZ-1',2);
INSERT INTO BOM VALUES ('ABC-123','   10019000101   10019000101   10019000101',3,'AYZ-1',100,'AYZ-2',1);
INSERT INTO BOM VALUES ('ABC-123','   10019000101   10019000101   10019000101   10019000101',4,'AYZ-2',100,'RAW-1',1);
INSERT INTO BOM VALUES ('ABC-123','   10019000101   10019000101   20019000101',3,'AYZ-1',200,'HARDWARE-1',10);
INSERT INTO BOM VALUES ('ABC-123','   20020001110',1,'ABC-123',200,'HARDWARE-2',15);
INSERT INTO BOM VALUES ('ABC-123','   30020001121',1,'ABC-123',300,'HARDWARE-1',26);
INSERT INTO BOM VALUES ('ABC-123','   40019000101',1,'ABC-123',400,'AYZ-25',1);
INSERT INTO BOM VALUES ('ABC-123','   50020001121',1,'ABC-123',500,'HARDWARE-3',5);Here are the results I expect (I don't care about the order, this is just the order I hand-calculated the results in):
PART_NBR    CHILD_PART  TOTAL_QTY  
ABC-123     ABC-123-1   1          
ABC-123     HARDWARE-1  46         
ABC-123     HARDWARE-2  15         
ABC-123     HARDWARE-3  5          
ABC-123     RAW-1       1          
ABC-123     AYZ-1       2          
ABC-123     AYZ-2       2          
ABC-123     AYZ-25      1          
12345-1     12345-155   1          
12345-1     12345-157   1          
12345-1     12345-158   2          
12345-1     12345-222   1          
12345-1     12345-250   8          
12345-1     12345-266   1          
12345-1     12345-267   1          
12345-1     12345-268   1          
12345-1     12345-268-1 1          
12345-1     12345-269   1          
12345-1     12345-270   1          
12345-1     12345-272   1          
12345-1     12345-76    1          
12345-1     A12345-475  1          
12345-1     A12345-476  1          
12345-1     A12345-476-11          
12345-1     A12345-486  2          
12345-1     A12345-493  1          
12345-1     A12345-494  2          
12345-1     FLUID1      0.00001    
12345-1     HARDWARE-10 1          
12345-1     HARDWARE-11 2          
12345-1     HARDWARE-12 1          
12345-1     HARDWARE-13 2          
12345-1     HARDWARE-14 2          
12345-1     HARDWARE-4  1          
12345-1     HARDWARE-5  1          
12345-1     HARDWARE-6  2          
12345-1     HARDWARE-7  1          
12345-1     HARDWARE-8  1          
12345-1     HARDWARE-9  2          
12345-1     RAW-2       6.2        
12345-1     RAW-3       27          Clearly this query:
SELECT     part_nbr
,     child_part
,     SUM(qty_per)
FROM     BOM
GROUP BY     part_nbr
,          child_part
ORDER BY     part_nbr
,          child_part
;will not give the desired results, as it doesn't take into account the quantity required of each child's parent, but I can't figure out how to do that.
The sample data I have provided represents data from a table or materialized view that is, roughly, the result of a hierarchical query of data in another table or three. If it's simpler to work off the tables on which this table is based, let me know, and I can put together some sample data from those tables.

Answer 1

Hi,
user11033437 wrote:
Hi all...
I am trying to determine the total quantity of each unique part number in a bill of materials (big list of parts that go into a final product). The total needs to take into account the quantity of the parent parts--what I mean by this is, if you have final product 'A' that takes 1 x part 'B' and 2 x part 'C', and part 'C' takes 1 x part 'B' and 3 x part 'D' then the totals of all unique parts in product 'A' would be: 3 x B, 2 x C, 6 x D.That's a very good explanation in general terms. No doubt, for you, applying that to the specific data is trivial, but most of us aren't as familiar with your application as you are. It would help a lot if you posted a similar explanation using specific ids from the sample data. For example, why do the desired results include:
PART_NBR    CHILD_PART  TOTAL_QTY  
ABC-123     HARDWARE-1  46     If someone explores the data enough, they might guess that the number 46 is the sum of 26 and 20=2*10, but it would sure save a lot of time if you, to whom this is second nature, could explain it.
It would be nice if this query ran under 8i, but if it's much more complex than the equivalent query for 10g, don't worry about making it work for 8i. Sorry, I don't know any simple way to do this in Oracle 8.1. The SYS_CONNECT_BY_PATH function, introduced in Oracle 9, is essential to the solution below.
Here is some sample data:
CREATE TABLE     BOM
INSERT INTO BOM VALUES ('ABC-123','   50020001121',1,'ABC-123',500,'HARDWARE-3',5);
Good job.
It looks like only about half of the columns have anything to do with this problem. Here's another place where sharing your knowlege ot he application could really help people. Don't post things that are irrelvant to the problem you're asking. If there's a sincere doubt, then say somthing like "I need part_nbr, bill_seq and bill_level in the output for my real problem. I don't think they have anything to do with getting the total qty, but I'm posting them just in case."
Here are the results I expect (I don't care about the order, this is just the order I hand-calculated the results in):
PART_NBR    CHILD_PART  TOTAL_QTY  
ABC-123     ABC-123-1   1          
ABC-123     HARDWARE-1  46    
12345-1     RAW-3       27          Clearly this query:
SELECT     part_nbr
,     child_part
,     SUM(qty_per)
FROM     BOM
GROUP BY     part_nbr
,          child_part
ORDER BY     part_nbr
,          child_part
;will not give the desired results, as it doesn't take into account the quantity required of each child's parent, but I can't figure out how to do that.Thanks for posting the query. Even though it doesn;t work, it helped me understand what you wanted, and saved me some time.
The sample data I have provided represents data from a table or materialized view that is, roughly, the result of a hierarchical query of data in another table or three. If it's simpler to work off the tables on which this table is based, let me know, and I can put together some sample data from those tables.I don't know if it would be any simpler. It might be more efficient, but I don't know how much that matters to you. Try the solution below. If it takes, say, 60 seconds, is it worthwhile trying to see if we can get it to run in 15?
This seems to get the right results:
SELECT     part_nbr
,     child_part
,     SUM (eval_number ('1' || SYS_CONNECT_BY_PATH (qty_per, '*')))     AS total_qty
FROM     bom
START WITH     parent_part     = part_nbr
CONNECT BY     parent_part     = PRIOR child_part
GROUP BY  part_nbr
,       child_part
ORDER BY  part_nbr
,       child_part
;Do some experiments, on variations of this query, if you don't understand what SYS_CONNECT_BY_PATH is doing. You'll see that it's returning a string, such as '*2*1*1*6.75' that reflects the quantities needed at each level of the process. To actually do the multiplication, and get a number, I used this function:
CREATE OR REPLACE FUNCTION     eval_number
(     in_txt     IN     VARCHAR2
,     err_val     IN     NUMBER     DEFAULT     NULL
RETURN     NUMBER
IS
--          **   e v a l _ n u m b e r   **
--          eval_number attempts to evaluate in_txt as a NUMBER,
--          returning that value.  If in_txt can not be interpreted,
--          then err_val is returned.
     result_txt     VARCHAR2 (100);
     return_val     NUMBER;
BEGIN
     EXECUTE IMMEDIATE     'SELECT '
               ||     in_txt
               ||     ' FROM dual'
               INTO     return_val;
--     dbms_output.put_line (result_val || ' = result_txt in eval_number');
     RETURN     return_val;
EXCEPTION
     WHEN OTHERS
     THEN
--          dbms_output.put_line (SQLERRM || ' = error in eval_number');
          RETURN     err_val;
END     eval_number
SHOW ERRORSI hate using "WHEN OTHERS" like this. Perhaps someone can suggest a reasonable set of specific errors that could be caught in the EXCEPTION section.