<?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: illegal join condition in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/illegal-join-condition/m-p/10149507#M1820218</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;I'm no expert on infosets, but the format change between the 18 character bank account number in LFBK and the 35 character number in TIBAN is done by function module CONVERT_BANK_ACCOUNT_NUMBER.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would also point out that the account number alone does not represent a unique relationship, the country and back key are also necessary.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Nick&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 20 Mar 2014 09:42:12 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2014-03-20T09:42:12Z</dc:date>
    <item>
      <title>illegal join condition</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/illegal-join-condition/m-p/10149506#M1820217</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;I have created Infoset using two Table TIBAN and LFBK .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now the common field between the two tables in BANKN.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The length of BANKN from LFBK table is 18 char and the length of BANKN from TIBAN is of 35 char.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Due to length mismatch I am unable to join.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any input on the above issue will be of great help .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If anyone has worked on creating infoset in SAP R3 system then please provide some input.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Anjali Singh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Mar 2014 09:23:03 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/illegal-join-condition/m-p/10149506#M1820217</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2014-03-20T09:23:03Z</dc:date>
    </item>
    <item>
      <title>Re: illegal join condition</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/illegal-join-condition/m-p/10149507#M1820218</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;I'm no expert on infosets, but the format change between the 18 character bank account number in LFBK and the 35 character number in TIBAN is done by function module CONVERT_BANK_ACCOUNT_NUMBER.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would also point out that the account number alone does not represent a unique relationship, the country and back key are also necessary.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Nick&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Mar 2014 09:42:12 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/illegal-join-condition/m-p/10149507#M1820218</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2014-03-20T09:42:12Z</dc:date>
    </item>
    <item>
      <title>Re: illegal join condition</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/illegal-join-condition/m-p/10149508#M1820219</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In Infoset unfortunately you can't connect two field with different lenght.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You need to manage data through a Routine.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Angelo.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Mar 2014 10:14:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/illegal-join-condition/m-p/10149508#M1820219</guid>
      <dc:creator>former_member302911</dc:creator>
      <dc:date>2014-03-20T10:14:05Z</dc:date>
    </item>
    <item>
      <title>Re: illegal join condition</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/illegal-join-condition/m-p/10149509#M1820220</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This message was moderated.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Mar 2014 10:22:24 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/illegal-join-condition/m-p/10149509#M1820220</guid>
      <dc:creator>former_member227685</dc:creator>
      <dc:date>2014-03-20T10:22:24Z</dc:date>
    </item>
  </channel>
</rss>

