Hi Manju,

The value is kept inside AGILE.REFDESIG table.  You can join BOM Table with REFDESIG Table as  BOM.ID = REFDESIG.BOM(+)  and then print  REFDESIG.LABEL table which is your reference designator value.

Regards,
Arif

And Arif is correct, LABEL is where the ref-des values are stored in REFDESIG, and the join is done as BOM.ID = REFDESIG.BOM(+).
 The bigger problem for a single query is that the ref-des values are stored as separate values in the table, and not as a single consolidated string. So you WILL get as many records for a single BOM line as there are ref-des values, if you simply link the 2 tables using the outer join.
The only way around this is to write a function to get the ref-des values and then have your query use it, instead of doing a join to the table. Something along the lines of :
create or replace function GetRD(bomID IN number) RETURN CLOB IS
    cursor csrSRD is select label from refdesig where bom = bomID order by label;
    rdes       varchar2(50);
    refdes    clob;
begin
   refdes := null;
   open csrSRD;
   loop
          fetch csrSRD into rdes;
          exit when csrSRD%NOTFOUND;

          if refdes is null then
                refdes := rdes;
          else
                refdes := refdes || ‘,’ || rdes;
          end if;
    end loop;
    close csrSRD;

     RETURN refdes;
end;
/
show err

 Note that the above function returns a CLOB value, as you have no idea how long the entire list of ref-des values will be. The above will return anything from a null string to a VERY long string of ref-des values.

And the function can be used as follows :
select i.item_number ASSEMBLY, b.item_number COMPONENT, b.find_number, b.quantity, GetRD(b.id) REFDES
 from bom b, item i
 where b.change_out = 0 and b.item = i.id and i.category = (select entryid from listentry where parentid = NNN and entryvalue = ‘11111’);

 Given everything you are trying to do, it might be easier to put all of the data into a table, update the list values and such using SQL, and to then finally just select all records from the table. Joins such are you are doing for LIST06 are far easier/simpler to do as a single query against a destination table than as you are doing. Just about everything in the Agile database (which is NOT documented in any way, shape or form by Oracle) is an ID, that is then linked to another table that contains the actual text value you need. ITEM.CATEGORY is an example, as it is NUMERIC data type, and must be linked to LISTENTRY to get the text value (just like you are doing with LIST06).