<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: BoM type table Join in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/bom-type-table-join/m-p/3163135#M902853</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;what do mean by climbing up levels?&lt;BR /&gt;I was looking for a way to combine three tables in metalink and this I found:&lt;A href="http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=FOR&amp;amp;p_id=333481.999" target="_blank"&gt;http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=FOR&amp;amp;p_id=333481.999&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;try this:&lt;BR /&gt;select p2.orderno, p1.pegging_type from (mrp_plan p1 left join mrp_pegging g on p1.plan_sequence = g.plan_sequence) left join mrp_plan p2 on g.peggingno = p2.peggingno where p2.pegging_type = 'P' and p2.orderno like 'W000%';&lt;BR /&gt;&lt;BR /&gt;greetings,&lt;BR /&gt;&lt;BR /&gt;Michael&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Tue, 13 Jan 2004 12:49:46 GMT</pubDate>
    <dc:creator>Michael Schulte zur Sur</dc:creator>
    <dc:date>2004-01-13T12:49:46Z</dc:date>
    <item>
      <title>BoM type table Join</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/bom-type-table-join/m-p/3163133#M902851</link>
      <description>I have two tables which combined complete a 'Bill of Materials' Type table join. i.e. table 1 links to table 2 and table 2 links back to table 1.&lt;BR /&gt;&lt;BR /&gt;As an example of this I have included the following query&lt;BR /&gt;&lt;BR /&gt;select p2.orderno, p1.pegging_type&lt;BR /&gt;from mrp_plan p1, mrp_plan p2, mrp_pegging g&lt;BR /&gt;where p1.plan_sequence = g.plan_sequence and&lt;BR /&gt;      g.peggingno = p2.peggingno and&lt;BR /&gt;      p2.pegging_type = 'P' and&lt;BR /&gt;      p2.orderno like 'W000%';&lt;BR /&gt;&lt;BR /&gt;This query climbs one level up the pegging tree to tell me if the demand is from a sales order or a forcast.&lt;BR /&gt;&lt;BR /&gt;My question is what is the proper structure for this type of join and how do I climb up multiple levels?&lt;BR /&gt;&lt;BR /&gt;DB software is Oracle 8.1.7</description>
      <pubDate>Tue, 13 Jan 2004 11:06:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/bom-type-table-join/m-p/3163133#M902851</guid>
      <dc:creator>John Flanagan</dc:creator>
      <dc:date>2004-01-13T11:06:55Z</dc:date>
    </item>
    <item>
      <title>Re: BoM type table Join</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/bom-type-table-join/m-p/3163134#M902852</link>
      <description>You probably have to use the "walking tree" technic if I understand your Query.&lt;BR /&gt;&lt;BR /&gt;I assume you have Metalink access.&lt;BR /&gt;search for "walking tree" &lt;BR /&gt;&lt;BR /&gt;regards,&lt;BR /&gt;Jean-Luc</description>
      <pubDate>Tue, 13 Jan 2004 11:36:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/bom-type-table-join/m-p/3163134#M902852</guid>
      <dc:creator>Jean-Luc Oudart</dc:creator>
      <dc:date>2004-01-13T11:36:40Z</dc:date>
    </item>
    <item>
      <title>Re: BoM type table Join</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/bom-type-table-join/m-p/3163135#M902853</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;what do mean by climbing up levels?&lt;BR /&gt;I was looking for a way to combine three tables in metalink and this I found:&lt;A href="http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=FOR&amp;amp;p_id=333481.999" target="_blank"&gt;http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=FOR&amp;amp;p_id=333481.999&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;try this:&lt;BR /&gt;select p2.orderno, p1.pegging_type from (mrp_plan p1 left join mrp_pegging g on p1.plan_sequence = g.plan_sequence) left join mrp_plan p2 on g.peggingno = p2.peggingno where p2.pegging_type = 'P' and p2.orderno like 'W000%';&lt;BR /&gt;&lt;BR /&gt;greetings,&lt;BR /&gt;&lt;BR /&gt;Michael&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 13 Jan 2004 12:49:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/bom-type-table-join/m-p/3163135#M902853</guid>
      <dc:creator>Michael Schulte zur Sur</dc:creator>
      <dc:date>2004-01-13T12:49:46Z</dc:date>
    </item>
    <item>
      <title>Re: BoM type table Join</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/bom-type-table-join/m-p/3163136#M902854</link>
      <description>I have looked at the Wakling tree situation but it seems only to work for a single table.&lt;BR /&gt;&lt;BR /&gt;In my case I have 2 tables.&lt;BR /&gt;&lt;BR /&gt;mrp_plan links to mrp_pegging by peggingno.  I can then use plan_sequence field to link mrp_pegging back to my parent record in mrp_plan.&lt;BR /&gt;&lt;BR /&gt;Is there a good way to do this?&lt;BR /&gt;Is my explanation make sense?&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;John.</description>
      <pubDate>Wed, 14 Jan 2004 07:54:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/bom-type-table-join/m-p/3163136#M902854</guid>
      <dc:creator>John Flanagan</dc:creator>
      <dc:date>2004-01-14T07:54:21Z</dc:date>
    </item>
  </channel>
</rss>

