Configuring System Messages 

Purpose

If an SAP R/3 system with Release 4.x is integrated in the system landscape of the portal, the user is logged on again each time he or she accesses the SAP R/3 system for technical reasons. With single sign-on using logon tickets, the portal user is authenticated in the back-end system without further logons, but the SAP R/3 system displays the window with the system messages each time.

Below you can find information about how to configure the SAP R/3 system so that the system messages are only displayed once per calendar day.

No configuration steps are needed in SAPsystems with Release 6.10 or higher.

Process Flow

See also Note 301563.

You must perform the following steps to configure your system:

...

       1.      Create and activate database table TEMSGU.

       2.      Create an index for table TEMSGU (optional).

This is recommended for larger systems with a number of users as it reduces the access times to table entries.

       3.      Change and activate the report and the function modules

...

                            a.      LSM02DEF

                            b.      SM02_DELOLD_MESSAGE

                            c.      SM02_GET_UNREAD_MESSAGE

                            d.      SM02_SET_LAST_USREMSG_ID

 

Result

Once the changes have been activated, the system messages are only displayed once per day.