Skip to Content

Finding standard messages to re-use in custom programs without knowing the message class

Hello everyone,

Most of the times, the most boring procedure of development at least for my case is to create and translate messages in order to handle and inform the user for any kind of error or action required during the execution of a program. I’m use to create all objects in English language and then translate them to Greek.

I was wondering if there was a way to search for messages that can cover my needs without knowing the message class. Apart from the way to try to trigger the message in order to find it and reuse it ( If you are searching for a message saying ” Company code & is not defined ” is very easy to find it by executing transaction ‘FB01’ and entering a non-existing company code ) I wasn’t aware of any other way to search for messages.

Figure 1

Figure 2

Finally, I found that by using transaction SE80 –> Repository Information System –> Other Objects –> Message Numbers ( Fig. 1,2 ),

there is a standard tool that let you search for messages without knowing the message class.

From that time, many of the messages that I use in programs are reused from standard message classes giving most of the times a better result and slightly reduced work effort required. Also, have in mind that since we are talking for standard messages the possibility of SAP changing the message in a future release exists. Still, I believe that such a possibility is minor and I personally prefer to use this way than to create new messages.

Regards,

Laurent Fournier.

5 Comments
You must be Logged on to comment or reply to a post.
  • Hello Laurent,

    Very valid point. IMHO the very basic idea of creating message classes is re-usability.

    I've worked on projects:

    • where every report has it's own msg. class,
    • 4-5 custom msg. classes having the same message (e.g.,"Comp. Code &1 is not valid"'),
    • and the most bizzare one: same message occuring multiple times in one msg. class 😡

    I prefer accessing the Repository Info. System directly via SE84 🙂

    BR,

    Suhas

    • Hello Suhas,

      Thanks for your comment. In my case, I was used to use a standard message of class FR ( 999 ) and pass text-elements as a variable in order to display a message than to create a new message class. But, from the day that I have discovered the utility that helps me search for standard messages, in the 95% of the cases, I reuse the existing messages. In some strange cases that I cannot find a suitable message to reuse, I' m still using the standard placeholder message to cover my needs.

      Kind regards,

      Laurent.

      • Good one!.

        I always used SE16 on Table T100, does exactly the same trick (and you can specify a language) but your solution also works.

        • Hi,

          SE16 on Table T100 is also another alternative but the problem is that you cannot see if there is a long text behind the message. I always check if there is a long text or the message is self explanatory in order to make sure that the user will get the correct guidance even if he/she reads the long text. Most of the times off course, the long text is not applicable for the use that I want for the message so I prefer self explanatory messages.

          Regards.