Skip to end of metadata
Go to start of metadata

SAP Screen Personas


Integrate Personas in SAP Enterprise Portal



This article describes how to integrate SAP Screen Personas screens in the SAP Enterprise Portal (EP) . It covers the creation of correct connection to the backend in the EP and describes the creation and configuration of the correct iView types for both Personas on SAP GUI for HTML and Slipstream Engine (SE).


The article is structured in there sections:

  1. Setup a connection to the ABAP backend serving Personas content.
  2. Configure an iView for Personas on SAP GUI for HTML
  3. Configure an iView for Personas in Slipstream Engine (only possible with SP8)

Setup the Connection to the ABAP Backend which runs SAP Screen Personas

In many cases, this is already done, because it is a common task for an portal administrator to configure a connection to an ABAP backend, e.g. to incorporate standard transaction via SAP GUI for HTML or content based on WebDynpro for ABAP.

The following screen shot is for a connection created with the connection template "Dedicated Application Server".


Creation and Configuration of an iView for Personas on SAP GUI for HTML

Step 1: Create a Transaction iView

In Portal Content, on the folder in which you want to create the iView, open the context menu->New->iView→iView from Remote Source:

In the following screen select the system in the Seach In field, transaction name, for instance VA01, in the Search For field, and select "Tramsaction" for Application Type:

Press Go, and select you application and move it into the Selected Applications pane:

Press Upload, then finish the wizard. In the end your iView should show up in your Portal Content.

Step 2: Configure the Properties of your iView

Open your iView's properties (Context Menu->Open->Properties):

Per default the iView wizard that we used earier uses the ITS service that was maintained in the connection properties (see the first section of this article where we configured the connection). For the most part, it's acceptable to use SAP Screen Personas through the standard ITS service (sap/bc/webgui), but it's nicer to use the dedicated personas service (which is delivered as /sap/bc/persons).

So,Set “SAP GUI for HMTL (WebGui) – Alternative Path/Alternative service” properties to point to the Personas service. See below.

When I uploaded/created the iView it mapped the applied flavor to two portal properties "Additional Parameters for Starting SAP GUI” and “Application Parameters”, as "sap-personas-flavor=<flavorid>":

However, the problem is that these portal properties do not set the flavor. So, I suggest to remove these values from these properties:

If you want the backend to pick the flavor for the transaction and the user, you are done now. If you want to open the transaction with a specific flavor applied, then you have to configure the Transaction Code property according to the following format: */personas/launch<SPACE>FLAVOR=<FLAVORID>

For example: */personas/launch FLAVOR=005056BB59E71EE8819F47192750195A or:

Creation and Configuration of an iView for Personas in Slipstream Engine

This section of the article will be updated when SP8 of SAP Screen Personas 3.0 is released as it is currently not possible to embed SE in the portal.

Step 1: Create an UI5 iView

In Portal Content, scroll to Portal Applications ->, select UI5, Context Menu -> Create:

Then select your target folder under Portal Content, Context Menu -> Paste as PCD Object:

Lastly, give your new iView a name.

Step 2: Configure the Properties of your iView


Related Content

Related Search Terms:

SAP Screen Personas, SAP Enterprise Portal, Slipstream Engine, SE, Portal Integration

Related SAP Notes/KBAs





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

  • No labels