Skip to end of metadata
Go to start of metadata

SAP Screen Personas


Logging and Tracing Tool

SAP SCREEN PERSONAS KNOWLEDGE BASE - by Tobias Queck , Former Member , Dominik Ofenloch


SAP Screen Personas SP05 comes with a logging and tracing tool. The logging tool are intended to be used by administrators to easily trace and debug SAP Screen Personas flavors and other functionality.


This article shows you how to enable the Personas Logging and Tracing tool and how you can access logs.

Enabling of the logging and tracing tool

To enable the tracing tool customizing table /PERSONAS/STTNGS needs to be maintained. To do this you can use transaction SM30. Alternatively you can also use the Personas Admin Tools transaction:

  1. Start transaction /PERSONAS/ADMIN

  2. Look up group "Additional Administrative Tasks" in the lower right corner and click on button "Change Settings"
  3. Add or change setting PERSONAS_LOG_LEVEL.

The following table shows you all available setting values:






Logger is turned off



Logs very severe error messages



Logs error messages and all above



Logs warning messages and all above



Logs all messages



Logs debug text and all messages



Logs everything that is supposed to be logged

Displaying logs

You can access the recordings using transaction /PERSONAS/TRACING.

After execution of the search the found traces will be displayed in a table. You can double click on any entry to see the complete trace message in the lower screen area.

Related Content

Related Search Terms:

SAP Screen Personas, Tracing, Logging, Debugging

Related SAP Notes/KBAs

No related notes available





Important News

This knowledge base is not solely SAP provided content - but community driven. Please also check on SMP and for SAP released information and notes on SAP Screen Personas.

Create New Article

Compare SAP Screen Personas versions

Search the KB

How to Open OSS Message

 What information is needed for creating OSS message?

  1. Make Sure you are on the latest patches and notes.
  2. Kernel Patch Level
  3. Two Types of connections to your environment: HTTP and R/3
  4. All the connections should be tested with proper credentials provided
  5. Steps to re-create the issue
  6. Attach related logs
  7. File tickets against BC_PER