<?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: check table caused RFC parameter compatible issue in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/check-table-caused-rfc-parameter-compatible-issue/m-p/485038#M16084</link>
    <description>&lt;P&gt;I bet Horst Keller could explain this and he even works at the same company!&lt;/P&gt;&lt;P&gt;To be honest, you lost me here - at first you're saying "someone change[d] the check table" but then "don't see any field changed". Might want to get the story straight. "How this happened" - how what happened?&lt;/P&gt;&lt;P&gt;Otherwise this is just ABAP 101 IMHO. Use dictionary definitions to call RFC and maintain consistent definitions. Whoever is changing dictionary must make sure the change won't break anything. &lt;/P&gt;&lt;P&gt;Rather confused by this question...&lt;/P&gt;</description>
    <pubDate>Mon, 20 Mar 2017 20:32:57 GMT</pubDate>
    <dc:creator>Jelena_Perfiljeva</dc:creator>
    <dc:date>2017-03-20T20:32:57Z</dc:date>
    <item>
      <title>check table caused RFC parameter compatible issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/check-table-caused-rfc-parameter-compatible-issue/m-p/485037#M16083</link>
      <description>&lt;P&gt;Hello experts, &lt;/P&gt;&lt;P&gt;I see a RFC, one of the parameter PAR1 has a type of a DDIC structure ZSTR (Field of ZSTR has a check table which refer to a DDIC table), and ZSTR contains 1 include (.INCLUDE abc) structure which contain all the fields. &lt;/P&gt;&lt;P&gt;when calling this RFC, the local structure for this parameter is refer to a local structure type. &lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;TYPES: BEGIN OF ty_str.
         include abc.
TYPES: END OF ty_str.
data ls_str type ty_str.
CALL FUNCTION 'RFC'
  IMPORTING 
    PAR1 = ls_str

&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;The local structure LS_STR has exactly the same structure as ZSTR.&lt;/P&gt;&lt;P&gt;RFC went well until someone change the check table of the field in ZSTR, the check table is now referred to a view.  currently, the local structure type is not compatible with the RFC parameter, it always cause a dump.  but I don't see any field changed,  Can someone explain me how this happened ?&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Kevin&lt;/P&gt;</description>
      <pubDate>Wed, 15 Mar 2017 03:32:53 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/check-table-caused-rfc-parameter-compatible-issue/m-p/485037#M16083</guid>
      <dc:creator>kevin_wang6</dc:creator>
      <dc:date>2017-03-15T03:32:53Z</dc:date>
    </item>
    <item>
      <title>Re: check table caused RFC parameter compatible issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/check-table-caused-rfc-parameter-compatible-issue/m-p/485038#M16084</link>
      <description>&lt;P&gt;I bet Horst Keller could explain this and he even works at the same company!&lt;/P&gt;&lt;P&gt;To be honest, you lost me here - at first you're saying "someone change[d] the check table" but then "don't see any field changed". Might want to get the story straight. "How this happened" - how what happened?&lt;/P&gt;&lt;P&gt;Otherwise this is just ABAP 101 IMHO. Use dictionary definitions to call RFC and maintain consistent definitions. Whoever is changing dictionary must make sure the change won't break anything. &lt;/P&gt;&lt;P&gt;Rather confused by this question...&lt;/P&gt;</description>
      <pubDate>Mon, 20 Mar 2017 20:32:57 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/check-table-caused-rfc-parameter-compatible-issue/m-p/485038#M16084</guid>
      <dc:creator>Jelena_Perfiljeva</dc:creator>
      <dc:date>2017-03-20T20:32:57Z</dc:date>
    </item>
  </channel>
</rss>

