<?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: session method in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/session-method/m-p/2279004#M496006</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;Session method. &lt;/P&gt;&lt;P&gt;error log is created &lt;/P&gt;&lt;P&gt;data is not updated until session is processed. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;from the error log we can update the 5 th and 8th record .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;u&amp;gt;&amp;lt;b&amp;gt;Call transaction.&amp;lt;/b&amp;gt;&amp;lt;/u&amp;gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;errors need to be handled explicitly &lt;/P&gt;&lt;P&gt; data is updated automatically &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For Update you have &lt;/P&gt;&lt;P&gt;A - asynchronus - does not wait for next update in the queue&lt;/P&gt;&lt;P&gt;S - Synchronus - waits until the previous update is completed before a new request is considered&lt;/P&gt;&lt;P&gt;L - Local update - Uses a different work process to trigger call function in update task.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In synchronus method until one record process takes place into database next record will not be processed. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In asynchronus immedate updation of data into database table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check this link for more detailed information:&lt;/P&gt;&lt;P&gt;&lt;A href="http://fuller.mit.edu/tech/sync_asynchronous.html" target="test_blank"&gt;http://fuller.mit.edu/tech/sync_asynchronous.html&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;'A', 'S' and 'L' are the update modes in CALL transaction method.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I will give you a simple example to explain this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Suppose that there are 30 records in total and an error has occured in the 5th record.&lt;/P&gt;&lt;P&gt; In asynchronous, update is done for every 30 records while in synchronous one,&lt;/P&gt;&lt;P&gt; update is done only upto the 4th record.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So only after the record in the fifth one is eliminated, remaining others are processed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rgds&lt;/P&gt;&lt;P&gt;Reshma&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 18 May 2007 09:52:46 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-05-18T09:52:46Z</dc:date>
    <item>
      <title>session method</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/session-method/m-p/2278999#M496001</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Iam updating 10 records . I had an error in 5 th and 8th record .&lt;/P&gt;&lt;P&gt;Will the remaining records get updated in session method.&lt;/P&gt;&lt;P&gt;What happens in call transaction method.&lt;/P&gt;&lt;P&gt;We need to process only error records or all records again in session method.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 May 2007 09:42:11 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/session-method/m-p/2278999#M496001</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-05-18T09:42:11Z</dc:date>
    </item>
    <item>
      <title>Re: session method</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/session-method/m-p/2279000#M496002</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;we can process error records only.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;first down loa that reacords and  correcr it and upload once again&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;pls reward if it helpful&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;P&gt;vana&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 May 2007 09:48:35 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/session-method/m-p/2279000#M496002</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-05-18T09:48:35Z</dc:date>
    </item>
    <item>
      <title>Re: session method</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/session-method/m-p/2279001#M496003</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi jeeven,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;in session method by default it can maintain log(error) file, that u can see in t.code 'sm35',&lt;/P&gt;&lt;P&gt;select your session name -&amp;gt;(which u have given in Function module 'BDC_OPEN_GROUP'  under group parameter.)&lt;/P&gt;&lt;P&gt;process-&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;then u can able to see the error records remaining all can updated in database.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if it's call transaction method then you should maintaion log file structure called BDCMSGCOLL.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards..&lt;/P&gt;&lt;P&gt;seshu.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 May 2007 09:49:16 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/session-method/m-p/2279001#M496003</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-05-18T09:49:16Z</dc:date>
    </item>
    <item>
      <title>Re: session method</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/session-method/m-p/2279002#M496004</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;    You can process only error records .open the log , correct the records and process the session  again .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Ranjita&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 May 2007 09:51:10 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/session-method/m-p/2279002#M496004</guid>
      <dc:creator>former_member196299</dc:creator>
      <dc:date>2007-05-18T09:51:10Z</dc:date>
    </item>
    <item>
      <title>Re: session method</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/session-method/m-p/2279003#M496005</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;U have to upload all the data again bcoz bdc session method doesnt update the record until n unless the session is not completed successfully.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Sunny&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 May 2007 09:51:46 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/session-method/m-p/2279003#M496005</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-05-18T09:51:46Z</dc:date>
    </item>
    <item>
      <title>Re: session method</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/session-method/m-p/2279004#M496006</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;Session method. &lt;/P&gt;&lt;P&gt;error log is created &lt;/P&gt;&lt;P&gt;data is not updated until session is processed. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;from the error log we can update the 5 th and 8th record .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;u&amp;gt;&amp;lt;b&amp;gt;Call transaction.&amp;lt;/b&amp;gt;&amp;lt;/u&amp;gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;errors need to be handled explicitly &lt;/P&gt;&lt;P&gt; data is updated automatically &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For Update you have &lt;/P&gt;&lt;P&gt;A - asynchronus - does not wait for next update in the queue&lt;/P&gt;&lt;P&gt;S - Synchronus - waits until the previous update is completed before a new request is considered&lt;/P&gt;&lt;P&gt;L - Local update - Uses a different work process to trigger call function in update task.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In synchronus method until one record process takes place into database next record will not be processed. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In asynchronus immedate updation of data into database table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check this link for more detailed information:&lt;/P&gt;&lt;P&gt;&lt;A href="http://fuller.mit.edu/tech/sync_asynchronous.html" target="test_blank"&gt;http://fuller.mit.edu/tech/sync_asynchronous.html&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;'A', 'S' and 'L' are the update modes in CALL transaction method.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I will give you a simple example to explain this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Suppose that there are 30 records in total and an error has occured in the 5th record.&lt;/P&gt;&lt;P&gt; In asynchronous, update is done for every 30 records while in synchronous one,&lt;/P&gt;&lt;P&gt; update is done only upto the 4th record.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So only after the record in the fifth one is eliminated, remaining others are processed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rgds&lt;/P&gt;&lt;P&gt;Reshma&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 May 2007 09:52:46 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/session-method/m-p/2279004#M496006</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-05-18T09:52:46Z</dc:date>
    </item>
  </channel>
</rss>

