Skip to end of metadata
Go to start of metadata

SAP Screen Personas

Import Templates for SAP Screen Personas

SAP SCREEN PERSONAS KNOWLEDGE BASE - by Tamas Hoznek , Regina Sheynblat , Sebastian Steinhauer

Updated in Admin Guide SP08


This article explains how to import Templates for SAP Screen Personas from a zip files. This feature is only available for customers on SAP Screen Personas 3.0 SP03 and higher.


The following sections will show how to use the import feature provided through the program /personas/template_ui. The program can be executed by either entering /n/personas/templates into the transaction code (ok code) field, or by click the Goto->Massmaintenance -> Template Maintenance menu entry in the main Personas admin transaction /personas/admin. These are standard transactions and can be executed with the SAP GUI of your choice.

Template Import

To import a Template follow these instructions:

  1. Open the admin user interface by entering /n/personas/admin into the okcode field
  2. From the menu select: Goto -> Mass Maintenance -> Template Maintenance
  3. On the resulting screen press the "Import" button
  4. In the file dialog select a template of your choice to be imported.

Where to find templates:

Templates are published in the SAP Screen Personas Flavor Gallery.
For your convenience some Templates for SAP Screen Personas are available below.

Please note that these templates are subject to the EULA (also included in the ZIP files).

Related Content

Related Search Terms:

SAP Screen Personas, Templates for SAP Screen Personas, Flavor Gallery



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