<?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: bdc - error logs in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/bdc-error-logs/m-p/871210#M49882</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;If your BI sessions were run with the option for keeping a log, you can use transaction SM35 to reprocess the session.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 21 Feb 2005 05:36:26 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2005-02-21T05:36:26Z</dc:date>
    <item>
      <title>bdc - error logs</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bdc-error-logs/m-p/871208#M49880</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello friends........can any one help me....how 2 find out the errors occured during batch input method , call transaction method and direct input method.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;for example..when uploading 100 records of data.... the error occured in the 60 th record...whr the error will be stored? ....what happens to the process?........n how to rectify it?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regds,&lt;/P&gt;&lt;P&gt;Ariff&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 Feb 2005 05:09:23 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bdc-error-logs/m-p/871208#M49880</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-02-21T05:09:23Z</dc:date>
    </item>
    <item>
      <title>Re: bdc - error logs</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bdc-error-logs/m-p/871209#M49881</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can reprocess the Session in ERROR Mode. You can rectify the data once the screen pops up in Error mode.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;hope this helps you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regds, Murugesh AS&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 Feb 2005 05:27:03 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bdc-error-logs/m-p/871209#M49881</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-02-21T05:27:03Z</dc:date>
    </item>
    <item>
      <title>Re: bdc - error logs</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bdc-error-logs/m-p/871210#M49882</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;If your BI sessions were run with the option for keeping a log, you can use transaction SM35 to reprocess the session.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 Feb 2005 05:36:26 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bdc-error-logs/m-p/871210#M49882</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-02-21T05:36:26Z</dc:date>
    </item>
    <item>
      <title>Re: bdc - error logs</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bdc-error-logs/m-p/871211#M49883</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ariff &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- SM35 -&amp;gt; analysis (or F2) &lt;/P&gt;&lt;P&gt;       -&amp;gt; log (F7) &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards Andreas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 Feb 2005 08:14:13 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bdc-error-logs/m-p/871211#M49883</guid>
      <dc:creator>andreas_mann3</dc:creator>
      <dc:date>2005-02-21T08:14:13Z</dc:date>
    </item>
    <item>
      <title>Re: bdc - error logs</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bdc-error-logs/m-p/871212#M49884</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ariff,&lt;/P&gt;&lt;P&gt;   If it is a 'Call transaction' method, then you have to pass the messages to an internal table with structure 'bdcmsgcoll'. Once you do this, you can read the various messages with the Message type and process this internal table and decide what whether to print or list or do any subsequent processings with the messages. You also get the message descriptions in this internal table. The syntax with an example is&lt;/P&gt;&lt;P&gt;CALL TRANSACTION 'ME21'  USING BDCDATA  MODE 'N' &lt;/P&gt;&lt;P&gt;                         MESSAGES INTO ITAB.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If it is 'session method' that you are using, the provision for tracking, viewing and further processing of meesages and errors are there within transaction sm35.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope things are clear and please award points if you find this info useful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;Madhavan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 Feb 2005 08:51:50 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bdc-error-logs/m-p/871212#M49884</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-02-21T08:51:50Z</dc:date>
    </item>
    <item>
      <title>Re: bdc - error logs</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bdc-error-logs/m-p/871213#M49885</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hello friends thanx for your replie........but if my batch input program runs in the background ...........how would i trap the errors?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thnx&lt;/P&gt;&lt;P&gt;Ariff&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 24 Feb 2005 05:57:42 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bdc-error-logs/m-p/871213#M49885</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-02-24T05:57:42Z</dc:date>
    </item>
    <item>
      <title>Re: bdc - error logs</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bdc-error-logs/m-p/871214#M49886</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;If you have marked the flag for KEEP='X' to retain the session, then you can still see them in SM35. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 24 Feb 2005 06:01:46 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bdc-error-logs/m-p/871214#M49886</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-02-24T06:01:46Z</dc:date>
    </item>
    <item>
      <title>Re: bdc - error logs</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bdc-error-logs/m-p/871215#M49887</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;   If you are using the Call transaction method in the background, then simply use the 'write' statement to write the messages and it appears in the log in sm37. &lt;/P&gt;&lt;P&gt;   If it is the session method, the log will anyway be there in sm35 provided the parameter KEEP = 'X' in function module 'BDC_OPEN_GROUP'.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;Madhavan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 Feb 2005 04:12:26 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bdc-error-logs/m-p/871215#M49887</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-02-25T04:12:26Z</dc:date>
    </item>
    <item>
      <title>Re: bdc - error logs</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bdc-error-logs/m-p/871216#M49888</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Try this code for error log in bdc it will get u all errors while loading a file . But the problem is if its a flat file thn u should validate it while downloading it to the SAP system. I mean validating the entries in the internal table before you actually call the transaction.That is effective for performance.&lt;/P&gt;&lt;P&gt;To get the SAP generated messages which are generated while the transaction here's the code.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DATA:   MESSTAB LIKE BDCMSGCOLL OCCURS 0 WITH HEADER LINE.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;LOOP AT MESSTAB.&lt;/P&gt;&lt;P&gt;  SELECT SINGLE * FROM T100 WHERE SPRSL = MESSTAB-MSGSPRA&lt;/P&gt;&lt;P&gt;                           AND   ARBGB = MESSTAB-MSGID&lt;/P&gt;&lt;P&gt;                           AND   MSGNR = MESSTAB-MSGNR.&lt;/P&gt;&lt;P&gt;      IF SY-SUBRC = 0.&lt;/P&gt;&lt;P&gt;        L_MSTRING = T100-TEXT.&lt;/P&gt;&lt;P&gt;        IF L_MSTRING CS '&amp;amp;1'.&lt;/P&gt;&lt;P&gt;          REPLACE '&amp;amp;1' WITH MESSTAB-MSGV1 INTO L_MSTRING.&lt;/P&gt;&lt;P&gt;          REPLACE '&amp;amp;2' WITH MESSTAB-MSGV2 INTO L_MSTRING.&lt;/P&gt;&lt;P&gt;          REPLACE '&amp;amp;3' WITH MESSTAB-MSGV3 INTO L_MSTRING.&lt;/P&gt;&lt;P&gt;          REPLACE '&amp;amp;4' WITH MESSTAB-MSGV4 INTO L_MSTRING.&lt;/P&gt;&lt;P&gt;        ELSE.&lt;/P&gt;&lt;P&gt;          REPLACE '&amp;amp;' WITH MESSTAB-MSGV1 INTO L_MSTRING.&lt;/P&gt;&lt;P&gt;          REPLACE '&amp;amp;' WITH MESSTAB-MSGV2 INTO L_MSTRING.&lt;/P&gt;&lt;P&gt;          REPLACE '&amp;amp;' WITH MESSTAB-MSGV3 INTO L_MSTRING.&lt;/P&gt;&lt;P&gt;          REPLACE '&amp;amp;' WITH MESSTAB-MSGV4 INTO L_MSTRING.&lt;/P&gt;&lt;P&gt;        ENDIF.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;        CONDENSE L_MSTRING.&lt;/P&gt;&lt;P&gt;        GV_MSG = L_MSTRING.&lt;/P&gt;&lt;P&gt;        IF T100-ARBGB NE 'M3' AND&lt;/P&gt;&lt;P&gt;             T100-MSGNR NE '800'.&lt;/P&gt;&lt;P&gt;      ELSE.&lt;/P&gt;&lt;P&gt;      ENDIF.&lt;/P&gt;&lt;P&gt;    ENDLOOP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    REFRESH MESSTAB.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 Feb 2005 04:56:16 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bdc-error-logs/m-p/871216#M49888</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-02-25T04:56:16Z</dc:date>
    </item>
    <item>
      <title>Re: bdc - error logs</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bdc-error-logs/m-p/871217#M49889</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;kindly rate the answer if it was of any help&lt;/P&gt;&lt;P&gt;Thanx &lt;/P&gt;&lt;P&gt;Varun&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 Feb 2005 08:21:45 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bdc-error-logs/m-p/871217#M49889</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-02-25T08:21:45Z</dc:date>
    </item>
  </channel>
</rss>

