<?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 Changing message from BAPI in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/changing-message-from-bapi/m-p/8810273#M1681097</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;I have implemented BADI WORKBREAKDOWN_UPDATE. I have added some coding in the AT_SAVE method. It works great. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Only a small issue though, when the coding finds an error, exception ERROR_WITH_MESSAGE is raised. &lt;/P&gt;&lt;P&gt;This will result in a simple error message, but I would like to give the user some more information why the error occurred.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So, is it possible to change, or add some extra information to the error message given?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;many thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ron.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 30 May 2012 11:48:29 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2012-05-30T11:48:29Z</dc:date>
    <item>
      <title>Changing message from BAPI</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/changing-message-from-bapi/m-p/8810273#M1681097</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;I have implemented BADI WORKBREAKDOWN_UPDATE. I have added some coding in the AT_SAVE method. It works great. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Only a small issue though, when the coding finds an error, exception ERROR_WITH_MESSAGE is raised. &lt;/P&gt;&lt;P&gt;This will result in a simple error message, but I would like to give the user some more information why the error occurred.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So, is it possible to change, or add some extra information to the error message given?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;many thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ron.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 May 2012 11:48:29 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/changing-message-from-bapi/m-p/8810273#M1681097</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2012-05-30T11:48:29Z</dc:date>
    </item>
    <item>
      <title>Re: Changing message from BAPI</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/changing-message-from-bapi/m-p/8810274#M1681098</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If you can change the error message in SE91, add long text to the error message. So when user clicks the message he can see the whole reason why it went wrong.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 May 2012 11:57:48 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/changing-message-from-bapi/m-p/8810274#M1681098</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2012-05-30T11:57:48Z</dc:date>
    </item>
    <item>
      <title>Re: Changing message from BAPI</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/changing-message-from-bapi/m-p/8810275#M1681099</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear Ron,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As the BAPI raises exceptions at multiple instances, it will be a huge task change or add details to the messages. Also, as these messages are stored as part of Standard message classes, changing the messages in the standard message class will also be cause changes across the application.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Practically, not recommended.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Finally, if it is a very custom requirement that you have already enhanced and the error message is &lt;/P&gt;&lt;P&gt;also raised in the same routine, you can attempt to override the exceptions if it is in an enhancement section.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards, Pranav.&lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_macro_emoticon jive_emote" height="1" src="https://community.sap.com/777/images/emoticons/happy.gif" width="1"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 May 2012 12:00:36 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/changing-message-from-bapi/m-p/8810275#M1681099</guid>
      <dc:creator>former_member222709</dc:creator>
      <dc:date>2012-05-30T12:00:36Z</dc:date>
    </item>
    <item>
      <title>Re: Changing message from BAPI</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/changing-message-from-bapi/m-p/8810276#M1681100</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Replace the&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;P&gt;raise error_with_message.&lt;/P&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;with a&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;P&gt;message id wa-msgid type wa-msgty number wa-msgno&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; with wa-msgv1 wa-msgv2 wa-msgv3 wa-msgv4&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; raising error_with_message.&lt;/P&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;Did you look at sample CL_EX_WORKBREAKDOWN_UPDATE ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Raymond&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 May 2012 12:18:18 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/changing-message-from-bapi/m-p/8810276#M1681100</guid>
      <dc:creator>RaymondGiuseppi</dc:creator>
      <dc:date>2012-05-30T12:18:18Z</dc:date>
    </item>
    <item>
      <title>Re: Changing message from BAPI</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/changing-message-from-bapi/m-p/8810277#M1681101</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Raymond,&lt;/P&gt;&lt;P&gt;Your solution worked like a charm!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;Ron.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I altered the statement as follows:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;P&gt;&lt;SPAN class="L0S52"&gt;message &lt;/SPAN&gt;&lt;SPAN class="L0S52"&gt;id &lt;/SPAN&gt;sy&lt;SPAN class="L0S70"&gt;-&lt;/SPAN&gt;msgid &lt;SPAN class="L0S52"&gt;type &lt;/SPAN&gt;&lt;SPAN class="L0S33"&gt;'I' &lt;/SPAN&gt;&lt;SPAN class="L0S52"&gt;number &lt;/SPAN&gt;sy&lt;SPAN class="L0S70"&gt;-&lt;/SPAN&gt;msgno &lt;SPAN class="L0S52"&gt;with &lt;/SPAN&gt;sy&lt;SPAN class="L0S70"&gt;-&lt;/SPAN&gt;msgv1 sy&lt;SPAN class="L0S70"&gt;-&lt;/SPAN&gt;msgv2 &lt;SPAN class="L0S33"&gt;'doesnt'&lt;/SPAN&gt;&lt;SPAN class="L0S33"&gt;'t allow a billing flag' &lt;/SPAN&gt;&lt;SPAN class="L0S33"&gt;''&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;SPAN class="L0S52"&gt;raising &lt;/SPAN&gt;error_with_message&lt;SPAN class="L0S55"&gt;.&lt;/SPAN&gt;&lt;/P&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 May 2012 12:55:14 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/changing-message-from-bapi/m-p/8810277#M1681101</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2012-05-30T12:55:14Z</dc:date>
    </item>
  </channel>
</rss>

