<?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: innner join? in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/innner-join/m-p/4028930#M962832</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HI,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The join syntax represents a recursively nestable join expression. A join expression consists of a left-hand and a right- hand side, which are joined either by means of [INNER] JOIN or LEFT [OUTER] JOIN. Depending on the type of join, a join expression can be either an inner (INNER) or an outer (LEFT OUTER) join. Every join expression can be enclosed in round brackets. If a join expression is used, the SELECT command circumvents SAP buffering. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On the left-hand side, either a single database table, a view dbtab_left, or a join expression join can be specified. On the right-hand side, a single database table or a view dbtab_right as well as join conditions join_cond can be specified after ON. In this way, a maximum of 24 join expressions that join 25 database tables or views with each other can be specified after FROM. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;AS can be used to specify an alternative table name tabalias for each of the specified database table names or for every view. A database table or a view can occur multiple times within a join expression and, in this case, have various alternative names. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Suman&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 20 Jun 2008 10:11:32 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-06-20T10:11:32Z</dc:date>
    <item>
      <title>innner join?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/innner-join/m-p/4028925#M962827</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi abapers.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;wat is innerr join and outer join.....wat is the difference between inner join and for all entries? . which one is performance wise very good(tel me the reason)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 20 Jun 2008 10:05:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/innner-join/m-p/4028925#M962827</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-06-20T10:05:05Z</dc:date>
    </item>
    <item>
      <title>Re: innner join?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/innner-join/m-p/4028926#M962828</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Sankaran,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;please check this link&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ec77446011d189700000e8322d00/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ec77446011d189700000e8322d00/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The data that can be selected with a view depends primarily on whether the view implements an inner join or an outer join. With an inner join, you only get the records of the cross-product for which there is an entry in all tables used in the view. With an outer join, records are also selected for which there is no entry in some of the tables used in the view.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The set of hits determined by an inner join can therefore be a subset of the hits determined with an outer join.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Database views implement an inner join. The database therefore only provides those records for which there is an entry in all the tables used in the view. Help views and maintenance views, however, implement an outer join.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please check this link&lt;/P&gt;&lt;P&gt;for the &lt;STRONG&gt;DIFFERENCES&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_thread" href="https://community.sap.com/" __jive_macro_name="thread" modifiedtitle="true" __default_attr="750620"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_thread" href="https://community.sap.com/" __jive_macro_name="thread" modifiedtitle="true" __default_attr="309762"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;raam&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 20 Jun 2008 10:06:25 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/innner-join/m-p/4028926#M962828</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-06-20T10:06:25Z</dc:date>
    </item>
    <item>
      <title>Re: innner join?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/innner-join/m-p/4028927#M962829</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Pls search through the SDN. You have many threads regarding this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Sharath&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 20 Jun 2008 10:07:20 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/innner-join/m-p/4028927#M962829</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-06-20T10:07:20Z</dc:date>
    </item>
    <item>
      <title>Re: innner join?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/innner-join/m-p/4028928#M962830</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi check this..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_thread" href="https://community.sap.com/" __jive_macro_name="thread" modifiedtitle="true" __default_attr="750620"&gt;&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 20 Jun 2008 10:09:43 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/innner-join/m-p/4028928#M962830</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-06-20T10:09:43Z</dc:date>
    </item>
    <item>
      <title>Re: innner join?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/innner-join/m-p/4028929#M962831</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Go through this links:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04/helpdata/en/fc/eb39c4358411d1829f0000e829fbfe/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04/helpdata/en/fc/eb39c4358411d1829f0000e829fbfe/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Adil&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 20 Jun 2008 10:09:57 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/innner-join/m-p/4028929#M962831</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-06-20T10:09:57Z</dc:date>
    </item>
    <item>
      <title>Re: innner join?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/innner-join/m-p/4028930#M962832</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HI,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The join syntax represents a recursively nestable join expression. A join expression consists of a left-hand and a right- hand side, which are joined either by means of [INNER] JOIN or LEFT [OUTER] JOIN. Depending on the type of join, a join expression can be either an inner (INNER) or an outer (LEFT OUTER) join. Every join expression can be enclosed in round brackets. If a join expression is used, the SELECT command circumvents SAP buffering. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On the left-hand side, either a single database table, a view dbtab_left, or a join expression join can be specified. On the right-hand side, a single database table or a view dbtab_right as well as join conditions join_cond can be specified after ON. In this way, a maximum of 24 join expressions that join 25 database tables or views with each other can be specified after FROM. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;AS can be used to specify an alternative table name tabalias for each of the specified database table names or for every view. A database table or a view can occur multiple times within a join expression and, in this case, have various alternative names. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Suman&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 20 Jun 2008 10:11:32 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/innner-join/m-p/4028930#M962832</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-06-20T10:11:32Z</dc:date>
    </item>
    <item>
      <title>Re: innner join?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/innner-join/m-p/4028931#M962833</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;What Is Inner and Left Outer Join&lt;/STRONG&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; inner join &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The data that can be selected with a view depends primarily on whether the view implements an inner join or an outer join. With an inner join, you only get the records of the cross-product for which there is an entry in all tables used in the view. With an outer join, records are also selected for which there is no entry in some of the tables used in the view.  The set of hits determined by an inner join can therefore be a subset of the hits determined with an outer join. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Example for Inner join: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SELECT A&lt;SUB&gt;EBELN A&lt;/SUB&gt;LIFNR A&lt;SUB&gt;KNUMV B&lt;/SUB&gt;EBELP B&lt;SUB&gt;NETWR B&lt;/SUB&gt;NETPR B&lt;SUB&gt;WERKS B&lt;/SUB&gt;MATNR &lt;/P&gt;&lt;P&gt;  L&lt;SUB&gt;NAME1 L&lt;/SUB&gt;NAME2 &lt;/P&gt;&lt;P&gt;  FROM EKKO AS A &lt;/P&gt;&lt;P&gt;  INNER JOIN EKPO AS B ON A&lt;SUB&gt;EBELN = B&lt;/SUB&gt;EBELN &lt;/P&gt;&lt;P&gt;  INNER JOIN LFA1 AS L ON L&lt;SUB&gt;LIFNR = A&lt;/SUB&gt;LIFNR &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;INNER JOIN EKKN AS C ON C&lt;SUB&gt;EBELN = A&lt;/SUB&gt;EBELN &lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;  INTO CORRESPONDING FIELDS OF TABLE itab &lt;/P&gt;&lt;P&gt;  WHERE B~BUKRS = 'company code' . &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Left outer join&lt;/STRONG&gt; &lt;/P&gt;&lt;P&gt;Usually, when defining InfoSets, the objects are linked via inner join operators. However, you can also use left outer joins.  Inner join and left outer join are only different in the situation where one of the involved tables does not contain any suitable record which meets the join conditions. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With an inner join (table 1 inner join table 2), no record is included in the result set in this case. However, this means that the corresponding record from tables 1 is not considered in the results set.                                         &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With an left outer join (table 1 left outer join table2), exactly one record is included in the results set in this case´. In this record, the fields from table 1 contain the values of the record from table 1 and the fields from table 2 are all filled with the initial value.    &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Example of left outer join: &lt;/P&gt;&lt;P&gt;DATA: CUSTOMER TYPE SCUSTOM,  &lt;/P&gt;&lt;P&gt;      BOOKING  TYPE SBOOK.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SELECT SCUSTOM&lt;SUB&gt;NAME SCUSTOM&lt;/SUB&gt;POSTCODE SCUSTOM~CITY  &lt;/P&gt;&lt;P&gt;       SBOOK&lt;SUB&gt;FLDATE SBOOK&lt;/SUB&gt;CARRID SBOOK&lt;SUB&gt;CONNID SBOOK&lt;/SUB&gt;BOOKID  &lt;/P&gt;&lt;P&gt;       INTO (CUSTOMER-NAME, CUSTOMER-POSTCODE, CUSTOMER-CITY,  &lt;/P&gt;&lt;P&gt;             BOOKING-FLDATE, BOOKING-CARRID, BOOKING-CONNID,  &lt;/P&gt;&lt;P&gt;             BOOKING-BOOKID)  &lt;/P&gt;&lt;P&gt;       FROM SCUSTOM LEFT OUTER JOIN SBOOK  &lt;/P&gt;&lt;P&gt;         ON SCUSTOM&lt;SUB&gt;ID = SBOOK&lt;/SUB&gt;CUSTOMID AND  &lt;/P&gt;&lt;P&gt;            SBOOK~FLDATE = '20081015'  &lt;/P&gt;&lt;P&gt;       ORDER BY SCUSTOM&lt;SUB&gt;NAME SBOOK&lt;/SUB&gt;FLDATE.  &lt;/P&gt;&lt;P&gt;  WRITE: / CUSTOMER-NAME, CUSTOMER-POSTCODE, CUSTOMER-CITY,  &lt;/P&gt;&lt;P&gt;           BOOKING-FLDATE, BOOKING-CARRID, BOOKING-CONNID,  &lt;/P&gt;&lt;P&gt;           BOOKING-BOOKID.  &lt;/P&gt;&lt;P&gt;ENDSELECT. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;go through these links.&lt;/P&gt;&lt;P&gt; &lt;A href="http://www.sap-img.com/abap/performance-tuning-for-data-selection-statement.htm" target="test_blank"&gt;http://www.sap-img.com/abap/performance-tuning-for-data-selection-statement.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sap-img.com/abap/usage-of-for-all-entries-in-select-statement.htm" target="test_blank"&gt;http://www.sap-img.com/abap/usage-of-for-all-entries-in-select-statement.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 20 Jun 2008 10:12:32 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/innner-join/m-p/4028931#M962833</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-06-20T10:12:32Z</dc:date>
    </item>
    <item>
      <title>Re: innner join?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/innner-join/m-p/4028932#M962834</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Inner join means retriving dat from 2 dat base tables , so hitting data base several time which is not preferable,&lt;/P&gt;&lt;P&gt;and &lt;/P&gt;&lt;P&gt;For all entries means u can select data from DBtable to itab and then u can perform that itab with another itab , so no.of hits on DB will be reduced, and it is preferable,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;and left outer join is if we have 2 itabs and we want to retrive data based on one field then in first itab we have one more additional value then the second itab then that value also come into final itab&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regds,&lt;/P&gt;&lt;P&gt;Murali.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 20 Jun 2008 10:14:42 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/innner-join/m-p/4028932#M962834</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-06-20T10:14:42Z</dc:date>
    </item>
  </channel>
</rss>

