Message---- End Message in Ecatt - -SAPGUI

Question

Hi Everyone:
    Can some one give me a detailed information about Message and End Message commands in Ecatt-SAPGUI.
    How can they be used?
    What are the main advantages etc.
Thanks,
Rajesh.S

Answer 1

Hello Rajesh
You can basically use the Message/End Message statement to surround SAPGUI or TCD commands to capture messages from the GUI as raised by the MESSAGE ABAP Statement in your programs. The captured messages can then be analysed using a set of specified rules to determine whether the program is functioning as expected or not.
For example, the following eCATT segment was used to capture a message from the program that certain data was successfully generated and saved.
MESSAGE ( OPTIONAL_COMMANDS ).
  SAPGUI ( CONFIRM_SAVE ).
  SAPGUI ( CONFIRM_GENERATE_SUCCESS ).
  SAPGUI ( SAVE_SUCC_MSG ).
ENDMESSAGE ( E_OPTIONAL_COMMANDS ).
The command interface used with the Message/End Message statement, in this case the command interface is called OPTIONAL_COMMANDS, will determine how the eCATT script will respond to the messages received from the SAPGUI commands.
The command interface has a specific parameter called MODE which will determine whether a specific message is allowed, is expected, is considered an error or is obligatory. You can also specify whether the script should exit if the specified condition is not met using the EXIT flag in the command interface. Also note that the command interface used with the Message/End Message statement can contain a number of these kind of rules as to establish a set of rules used to govern the expected behaviour in terms of the messages being raised by the program.
In your recorded SAPGUI or TCD statements specifically look for the Message variant in the recording to see what messages should be raised by the program in terms of the message classes and message numbers since you are going to need these to fully specify your messages to the Message/End Message statement. The following is an example of the message recorded in the CONFIRM_GENERATE_SUCCESS command interface from the above code except that can be used to determine the exact information to use in drawing up the OPTIONAL_COMMANDS command interface for the Message/End Message statement:
Message
  Type  I
  Text  Report /EPIUSE/VM3REP_22000003_NEW was generated  successfully.
  Id    /EPIUSE/VM3MESS
  Number 225
  Parameter1 /EPIUSE/VM3REP_22000003_NEW
  Parameter2
  Parameter3
  Parameter4
  AsPopup  X
Here your expected message is an information message (Type I), the message class would be /EPIUSE/VM3MESS as recorded in the Id field and the message number would be 225, do take note of these fields since you are going to need them to draw up the command interface for the Message/End Message statement. The parameters 1-4 might also be used in your Message/End Message statement conditions to really narrow down your expected messages. Well, this is a lot of information for you, I hope it helps...
Stay well
Ettienne Hugo