Fake Messages [ABAP]

August 5th, 2010

You can show fake messages by using “DISPLAY LIKE dtype” option of MESSAGE statement. For example you can show a S (Success) message as E (Error) message.

MESSAGE … DISPLAY LIKE dtype

When you use this addition, the icon of the message type specified in dtype is displayed instead of the associated icon. A character-type data object is expected for dtype. This data object has to contain one of the values “A”, “E”, “I”, “S” or “W” in upper-case letters.

The message short text is still displayed as a dialog window for messages that are displayed this way by default. Messages with the type “E” or “W” (except those for PBO and LOAD-OF-PROGRAM) are displayed as a dialog window if dtype contains “A” or “I”. Messages with the type “S” are always displayed in the status bar, independently of dtype. The latter also applies to messages of the type “I” for PBO and LOAD-OF-PROGRAM. Messages of the type “X” always cause a runtime error.

Read the rest of this entry »

Rule 2 - Adhere to the KISS Principle [Official ABAP Programming Guidelines]

May 17th, 2010

Don’t Cancel Release IDOC Type, Create a Successor IDOC Type [SAP]

May 14th, 2010

Failed to Load the Repository, No Panic! Just follow! [iWay]

May 13th, 2010

Blogs - May 12, 2010

May 12th, 2010

Rule 1 - Adhere to the SoC Principle [Official ABAP Programming Guidelines]

May 12th, 2010

Message E2257 - Observe the constraints for use in a logical database [SAP]

May 7th, 2010

Blogs - May 5, 2010

May 5th, 2010

Changing Printer Speed and Darkness of the Label [Zebra BAR-ONE]

May 5th, 2010

What a mistake! Exception CX_SY_DYN_CALL_ILLEGAL_TYPE [SAP]

April 30th, 2010