2012 May 30 12:48 PM
Hi All,
I have implemented BADI WORKBREAKDOWN_UPDATE. I have added some coding in the AT_SAVE method. It works great.
Only a small issue though, when the coding finds an error, exception ERROR_WITH_MESSAGE is raised.
This will result in a simple error message, but I would like to give the user some more information why the error occurred.
So, is it possible to change, or add some extra information to the error message given?
many thanks,
regards,
Ron.
2012 May 30 1:18 PM
2012 May 30 12:57 PM
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.
2012 May 30 1:00 PM
Dear Ron,
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.
Practically, not recommended.
Finally, if it is a very custom requirement that you have already enhanced and the error message is
also raised in the same routine, you can attempt to override the exceptions if it is in an enhancement section.
Regards, Pranav.
2012 May 30 1:18 PM
2012 May 30 1:55 PM
Thanks Raymond,
Your solution worked like a charm!
regards,
Ron.
I altered the statement as follows:
message id sy-msgid type 'I' number sy-msgno with sy-msgv1 sy-msgv2 'doesnt''t allow a billing flag' ''
raising error_with_message.