<?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 RFC interface mapping issue in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/rfc-interface-mapping-issue/m-p/11640066#M1942947</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am facing an issue that system A calls system B RFC, RFC has a table interface which the structure contains '.INCLUDE' . &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;but in system A, the corresponding data source for this interface is a local type , which don't contain any '.INCLUDE' . &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;here we face a mapping issue due to include structure concept. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is it possible that we could avoid this mapping issue?&amp;nbsp; and how ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks ,&lt;BR /&gt;Kevin&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 19 Apr 2016 03:09:50 GMT</pubDate>
    <dc:creator>kevin_wang6</dc:creator>
    <dc:date>2016-04-19T03:09:50Z</dc:date>
    <item>
      <title>RFC interface mapping issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/rfc-interface-mapping-issue/m-p/11640066#M1942947</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am facing an issue that system A calls system B RFC, RFC has a table interface which the structure contains '.INCLUDE' . &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;but in system A, the corresponding data source for this interface is a local type , which don't contain any '.INCLUDE' . &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;here we face a mapping issue due to include structure concept. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is it possible that we could avoid this mapping issue?&amp;nbsp; and how ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks ,&lt;BR /&gt;Kevin&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Apr 2016 03:09:50 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/rfc-interface-mapping-issue/m-p/11640066#M1942947</guid>
      <dc:creator>kevin_wang6</dc:creator>
      <dc:date>2016-04-19T03:09:50Z</dc:date>
    </item>
    <item>
      <title>Re: RFC interface mapping issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/rfc-interface-mapping-issue/m-p/11640067#M1942948</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;problem doesn't because of the include structure.&amp;nbsp; is because of the mapping issue.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sorry , and case closed.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Apr 2016 05:45:56 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/rfc-interface-mapping-issue/m-p/11640067#M1942948</guid>
      <dc:creator>kevin_wang6</dc:creator>
      <dc:date>2016-04-19T05:45:56Z</dc:date>
    </item>
  </channel>
</rss>

