Kontakt

Ansicht
Dokumentation

PCUI_ESS_PT_LRQ_070 - Configure Output of Messages

PCUI_ESS_PT_LRQ_070 - Configure Output of Messages

TXBHW - Original Tax Base Amount in Local Currency   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.
SAP E-Book

Employees who use an Employee Self-Service application often do not have the necessary expertise to react appropriately to SAP system messages. With this in mind, this IMG activity enables you to suppress or change system messages. Consequently, the administrator takes on the task of analyzing or resolving situations in which errors occurred. To do this, the administrator uses the error log of the posting run.

In this activity, you can only change or suppress messages that come from the backend system. This is with the exception of messages displayed on the user interface that refer to an incorrect date having being entered, for example.

Options for Modifying Messages

  • You can suppress individual messages or messages of an entire message class.
  • You can suppress messages of a particular message type (for example, if you do not want information messages to be displayed). Note: You should not suppress messages of type Error or Abort because this can lead to subsequent errors, short dumps, or database inconsistencies.
  • You can change the message type of messages (change warning messages to information messages, for example).
  • You can specify alternative messages in an application area (user) and thereby determine your own message texts and message types. Note: You should not replace messages of type Error or Abort with alternative messages of type Message on Next Screen, Information,or Warning because this can lead to subsequent errors, short dumps, or database inconsistencies.
Note: The message type Message on Next Screen describes a success message (S message).

If the options in this Customizing settings are not sufficient for your requirements, you can use the MODIFY_APPLICATION_MESSAGES method of the PT_GEN_REQ Business Add-In to further refine the message modification.

Processing Table Entries

To make it easier to customize the behavior of messages, the system processes entries as follows:

  1. When a message is created, the system checks whether an entry exists for this message in the table.
  2. The system then checks the entries in which the Application Area, Message Type, and Message fields have been filled.
  3. Next, the system checks whether an entry exists for the Application Area.
  4. Only after it has done this, does the system then check whether an entry exists for the Message Type.

Example

You suppress messages for an entire application area, that is messages from this application area are not to be displayed in the Web application. To suppress these messages, you enter the name of the message class in the table and select the Suppress Message field. You leave all other fields blank.

This is with the exception of one message that you do want to be displayed. To ensure that this messages is displayed, you make entries in the Application Area, Message Type, and Message fields. You leave all other fields blank.

Result: The system only displays this message when this specific message is created. All other messages in the application area are suppressed.

Maintain the entries in the table. The following message classes can be relevant:

  • HRTIM*
  • 3H
  • 3T
  • P2
  • 54
  • 5X
  • PG
  • RP






BAL Application Log Documentation   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 4572 Date: 20240523 Time: 191206     sap01-206 ( 83 ms )