<?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 Message handling in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/message-handling/m-p/4539592#M1072479</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;I've got a fundamental question:&lt;/P&gt;&lt;P&gt;I have to write a program which should give messages about the result of the program run (as nearly every program does &lt;SPAN __jive_emoticon_name="wink"&gt;&lt;/SPAN&gt; ). In addition to that the result should be sent via email.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am using a program as template which uses only WRITE statements to achieve that (the business requirements are quite equal). But honestly I don't like that, because you always have a mixture of your business logic with the messages that are written. I prefer to have the messages written at the end of the program.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In former projects I always used the structures BAPIRET2 to store my messages during the program run (I worked a lot with BAPIs at that time). And in the end I used the function BAL_DSP_LOG_DISPLAY or BAL_DSP_LOG_SAVE to show/save these messages.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In your opinion, is that the approach that I should use for the future? Can I combine that with using messages classes? Could you please give me an example?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Or is my approach not the best one? If so, I am open to alternatives...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 30 Sep 2008 08:09:44 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-09-30T08:09:44Z</dc:date>
    <item>
      <title>Message handling</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/message-handling/m-p/4539592#M1072479</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;I've got a fundamental question:&lt;/P&gt;&lt;P&gt;I have to write a program which should give messages about the result of the program run (as nearly every program does &lt;SPAN __jive_emoticon_name="wink"&gt;&lt;/SPAN&gt; ). In addition to that the result should be sent via email.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am using a program as template which uses only WRITE statements to achieve that (the business requirements are quite equal). But honestly I don't like that, because you always have a mixture of your business logic with the messages that are written. I prefer to have the messages written at the end of the program.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In former projects I always used the structures BAPIRET2 to store my messages during the program run (I worked a lot with BAPIs at that time). And in the end I used the function BAL_DSP_LOG_DISPLAY or BAL_DSP_LOG_SAVE to show/save these messages.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In your opinion, is that the approach that I should use for the future? Can I combine that with using messages classes? Could you please give me an example?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Or is my approach not the best one? If so, I am open to alternatives...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 Sep 2008 08:09:44 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/message-handling/m-p/4539592#M1072479</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-09-30T08:09:44Z</dc:date>
    </item>
    <item>
      <title>Re: Message handling</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/message-handling/m-p/4539593#M1072480</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ok, I've no found some interesting example programs in package SZAL (programs SBAL_DEMO_*).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I also found the class CL_SBAL_LOGGER.&lt;/P&gt;&lt;P&gt;I think I will copy this one and add some own code, because I want to display the messages in a hierarchical structure as it is done in SBAL_DEMO_04_DETLEVEL.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The only problem that remains is how to send these logs via email. Could you please advice me on this?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 Sep 2008 08:39:20 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/message-handling/m-p/4539593#M1072480</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-09-30T08:39:20Z</dc:date>
    </item>
  </channel>
</rss>

