Posts Tagged ‘ABAP’

Fake Messages [ABAP]

Thursday, 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.

(more…)

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

Monday, May 17th, 2010

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

Wednesday, May 12th, 2010

What a mistake! Exception CX_SY_DYN_CALL_ILLEGAL_TYPE [SAP]

Friday, April 30th, 2010

User-Exit: EXIT_SAPLF050_008 Change Fields for FI Document [SAP]

Wednesday, April 28th, 2010

Function Module: XSI_E1EDL47 - How Delivery Tracking Data Selected [SAP]

Monday, April 26th, 2010

Warning: DS027 Program names ZX… are reserved for includes of exit function groups [SAP]

Thursday, April 22nd, 2010

Selecting Condition Record Value (VK12) for a Sales Order [SAP]

Thursday, October 15th, 2009

Adventure on SAP ALV Function Modules [SAP]

Friday, July 10th, 2009

ABAP: Call REST Services [SAP]

Thursday, March 19th, 2009