<?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: Error handling in session method in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/error-handling-in-session-method/m-p/4952423#M1154713</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;as per your question as in session method once you run the program and then in SM35 we can check the error log,for the particular session if check analysis we can find the errors for paticular transaction,in session method it can't give return value like sy-subrc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;in call transaction method it can return the sy-subrc ,if sy-subrc is not equal to 0 ,call to formate_message then error records r stored in internal table like bdcmsgcall,and in call transaction method can run in foregroung and back ground and once u get the error records then upload the records.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Madhu&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 02 Jan 2009 11:03:02 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2009-01-02T11:03:02Z</dc:date>
    <item>
      <title>Error handling in session method</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/error-handling-in-session-method/m-p/4952420#M1154710</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Experts,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm doing Asset Mass deletion using BDC session method, program executes successfully when the asset doesn't contain any values or else error message( ' Deleting is not possible. The asset already has values.' ) is thrown while uploading by foreground process. How to handle this errors &amp;amp; upload the rest of the assets without values for deletion?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Kavitha&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Dec 2008 08:28:55 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/error-handling-in-session-method/m-p/4952420#M1154710</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-12-24T08:28:55Z</dc:date>
    </item>
    <item>
      <title>Re: Error handling in session method</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/error-handling-in-session-method/m-p/4952421#M1154711</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;Better U proceed with CALL TRANSACTION method and check the return code(SY-SUBRC) after the statement call and  if it is NE zero then open a error session to insert the error records. By this way you can move the error records to session and proceed with the rest of the data records.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Hakim&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Dec 2008 09:29:30 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/error-handling-in-session-method/m-p/4952421#M1154711</guid>
      <dc:creator>abdul_hakim</dc:creator>
      <dc:date>2008-12-24T09:29:30Z</dc:date>
    </item>
    <item>
      <title>Re: Error handling in session method</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/error-handling-in-session-method/m-p/4952422#M1154712</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;In this case I suggest you to go for call transaction method and you can check the return code sy-subrc after calling the call transaction. If it is not equal zero then capture the error messages. Open the error session to insert the all error records.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Jyothi CH.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 Dec 2008 10:40:54 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/error-handling-in-session-method/m-p/4952422#M1154712</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-12-30T10:40:54Z</dc:date>
    </item>
    <item>
      <title>Re: Error handling in session method</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/error-handling-in-session-method/m-p/4952423#M1154713</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;as per your question as in session method once you run the program and then in SM35 we can check the error log,for the particular session if check analysis we can find the errors for paticular transaction,in session method it can't give return value like sy-subrc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;in call transaction method it can return the sy-subrc ,if sy-subrc is not equal to 0 ,call to formate_message then error records r stored in internal table like bdcmsgcall,and in call transaction method can run in foregroung and back ground and once u get the error records then upload the records.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Madhu&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Jan 2009 11:03:02 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/error-handling-in-session-method/m-p/4952423#M1154713</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-01-02T11:03:02Z</dc:date>
    </item>
    <item>
      <title>Re: Error handling in session method</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/error-handling-in-session-method/m-p/4952424#M1154714</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Problem solved after using CAll transaction method&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Mar 2009 04:35:03 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/error-handling-in-session-method/m-p/4952424#M1154714</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-03-10T04:35:03Z</dc:date>
    </item>
    <item>
      <title>Re: Error handling in session method</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/error-handling-in-session-method/m-p/4952425#M1154715</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Problem solved after using CAll transaction method&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Mar 2009 04:35:07 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/error-handling-in-session-method/m-p/4952425#M1154715</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-03-10T04:35:07Z</dc:date>
    </item>
  </channel>
</rss>

