<?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: application log or spool message in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/application-log-or-spool-message/m-p/5629719#M1281864</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 use some error mechanism and terminate the program.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the error is a critical one you can send an error by e-mail to specified users for prompt response.&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;Krishna&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 06 May 2009 13:00:01 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2009-05-06T13:00:01Z</dc:date>
    <item>
      <title>application log or spool message</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/application-log-or-spool-message/m-p/5629717#M1281862</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello People,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I want to know best practices regarding implementation of batch/background programs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My question is:&lt;/P&gt;&lt;P&gt;1. Do you use any error mechanism if sy-subrc fails e.g. en-queue function module fails and return sy-subrc = '1' ... in that case do you just terminate your program or use some error mechanism and then terminate it (I want to know industry best practice). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. Also which is the best error mechanism available (easy and performance oriented)&lt;/P&gt;&lt;P&gt;i.e. app. log, bpem or simple spool message etc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any documentation/url would be of great help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;P&gt;Kind Regards,&lt;/P&gt;&lt;P&gt;Nikhil J.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN __default_attr="red" __jive_macro_name="color"&gt;Moderator message - Moved to the correct forum&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Rob Burbank on May 6, 2009 9:30 AM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 May 2009 09:19:51 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/application-log-or-spool-message/m-p/5629717#M1281862</guid>
      <dc:creator>former_member221838</dc:creator>
      <dc:date>2009-05-06T09:19:51Z</dc:date>
    </item>
    <item>
      <title>Re: application log or spool message</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/application-log-or-spool-message/m-p/5629718#M1281863</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;   First some error mechanism and then termination is prefferable. Application error is generally used one. if specifically spool message required means then spool message will be used.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Suma.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 May 2009 12:33:09 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/application-log-or-spool-message/m-p/5629718#M1281863</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-05-06T12:33:09Z</dc:date>
    </item>
    <item>
      <title>Re: application log or spool message</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/application-log-or-spool-message/m-p/5629719#M1281864</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 use some error mechanism and terminate the program.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the error is a critical one you can send an error by e-mail to specified users for prompt response.&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;Krishna&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 May 2009 13:00:01 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/application-log-or-spool-message/m-p/5629719#M1281864</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-05-06T13:00:01Z</dc:date>
    </item>
    <item>
      <title>Re: application log or spool message</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/application-log-or-spool-message/m-p/5629720#M1281865</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Simply giving the error message is enough. &lt;/P&gt;&lt;P&gt;An error message will terminate the backgroud job, rollback any database update and you will be abe to see the job in cancelled state.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, you program may require any custom error handling procedure..e.g. sending mail , notifying user or starting a work flow.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 May 2009 13:16:25 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/application-log-or-spool-message/m-p/5629720#M1281865</guid>
      <dc:creator>Pawan_Kesari</dc:creator>
      <dc:date>2009-05-06T13:16:25Z</dc:date>
    </item>
  </channel>
</rss>

