<?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: communication structures in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/communication-structures/m-p/1116092#M107473</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;No, they have nothing to do with external communications or BAPIs. Please don't go by their description. They are like any other structure used to hold temporary data until it is finally passed to the database. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The 'X' structures are specifically used for BAPIs.&lt;/P&gt;&lt;P&gt;The term communication is used to loosely refer to the communication between the data entered on the screen and the final database table in which they will be stored. The communication structures are generated if you change the standard either through config(for pricing communication structures) or user exits(changing VBAP or VBAK etc). So in a way these structures are dynamic in nature, in that, they adjust according to your system. Compare that with any static structure that doesn't change just by changing config or using user exits.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 31 Jan 2006 22:23:10 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2006-01-31T22:23:10Z</dc:date>
    <item>
      <title>communication structures</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/communication-structures/m-p/1116091#M107472</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi all,&lt;/P&gt;&lt;P&gt;what actually is the purpose of communication structures in SAP like VBAKKOM, VBAKKOMX,VBAPKOM etc.&lt;/P&gt;&lt;P&gt;are they for the BAPI's called from remote sytems to communicate with SAP tables and fields?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 31 Jan 2006 22:10:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/communication-structures/m-p/1116091#M107472</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-01-31T22:10:05Z</dc:date>
    </item>
    <item>
      <title>Re: communication structures</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/communication-structures/m-p/1116092#M107473</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;No, they have nothing to do with external communications or BAPIs. Please don't go by their description. They are like any other structure used to hold temporary data until it is finally passed to the database. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The 'X' structures are specifically used for BAPIs.&lt;/P&gt;&lt;P&gt;The term communication is used to loosely refer to the communication between the data entered on the screen and the final database table in which they will be stored. The communication structures are generated if you change the standard either through config(for pricing communication structures) or user exits(changing VBAP or VBAK etc). So in a way these structures are dynamic in nature, in that, they adjust according to your system. Compare that with any static structure that doesn't change just by changing config or using user exits.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 31 Jan 2006 22:23:10 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/communication-structures/m-p/1116092#M107473</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-01-31T22:23:10Z</dc:date>
    </item>
  </channel>
</rss>

