<?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 BDC Session Method in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/error-handling-bdc-session-method/m-p/624513#M26115</link>
    <description>&lt;P&gt;&lt;EM&gt;When i have 10000+ transactions to be originally loaded from a flat file into the SAP using BDC session method and, of which, 3500+ transactions contains errors then, what is the best way to handle/correct/remove these errors and ensure that we have 100% data conversion achieved without duplicating any transaction?&lt;/EM&gt;&lt;/P&gt;
  &lt;P&gt;&lt;/P&gt;
  &lt;P&gt;3.5K errored transactions.. hunch is this could be improper data.. &lt;/P&gt;
  &lt;P&gt;Download, Sort/See Errored messages&lt;/P&gt;
  &lt;P&gt;Locate the errored pattern &amp;amp; fix it.&lt;/P&gt;
  &lt;P&gt;You might know this already, just again to bolster it.&lt;/P&gt;
  &lt;P&gt;SM35 ==&amp;gt; Choose your session ==&amp;gt; Log ==&amp;gt; Print&lt;/P&gt;
  &lt;P&gt;Download the errors to your Desktop&lt;/P&gt;
  &lt;P&gt;&lt;/P&gt;
  &lt;P&gt;Hope this helps you.&lt;/P&gt;</description>
    <pubDate>Tue, 03 Apr 2018 04:00:33 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2018-04-03T04:00:33Z</dc:date>
    <item>
      <title>Error Handling BDC Session Method</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/error-handling-bdc-session-method/m-p/624508#M26110</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt;When i have 10000+ transactions to be originally loaded from a flat file into the SAP using BDC session method and, of which, 3500+ transactions contains errors then, what is the best way to handle/correct/remove these errors and ensure that we have 100% data conversion achieved without duplicating any transaction?&lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt;Best Regards,&lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt;Vishwanath&lt;/P&gt;</description>
      <pubDate>Mon, 02 Apr 2018 18:15:46 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/error-handling-bdc-session-method/m-p/624508#M26110</guid>
      <dc:creator>VishwanathV</dc:creator>
      <dc:date>2018-04-02T18:15:46Z</dc:date>
    </item>
    <item>
      <title>Re: Error Handling BDC Session Method</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/error-handling-bdc-session-method/m-p/624509#M26111</link>
      <description>&lt;P&gt;Hard to help without knowing the transaction that you made a BDC for, and not knowing what kind of errors these are.&lt;/P&gt;
  &lt;P&gt;How many equal errors are there, how many different errors?&lt;/P&gt;</description>
      <pubDate>Mon, 02 Apr 2018 18:25:21 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/error-handling-bdc-session-method/m-p/624509#M26111</guid>
      <dc:creator>JL23</dc:creator>
      <dc:date>2018-04-02T18:25:21Z</dc:date>
    </item>
    <item>
      <title>Re: Error Handling BDC Session Method</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/error-handling-bdc-session-method/m-p/624510#M26112</link>
      <description>&lt;P&gt;Hi Jurgen,&lt;/P&gt;
  &lt;P&gt;&lt;/P&gt;
  &lt;P&gt;The data at hand is specific to sales orders for which we are using recording on VA01 tcode to load the data into SAP. The errors encountered are largely categorized into missing inco-terms, incorrect UoMs for materials used and missing Sold-Tos in SAP.&lt;/P&gt;
  &lt;P&gt;&lt;/P&gt;
  &lt;P&gt;Are these errors to be addressed manually for each errorneous transaction?&lt;/P&gt;
  &lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 02 Apr 2018 18:43:13 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/error-handling-bdc-session-method/m-p/624510#M26112</guid>
      <dc:creator>VishwanathV</dc:creator>
      <dc:date>2018-04-02T18:43:13Z</dc:date>
    </item>
    <item>
      <title>Re: Error Handling BDC Session Method</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/error-handling-bdc-session-method/m-p/624511#M26113</link>
      <description>&lt;P&gt;Yes and no, there is no automatism to process errors from batch input sessions, you need to run it foreground (errors only mode) to take care about the errors manually.&lt;/P&gt;
  &lt;P&gt;3500+ is a large number and you may need to sit for some days to get this all through.&lt;/P&gt;
  &lt;P&gt;But partially it depends on the messages. How can there be no sold-to when you process VA01? If it would be a master data issue then you cannot resolve it by processing the BDC in foreground, then you would need to maintain the customers and materials correctly and can finally just re-run the BDC again and it will process all transactions and only the others errors would remain, maybe you get new messages when the previously missing sold-to is then not maintained with Incoterms either.&lt;/P&gt;
  &lt;P&gt;Actually doing a BDC requires a bit of ABAP knowledge, and with a bit of ABAP knowledge you can validate the data when you create the batch input sessions, before you just blindly execute such a batch input session. &lt;/P&gt;
  &lt;P&gt;It is even hard now to find out which of your source data got processed and which part ended in errors. If you identify that then you can separate them in your source file and create for the faulty records a new batch input where you do validations and do eventually programmatic adjustments with defaults (or you just give this error part back to the person who gave it to you to complete it with correct information)&lt;/P&gt;
  &lt;P&gt;&lt;/P&gt;
  &lt;P&gt;&lt;BR /&gt;&lt;/P&gt;
  &lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 02 Apr 2018 18:59:34 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/error-handling-bdc-session-method/m-p/624511#M26113</guid>
      <dc:creator>JL23</dc:creator>
      <dc:date>2018-04-02T18:59:34Z</dc:date>
    </item>
    <item>
      <title>Re: Error Handling BDC Session Method</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/error-handling-bdc-session-method/m-p/624512#M26114</link>
      <description>&lt;P&gt;Remove successful records from flat file and correct INCO terms in flat file and re run it. it will correct all. &lt;/P&gt;</description>
      <pubDate>Mon, 02 Apr 2018 19:37:50 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/error-handling-bdc-session-method/m-p/624512#M26114</guid>
      <dc:creator>kasralikarpratik</dc:creator>
      <dc:date>2018-04-02T19:37:50Z</dc:date>
    </item>
    <item>
      <title>Re: Error Handling BDC Session Method</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/error-handling-bdc-session-method/m-p/624513#M26115</link>
      <description>&lt;P&gt;&lt;EM&gt;When i have 10000+ transactions to be originally loaded from a flat file into the SAP using BDC session method and, of which, 3500+ transactions contains errors then, what is the best way to handle/correct/remove these errors and ensure that we have 100% data conversion achieved without duplicating any transaction?&lt;/EM&gt;&lt;/P&gt;
  &lt;P&gt;&lt;/P&gt;
  &lt;P&gt;3.5K errored transactions.. hunch is this could be improper data.. &lt;/P&gt;
  &lt;P&gt;Download, Sort/See Errored messages&lt;/P&gt;
  &lt;P&gt;Locate the errored pattern &amp;amp; fix it.&lt;/P&gt;
  &lt;P&gt;You might know this already, just again to bolster it.&lt;/P&gt;
  &lt;P&gt;SM35 ==&amp;gt; Choose your session ==&amp;gt; Log ==&amp;gt; Print&lt;/P&gt;
  &lt;P&gt;Download the errors to your Desktop&lt;/P&gt;
  &lt;P&gt;&lt;/P&gt;
  &lt;P&gt;Hope this helps you.&lt;/P&gt;</description>
      <pubDate>Tue, 03 Apr 2018 04:00:33 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/error-handling-bdc-session-method/m-p/624513#M26115</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2018-04-03T04:00:33Z</dc:date>
    </item>
  </channel>
</rss>

