<?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 Application Log Class in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/application-log-class/m-p/1607398#M272595</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all -&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;About to commence new implementation of NW2004s.  ECC, Sol. Mgr. and BI in-scope.  XI and EP out of scope.  Have to construct some generic exception handling for custom programs (i.e. interfaces that run batch). Specifically, the handling of messaging of different types (E.g. writing to appl. log, email, paging, etc.) and cleanup on exceptions.  Anyone out there designed/implemented such an infra-structure and can provide design/code?  (Note, I am familiar with class-based exception handling, what I require is a generic framework to handle all exceptions, message appropriately and clean-up if necessary.) Can Sol. Mgr monitor application logs and message (Email/page/etc.) based on messages written to application log?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, is there an application log class now available in 6.40 to replace FMs in FG SBAL (Application Log: Collect Messages).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your help,&lt;/P&gt;&lt;P&gt;Pat&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 14 Sep 2006 13:37:24 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2006-09-14T13:37:24Z</dc:date>
    <item>
      <title>Application Log Class</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/application-log-class/m-p/1607398#M272595</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all -&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;About to commence new implementation of NW2004s.  ECC, Sol. Mgr. and BI in-scope.  XI and EP out of scope.  Have to construct some generic exception handling for custom programs (i.e. interfaces that run batch). Specifically, the handling of messaging of different types (E.g. writing to appl. log, email, paging, etc.) and cleanup on exceptions.  Anyone out there designed/implemented such an infra-structure and can provide design/code?  (Note, I am familiar with class-based exception handling, what I require is a generic framework to handle all exceptions, message appropriately and clean-up if necessary.) Can Sol. Mgr monitor application logs and message (Email/page/etc.) based on messages written to application log?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, is there an application log class now available in 6.40 to replace FMs in FG SBAL (Application Log: Collect Messages).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your help,&lt;/P&gt;&lt;P&gt;Pat&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 Sep 2006 13:37:24 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/application-log-class/m-p/1607398#M272595</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-09-14T13:37:24Z</dc:date>
    </item>
    <item>
      <title>Re: Application Log Class</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/application-log-class/m-p/1607399#M272596</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Pat&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I cannot provide you with an entire "message handling framework" but at least I can tell you which class I frequently use for message handling and logging:&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;CL_RECA_MESSAGE_LIST&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When you create an instance (CF_RECA_MESSAGE_LIST=&amp;gt;CREATE) you can link the instance to a log object.&lt;/P&gt;&lt;P&gt;A very nice feature of this class is method &lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;ADD_FROM_INSTANCE&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt; which is particularly useful if you have a composition of objects which all send messages and you want to collect all these messages in the "outermost" instance.&lt;/P&gt;&lt;P&gt;If you are familiar with logging it will be clear what method &lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;GET_HANDLE&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt; does.&lt;/P&gt;&lt;P&gt;The sample report SBAL_DEMO_04_CONTROL shows how to display a log in an ALV control.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope I could give you some insights.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;  Uwe&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 Sep 2006 22:52:12 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/application-log-class/m-p/1607399#M272596</guid>
      <dc:creator>uwe_schieferstein</dc:creator>
      <dc:date>2006-09-14T22:52:12Z</dc:date>
    </item>
  </channel>
</rss>

