<?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: clientdata Vs clientdatax in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/clientdata-vs-clientdatax/m-p/2812629#M657544</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Shipra,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The corresponding fields in the tables (such as CLIENTDATA) must first be supplied with data by the calling program. An indicator must also be set for each of these fields so that the data is written to the database by the method. This requires the calling program to supply the corresponding field with the indicator in a checkbox table (for example, CLIENTDATAX). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can have this information in the function module documentation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Aneesh.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 02 Oct 2007 17:49:31 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-10-02T17:49:31Z</dc:date>
    <item>
      <title>clientdata Vs clientdatax</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/clientdata-vs-clientdatax/m-p/2812628#M657543</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;When we call FM  "BAPI_MATERIAL_SAVEDATA"&lt;/P&gt;&lt;P&gt;we get EXPORTING parameters like this&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;clientdata = &lt;/P&gt;&lt;P&gt;clientdatax =&lt;/P&gt;&lt;P&gt;plantdata =&lt;/P&gt;&lt;P&gt;plantdatax = &lt;/P&gt;&lt;P&gt;storagelocationdata = &lt;/P&gt;&lt;P&gt;storagelocationdatax = &lt;/P&gt;&lt;P&gt;AND SO ON.............&lt;/P&gt;&lt;P&gt;I am not able to understand the difference between &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;clientdata and clientdatax &lt;/P&gt;&lt;P&gt;plantdata  and plantdatax&lt;/P&gt;&lt;P&gt;storagelocationdata and storagelocationdatax&lt;/P&gt;&lt;P&gt;and so on.............&lt;/P&gt;&lt;P&gt;what is this 'x' thing for every parameters?????&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Oct 2007 17:33:22 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/clientdata-vs-clientdatax/m-p/2812628#M657543</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-10-02T17:33:22Z</dc:date>
    </item>
    <item>
      <title>Re: clientdata Vs clientdatax</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/clientdata-vs-clientdatax/m-p/2812629#M657544</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Shipra,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The corresponding fields in the tables (such as CLIENTDATA) must first be supplied with data by the calling program. An indicator must also be set for each of these fields so that the data is written to the database by the method. This requires the calling program to supply the corresponding field with the indicator in a checkbox table (for example, CLIENTDATAX). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can have this information in the function module documentation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Aneesh.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Oct 2007 17:49:31 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/clientdata-vs-clientdatax/m-p/2812629#M657544</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-10-02T17:49:31Z</dc:date>
    </item>
  </channel>
</rss>

