Skip to content

Latest commit

 

History

History
43 lines (27 loc) · 1.27 KB

message-easy-to-find.md

File metadata and controls

43 lines (27 loc) · 1.27 KB
Raw

code pal for ABAP > Documentation > Message Easy To Find

Message Easy To Find

What is the intent of the check?

Since the specification of message classes and numbers by variables creates no entry in the where-used list of the corresponding message, this check searches for MESSAGE statements that do not statically specify their message by literals since these cannot be found in the where-used list of the message.

How to solve the issue?

Specify the message used by literals.

What to do in case of exception?

In exceptional cases, you can suppress this finding by using the pseudo comment "#EC MSG_FIND which has to be placed after the message statement:

  DATA(message_class) = '00'.
  MESSAGE i002(message_class). "#EC MSG_FIND

Example

Before the check:

  DATA(message_class) = '00'.
  DATA(message_id) = '002'.

  MESSAGE i002(message_class).
  MESSAGE ID message_class type 'I' NUMBER message_id.

After the check:

  MESSAGE i002(00).
  MESSAGE ID 00 type 'I' NUMBER 002.

Further Readings & Knowledge