topic Re: Message handling in ABAP program in Application Development and Automation Discussions

Message handling in ABAP program

Former Member — Thu, 14 Feb 2008 11:30:21 GMT

How do invoke a message in ABAP program without defending the message-id in the report header?

Re: Message handling in ABAP program

Former Member — Thu, 14 Feb 2008 11:34:52 GMT

Hi Dudette,

Only system messages are issued without the inclusion of

Message-Class addition to the Report statement.

For issuing your own messages you shoud definitely

specify the message-class containing the messages you use

in that report.

<REMOVED BY MODERATOR>

Regards,

Lakshmanan

Edited by: Alvaro Tejada Galindo on Feb 14, 2008 12:30 PM

Re: Message handling in ABAP program

Lakshmant1 — Thu, 14 Feb 2008 11:37:55 GMT

Hi Chitra,

Refer program DEMO_MESSAGES on how to provide message without Message-ID in report header.

e.g. MESSAGE i888(sabapdocu)

WITH 'No exception raised in function module'

Hope this helps

Thanks

Re: Message handling in ABAP program

Former Member — Thu, 14 Feb 2008 11:38:36 GMT

HI.

check 4th one.

1.REPORT rep MESSAGE-ID sabapdocu.

...

MESSAGE i014.

2.REPORT ...

...

MESSAGE i014(sabapdocu).

3.DATA: mid TYPE sy-msgid VALUE 'SABAPDOCU',

mtype TYPE sy-msgty VALUE 'I',

num TYPE sy-msgno VALUE '014'.

MESSAGE ID mid TYPE mtype NUMBER num.

4. MESSAGE 'Message in a Method' TYPE 'I'

<REMOVED BY MODERATOR>

Jay

Edited by: Alvaro Tejada Galindo on Feb 14, 2008 12:30 PM

Re: Message handling in ABAP program

Former Member — Thu, 14 Feb 2008 11:44:05 GMT

Hi,

you can do by following way.

MESSAGE s418(ztest).

where "ztest" is message class.

Regards

Venkat

Re: Message handling in ABAP program

Former Member — Thu, 14 Feb 2008 11:47:45 GMT

MESSAGE ext TYPE mtype ... .

This variant sends a character string contained in text as a message of the message type specified in mtype. You can enter a character-type data object text, which will be used as a short text for the message. Only the first 300 characters in text are taken into account. No long text can be defined for a message of this type.

For mtype, a character-type data object is expected, which must contain the message type in capital letters. Invalid message types generate an untreatable exception.

Notes

: In this variant, the additions WITH and INTO are not allowed in message_options.

If field symbols or formal parameters of the type any or data are specified for text, these must be of character type when the statement is executed. The syntactically identical variant MESSAGE oref cannot be executed with generically typed field symbols or formal parameters.

Because the system fields sy-msgid and sy-msgno are filled unspecifically when a character string is entered, this variant should only be used on rare occasions if the content of the system fields is not required for identification of the message. Otherwise, in all cases in which messages are transferred (for example, from function modules) or logged (for example, in batch input) using these system fields, language-independent access to the message text would be lost.

Example

: Output of an exception text as an information message.

DATA: oref TYPE REF TO cx_sy_arithmetic_error,

text TYPE string.

TRY.

...

CATCH cx_sy_arithmetic_error INTO oref.

text = oref->get_text( ).

MESSAGE text TYPE 'I'.

ENDTRY.