<?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: buffer synchronization in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/buffer-synchronization/m-p/3449590#M828656</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;STRONG&gt;Buffer Synchronization&lt;/STRONG&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The fact that each application server has its own buffers could result in data inconsistency across the various application servers (instances). To prevent data inconsistency, the SAP System uses periodical buffer synchronization, which is sometimes called buffer refresh.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Every modifying action on buffered data, which could also be buffered by other application servers, produces synchronization telegrams that are written to a central DB table (DDLOG). Every application server periodically reads the telegrams written since the last synchronization, and checks its buffers for data to be refreshed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Buffer synchronization can be controlled by changing the following parameters in the  instance profile:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;rdisp/bufrefmode = sendon | sendoff, exeauto | exeoff &lt;/P&gt;&lt;P&gt;rdisp/bufreftime = (in seconds, time between two synchronization)&lt;/P&gt;&lt;P&gt;During the period between two refreshes, an application server may read data from its buffers while they are being modified by another application server. For this reason, no important volatile customer data should be buffered in the SAP buffers. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Examples of buffered data:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Table TSTC (SAP transaction codes)&lt;/P&gt;&lt;P&gt;Table T100 (error messages)&lt;/P&gt;&lt;P&gt;ABAP executables&lt;/P&gt;&lt;P&gt;Screens&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check this link for more..&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04s/helpdata/en/c4/3a6dd5505211d189550000e829fbbd/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04s/helpdata/en/c4/3a6dd5505211d189550000e829fbbd/content.htm&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 12 Feb 2008 06:43:32 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-02-12T06:43:32Z</dc:date>
    <item>
      <title>buffer synchronization</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/buffer-synchronization/m-p/3449589#M828655</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;what happens in buffer synchronization?if i need to access previous data from data base what i will do?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 12 Feb 2008 06:26:57 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/buffer-synchronization/m-p/3449589#M828655</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-12T06:26:57Z</dc:date>
    </item>
    <item>
      <title>Re: buffer synchronization</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/buffer-synchronization/m-p/3449590#M828656</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;STRONG&gt;Buffer Synchronization&lt;/STRONG&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The fact that each application server has its own buffers could result in data inconsistency across the various application servers (instances). To prevent data inconsistency, the SAP System uses periodical buffer synchronization, which is sometimes called buffer refresh.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Every modifying action on buffered data, which could also be buffered by other application servers, produces synchronization telegrams that are written to a central DB table (DDLOG). Every application server periodically reads the telegrams written since the last synchronization, and checks its buffers for data to be refreshed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Buffer synchronization can be controlled by changing the following parameters in the  instance profile:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;rdisp/bufrefmode = sendon | sendoff, exeauto | exeoff &lt;/P&gt;&lt;P&gt;rdisp/bufreftime = (in seconds, time between two synchronization)&lt;/P&gt;&lt;P&gt;During the period between two refreshes, an application server may read data from its buffers while they are being modified by another application server. For this reason, no important volatile customer data should be buffered in the SAP buffers. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Examples of buffered data:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Table TSTC (SAP transaction codes)&lt;/P&gt;&lt;P&gt;Table T100 (error messages)&lt;/P&gt;&lt;P&gt;ABAP executables&lt;/P&gt;&lt;P&gt;Screens&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check this link for more..&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04s/helpdata/en/c4/3a6dd5505211d189550000e829fbbd/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04s/helpdata/en/c4/3a6dd5505211d189550000e829fbbd/content.htm&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 12 Feb 2008 06:43:32 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/buffer-synchronization/m-p/3449590#M828656</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-12T06:43:32Z</dc:date>
    </item>
  </channel>
</rss>

