Extended System Message Check 

Use

After each transaction, the last system message sent is logged. You can define other checks in addition to the CHEERR – Check system message check, by inserting a particular screen at the end of the screen sequence of a transaction.

Procedure

  1. Go to the CATT function editor.
  2. Go to the screen sequence of a transaction (function TCD ).
  3. Go to the last screen.
  4. Insert SAPMSCEM 0001 as last screen, if this is not already the case.
  5. The screen SAPMSCEM 0001 is automatically appended to all test cases which are newly-recorded in Release 4.6C.

     

  6. Double-click on this screen.
  7. Define a message check. You can check the message number or the combination of message class (Message ID) and message number.
    Put the cursor on the field number and delete the displayed value. Choose Check field. Enter the expected message number or a parameter that will contain the expected message number at runtime, in the following dialog box.
    To check the message class, delete the Message ID field contents and choose Check field. Enter the message class in the following dialog box.
  8. You can define other allowed messages by performing step 5 using the Other allowed messages fields.

Result

You have defined system message checks. If these system messages are sent, the test is a success, even if the transaction ended with an error (check error). If you have defined several allowed messages, the transaction must send one of them during the test for it to be a success.