topic Re: error message ( urgent) in Application Development and Automation Discussions

error message ( urgent)

Former Member — Tue, 20 Nov 2007 05:04:17 GMT

Hi all,

I want to give error message if the user enter incorrect value wat do i need to do

Thanx,

Amruta.

Re: error message ( urgent)

Former Member — Tue, 20 Nov 2007 05:06:24 GMT

MESSAGE

Syntax

MESSAGE { msg | txt } [message_options].

Effect

This statement interrupts the program flow and either displays the short text of a message specified in msg in the logon language of the current user, or any text from txt as a message. The exact behavior of the MESSAGE statement - that is, how the text is displayed and how the program flow is continued after the MESSAGE statement - is context-dependent and is determined by a message type specified in msg or txt. This behavior can be changed using the message_options additions and the placeholders can be replaced in messages.

System fields/>

Name Relevance

sy-msgid Contains the message-class after sending a message, and the value "00" after sending any text.

sy-msgno Contains the message number after sending a message, and the value "001" after sending any text.

sy-msgty Contains the identifier of the message type with which the message resp. the text was sent.

sy-msgv1 to sy-msgv4 Contain the content of the data objects specified after the addition WITH after sending a message. After sending any text, they contain the first 200 characters of the data object text.

Notes

Messages are one way of interacting with a user. Except for messages of the type "X", the MESSAGE statement should be use exclusively in the presentation logic layer and never in the application logic layer.

Setting the text environment by means of the SET LOCALE statement has no effect on the language in which the message is displayed.

MESSAGE - msg

Syntax

...

| { tn(id) }

| { ID mid TYPE mtype NUMBER num }

| { oref TYPE mtype } ... .

Alternatives:

1. ... tn ...

2. ... tn(id) ...

3. ... ID mid TYPE mtype NUMBER num ...

4. ... oref TYPE mtype ...

Effect

In msg a message is specified from the database table T100 either via direct specification of id and n resp. via the content of the data objects mid and num for the message class and the message number. Or, an object reference variable oref is specified, whose dynamic type implements the interface IF_T100_MESSAGE. You have to specify one of the possible message types "A", "E", "I", "S", "W" or "X", either by direct specification of t, or as content of the data object mtype, whereby the behavior of the message is controlled.

If the specified message is not found for the logon language, then the specified message type, the message class and the message number are used as short text in capital letters separated by a colon ":".

The system fields of the statement MESSAGE are always supplied with the specified values.

Alternative 1

... tn ...

Effect

With t and n you specify the one-digit message type and the three-digit message number directly in a row (static short form). The message class must be specified with the addition MESSAGE-ID at the statement that introduces the program.

Example

Display of the short text of the message with the number 014 from the message class SABAPDOCU as Information message.

REPORT rep MESSAGE-ID sabapdocu.

...

MESSAGE i014.

Alternative 2

... tn(id) ...

Effect

For t and n the same applies as for the static short form. In the static long form, the message class is specified directly in brackets through id.

Notes

The explicit specification of the message class overrides the addition MESSAGE-ID of the statement that introduces the program.

The specification of the message class in brackets does not signify that the content of id is used. In fact, the message class is used that has the name that was specified directly with id.

Example

As example for alternative 1, with explicit specification of the message class.

REPORT ...

...

MESSAGE i014(sabapdocu).

Alternative 3

... ID mid TYPE mtype NUMBER num ...

Effect

The message class, the message type and the message number are specified as content of the data objects mid, mtype and num (dynamic form). For mid and mtype, character-type data objects are expected that must contain the message class resp. the message type in capital letters. Invalid message types create an uncatchable exception. For num, a data object of the type n and the length 3 is expected.

Note

The explicit specification of the message class overrides the addition MESSAGE-ID of the statement that introduces the program.

Example

As example for alternative 2, with dynamic specification of the message and the message type.

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.

Alternative 4

... oref TYPE mtype ...

Effect

For oref, you can specify an object reference variable which, at execution of the statement MESSAGE points at an object, whose class implements the system-interface IF_T100_MESSAGE ,which in turn contains the component-interface IF_MESSAGE. For mtype, a character-type data object is expected which must contain the message type in capital letters.

The statement MESSAGE analyses the components of the structured attribute T100KEY of the interface IF_T100_MESSAGE in the referenced object. The message class is taken from the component MSGID, the message number from the component MSGNO. If the components ATTR1 to ATTR4 contain the names of other attributes of the object, the placeholder "&1" to "&4" und "&" of the short text resp. "&V1&" to "&V4&" of the long text of the message are replaced by the content of these attributes according to the rules of usage given by the additions WITH in message_options. If one of these components does not contain an attribute name, the character "&" is added to the content at the beginning and end, thus replacing the placeholder.

Notes

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

If field symbols or formal parameters of the generic type any or data are specified for oref, then the syntactically identical variant MESSAGE text is used.

This variant is mainly designated to be used with exception objects. If an exception class implements the interface IF_T100_MESSAGE, then the components of the structure T100KEY are automatically filled when an exception is raised (according to the respective definition of the exception text).

Due to compatibility reasons, this variant can still be used for classes that only implement the interface IF_MESSAGE. In this case, the interface methods GET_TEXT and GET_LONGTEXT arecalled automatically in the referenced object and their return value is used as short text resp. long text of the message. In this case, the system fields sy-msgid and sy-msgno are not specifically filled. The root class of all exception classes, CX_ROOT, implements the interface IF_MESSAGE. In exception classes that do not implement the interface IF_T100_MESSAGE, the interface methods GET_TEXT and GET_LONGTEXT get the exception texts of exception objects stored in OTR (Online Text Repository), which then can be issued by using the variant of the MESSAGE-statement as message.

Example

In a class c1, the interface IF_T100_MESSAGE is implemented and its attribute T100KEY supplied with values. The statement MESSAGE displays the respective statement, in which a placeholder "&" is replaced with the content of the attribute text.

CLASS c1 DEFINITION.

PUBLIC SECTION.

INTERFACES if_t100_message.

DATA text TYPE c LENGTH 10 VALUE 'Hello!'.

METHODS constructor.

ENDCLASS.

CLASS c1 IMPLEMENTATION.

METHOD constructor.

if_message~get_text( ).

ENDMETHOD.

METHOD if_message~get_text.

if_t100_message~t100key-msgid = 'SABAPDOCU'.

if_t100_message~t100key-msgno = '888'.

if_t100_message~t100key-attr1 = 'TEXT'.

ENDMETHOD.

METHOD if_message~get_longtext.

ENDMETHOD.

ENDCLASS.

DATA oref TYPE REF TO c1.

START-OF-SELECTION.

CREATE OBJECT oref.

MESSAGE oref TYPE 'I'.

MESSAGE - text

Syntax

... text TYPE mtype ... .

Effect

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.

MESSAGE - message_options

Syntax

... { {[DISPLAY LIKE dtype] [RAISING exception]}

| [INTO text] }

[WITH dobj1 ... dobj4].

Extras:

1. ... DISPLAY LIKE dtype

2. ... RAISING exception

3. ... INTO text

4. ... WITH dobj1 ... dobj4

Effect

These additions change the type of display, raise a non-class-based exception in function modules or methods, assign the text of the message to a data object and replace the placeholders in short- and long-texts of messages.

Addition 1

... DISPLAY LIKE dtype

Effect

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.

Note

The usage of this addition does not influence the behavior determined by the message type, but only the type of display.

Addition 2

... RAISING exception

Effect

With this addition, the statement MESSAGE raises either a non-class-based exception exception, or sends a message. The addition only makes sense during the processing of methods and function modules, in which the non-class-based exception exception is defined. Furthermore, the addition must not be used in the same processing block as the statement RAISE EXCEPTION for raising class-based exceptions.

If the MESSAGE-statement is processed with the addition RAISING during processing of a method or a function module whose caller assigns a return value to the exception exception with the addition EXCEPTIONS of the statement CALL, it has the same effect as the statement RAISE. If no return value is assigned to the exception exception , then the addition RAISING is ignored and the message is processed according to its message type.

The system fields of the statement MESSAGE are populated in both cases and are available in the calling program after handling an exception raised with MESSAGE ...RAISING. This is especially true, when a function module was called through Remote Function Call (RFC).

Note

You can assign a return value to messages that are sent in function modules without the addition RAISING via the predefined exception error_message.

Example

At the first call of the method, an information message is sent, at the second call an exception is raised instead and is handled after the call via analysis of sy-subrc.

CLASS c1 DEFINITION.

PUBLIC SECTION.

CLASS-METHODS m1 EXCEPTIONS exc1.

ENDCLASS.

CLASS c1 IMPLEMENTATION.

METHOD m1.

MESSAGE 'Message in a Method' TYPE 'I' RAISING exc1.

ENDMETHOD.

ENDCLASS.

...

c1=>m1( ).

c1=>m1( EXCEPTIONS exc1 = 4 ).

IF sy-subrc = 4.

...

ENDIF.

Addition 3

... INTO text

Effect

With this addition, you assign the short text of the message to the variable text. The message type does not matter. The program flow is not interrupted and there is no message processing taking place. For text, a character-type data object is expected.

The addition INTO cannot be specified at the output of a user-defined text.

Example

The short text of a message sent in a function module is stored in the data object mtext when handling the exception error_message with help of the respective system fields.

DATA mtext TYPE string.

CALL FUNCTION ... EXCEPTIONS error_message = 4.

IF sy-subrc = 4.

MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno

INTO mtext

WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.

ENDIF.

Addition 4

... WITH dobj1 ... dobj4

Effect

This addition replaces the placeholders "&1" to "&4" and "&" of the short text resp. "&V1&" to "&V4&" of the long text of the message with the first 50 characters of the content of the data objects dobj1, ..., dobj4. You can specify up to four character-type data objects. The position of a data object determines which placeholder will be replaced. The content of the first data object replaces the placeholders "&1", the first placeholder "&" and "&V1&", the second replaces "&2", the second "&" and "&V2&" etc. Furthermore, the content of the data objects dobj1, ..., dobj4 is assigned in sequence to the system fields sy-msgv1 to sy-msgv4.

If you specify fewer data objects than placeholders, then surplus placeholders are not displayed in the short text and the associated system fields sy-msgv1 to sy-msgv4 are initialized. If a specified data object cannot be assigned to a placeholder, it is ignored.

The addition WITH cannot be specified at the output of an user-defined text, or, resp., an object reference oref.

Note

If a short text contains placeholders of both forms "&i" and "&", then the content of a data object can replace both placeholders. The data object at the position i not only replaces "&i" but also the i-th placeholder at position "&". We recommend that you use only one of the two forms for placeholders in a short text. If a short text is to be translated into other languages, only the numbered placeholder "&i" is used, as the structure of the sentence may change.

Example

If the short text of the specified message in the table T100 contains the value "& & & &" , then the text "This is not America" is put out as information message. If the short text was defined as "&4 &1 &3 &2" , then the output is "America This not is".

MESSAGE i010 WITH 'This' 'is' 'not' 'America'.

Re: error message ( urgent)

naimesh_patel — Tue, 20 Nov 2007 05:07:03 GMT

You can do like this in report

parameters: p_num type i.

at selection-screen on p_num
if p_num > 10,.
 message e398(00) with 'you entered wrong parameter.
endif.

Regards,

Naimesh Patel

Re: error message ( urgent)

Former Member — Tue, 20 Nov 2007 05:08:00 GMT

Hi amruta,

If it is a selection screen of a report, the you can write the code as follows:

AT SELECTION-SCREEN ON FIELD1 (e.g. p_matnr. Here p_matnr is a parameter).

Write ur logic for checking the value entered by user.

If Value is incorrect.

MESSAGE E000(0K) WITH <Your error text>.

endif.

Hope it helps.

Regards,

Himanshu

Re: error message ( urgent)

Former Member — Tue, 20 Nov 2007 05:09:51 GMT

you have to give a message like this

MESSAGE E999 WITH TEXT-005.

see this below program you can understand very easily , bold ones are important to use messages in report

REPORT ZNNR_REPORT NO STANDARD PAGE HEADING MESSAGE-ID ZNNR LINE-SIZE 100 LINE-COUNT 65(4).

******DATA DECLARATIONS**********

DATA : BEGIN OF IT_PLANT OCCURS 0,

MATNR LIKE MARA-MATNR,

WERKS LIKE MARC-WERKS,

PSTAT LIKE MARC-PSTAT,

EKGRP LIKE MARC-EKGRP,

END OF IT_PLANT.

DATA : BEGIN OF IT_PONO OCCURS 0,

EBELN LIKE EKKO-EBELN,

EBELP LIKE EKPO-EBELP,

MATNR LIKE EKPO-MATNR,

WERKS LIKE EKPO-WERKS,

LGORT LIKE EKPO-LGORT,

END OF IT_PONO.

TABLES EKKO.

********END OF DATA DECLARATIONS*********

********SELECTION SCREEN DESIGN ***********

SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-001.

PARAMETER : P_WERKS LIKE MARC-WERKS MODIF ID S1.

SELECT-OPTIONS : S_EBELN FOR EKKO-EBELN NO INTERVALS MODIF ID S2.

SELECTION-SCREEN END OF BLOCK B1.

SELECTION-SCREEN BEGIN OF BLOCK B2 WITH FRAME TITLE TEXT-004.

SELECTION-SCREEN BEGIN OF LINE.

PARAMETERS : R1 RADIOBUTTON GROUP G1 DEFAULT 'X'.

SELECTION-SCREEN COMMENT 5(20) TEXT-002 FOR FIELD R1.

SELECTION-SCREEN END OF LINE.

SELECTION-SCREEN BEGIN OF LINE.

PARAMETERS : R2 RADIOBUTTON GROUP G1.

SELECTION-SCREEN COMMENT 5(20) TEXT-003 FOR FIELD R2.

SELECTION-SCREEN END OF LINE.

SELECTION-SCREEN END OF BLOCK B2.

******END OF SELECTION SCREEN DESIGN****************

*********INITIALIZATION OF SELECTION SCREEN ELEMENTS.*****

INITIALIZATION.

P_WERKS = '1000'.

S_EBELN-LOW = '4500016926'.

S_EBELN-OPTION = 'EQ'.

S_EBELN-SIGN = 'I'.

APPEND S_EBELN.

CLEAR S_EBELN.

************END OF INITIALIZATION***********************

***********SCREEN MODIFICATIONS*******************

AT SELECTION-SCREEN OUTPUT.

LOOP AT SCREEN.

IF R1 EQ 'X' AND SCREEN-GROUP1 EQ 'S2'.

SCREEN-INPUT = 0.

MODIFY SCREEN.

ENDIF.

IF R2 EQ 'X' AND SCREEN-GROUP1 EQ 'S1'.

SCREEN-INPUT = 0.

MODIFY SCREEN.

ENDIF.

ENDLOOP.

********END OF SCREEN MODIFICATIONS*****************

***************SCREEN VALIDATIONS *****************

at selection-screen.

SELECT SINGLE *

FROM EKKO

INTO EKKO

WHERE EBELN IN S_EBELN.

IF SY-SUBRC <> 0.

SET CURSOR FIELD 'S_EBELN-LOW'.

MESSAGE E999 WITH TEXT-005.

ENDIF.

********end of screen validation*****************

START-OF-SELECTION.

*set pf-status '100'.

IF R1 EQ 'X'.

SELECT MATNR

WERKS

PSTAT

EKGRP

FROM MARC

INTO TABLE IT_PLANT

WHERE WERKS = P_WERKS.

LOOP AT IT_PLANT.

WRITE : SY-VLINE , 2 IT_PLANT-MATNR COLOR COL_KEY,

21 SY-VLINE , 22 IT_PLANT-WERKS COLOR COL_KEY,

27 SY-VLINE ,28 IT_PLANT-PSTAT COLOR COL_NORMAL,

43 SY-VLINE ,44 IT_PLANT-EKGRP COLOR COL_NORMAL.

ENDLOOP.

ENDIF.

IF R2 EQ 'X'.

SELECT EBELN EBELP MATNR WERKS LGORT

FROM EKPO

INTO TABLE IT_PONO

WHERE EBELN IN S_EBELN.

LOOP AT IT_PONO.

WRITE : SY-VLINE , 2 IT_PONO-EBELN COLOR COL_KEY,

12 SY-VLINE , 13 IT_PONO-EBELP COLOR COL_KEY,

18 SY-VLINE , 19 IT_PONO-MATNR COLOR COL_NORMAL,

37 SY-VLINE , 38 IT_PONO-WERKS COLOR COL_NORMAL,

44 SY-VLINE , 45 IT_PONO-LGORT COLOR COL_NORMAL, 49 SY-VLINE..

ENDLOOP.

ENDIF.

TOP-OF-PAGE.

IF R1 EQ 'X'.

*ULINE AT /1(48).

WRITE : SY-VLINE ,2 'MATERIAL NUMBER',

21 SY-VLINE , 22 'PLANT',

27 SY-VLINE , 28 'STATUS',

43 SY-VLINE , 44 'GRUP', 48 SY-VLINE.

ULINE AT /1(48).

ENDIF.

IF R2 EQ 'X'.

WRITE : SY-VLINE , 2 'PO NUMBER',

12 SY-VLINE, 13 'ITEM',

18 SY-VLINE,19 'MATERIAL NUMBER',

37 SY-VLINE, 38 'PLANT',

44 SY-VLINE, 45 'GRUP',

49 SY-VLINE.

ULINE AT /1(50).

ENDIF.

END-OF-PAGE.

ULINE AT /1(50).

WRITE :/10 'PAGE NUMBER', SY-PAGNO.

Reward if usefull