You are on page 1of 57

SAP Screen Personas Configuration Guide Addendum

SAP Screen Personas Configuration Guide - Addendum


v.2.0
2014-07-29

SAP Screen Personas Configuration Guide Addendum


1/2015

SAP Screen Personas Configuration Guide Addendum

Copyright
Copyright 2013 SAP AG. All rights reserved.
SAP Library document classification: PUBLIC

No part of this publication may be reproduced or transmitted in any form or for any purpose
without the express permission of SAP AG. The information contained herein may be changed
without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software
components of other software vendors. National product specifications may vary.
These materials are provided by SAP AG and its affiliated companies (SAP Group) for
informational purposes only, without representation or warranty of any kind, and SAP Group
shall not be liable for errors or omissions with respect to the materials. The only warranties for
SAP Group products and services are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein should be construed as
constituting an additional warranty.
SAP and other SAP products and services mentioned herein as well as their respective logos are
trademarks or registered trademarks of SAP AG in Germany and other countries.
Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for
additional trademark information and notices.

SAP Screen Personas Configuration Guide Addendum


1/2015

SAP Screen Personas Configuration Guide Addendum

Icons in Body Text


Icon

Meaning
Caution
Example
Note
Recommendation
Syntax

Additional icons are used in SAP Library documentation to help you identify different types of
information at a glance. For more information, see Help on Help General Information Classes and
Information Classes for Business Information Warehouse on the first page of any version of SAP Library.

Typographic Conventions
Type Style

Description

Example text

Words or characters quoted from the screen. These include field names, screen titles,
pushbuttons labels, menu names, menu paths, and menu options.
Cross-references to other documentation.

Example text

Emphasized words or phrases in body text, graphic titles, and table titles.

EXAMPLE TEXT

Technical names of system objects. These include report names, program names,
transaction codes, table names, and key concepts of a programming language when
they are surrounded by body text, for example, SELECT and INCLUDE.

Example text

Output on the screen. This includes file and directory names and their paths, messages,
names of variables and parameters, source text, and names of installation, upgrade
and database tools.

Example text

Exact user entry. These are words or characters that you enter in the system exactly as
they appear in the documentation.

<Example text>

Variable user entry. Angle brackets indicate that you replace these words and
characters with appropriate entries to make entries in the system.

EXAMPLE TEXT

Keys on the keyboard, for example, F2 or ENTER.

SAP Screen Personas Configuration Guide Addendum


1/2015

SAP Screen Personas Configuration Guide Addendum

Contents
1

About This Document ............................................................................................................................... 6


1.1

Purpose and Scope............................................................................................................................ 6

1.1.1

Prerequisites ............................................................................................................................. 6

1.1.2

SAP Screen Personas Features .................................................................................................. 6

1.1.3

Constraints ................................................................................................................................ 6

1.2

Target Audience ................................................................................................................................ 6

1.3

Glossary ............................................................................................................................................. 7

1.4

Related Information .......................................................................................................................... 7

1.4.1

Further Useful Links .................................................................................................................. 8

1.4.2

Related Master Guides.............................................................................................................. 8

1.4.3

Important SAP Notes................................................................................................................. 9

1.4.4

SAP Screen Personas Documentation Guide ..........................................................................10

1.4.5

Useful Links .............................................................................................................................11

Configuration ..........................................................................................................................................11
2.1

Setup Silverlight Cross Domain .......................................................................................................11

2.1.1

2.2

Setup URL Handler ..........................................................................................................................15

2.3

Activate Services in SICF..................................................................................................................20

2.3.1

Procedure: Activate.................................................................................................................20

2.3.2

Procedure:Test ........................................................................................................................20

2.3.3

Result ......................................................................................................................................21

SPRO Transaction ....................................................................................................................................22


3.1

Maintain Controls for Control Specific Settings ..............................................................................22

3.2

Maintain Screen ID Overwrite Logic ...............................................................................................23

3.3

Maintain Personas Global Settings .................................................................................................24

3.4

Maintain Whitelist URLs..................................................................................................................25

3.5

Maintain Roles ................................................................................................................................26

3.5.1
3.6

Role Creation using PFCG ........................................................................................................29

Maintain Systems ............................................................................................................................31

3.6.1
4

Procedure ................................................................................................................................11

RFC Destination .......................................................................................................................34

Assign Admin Authorizations ..................................................................................................................36

5 Get URL to Access SAP Screen Personas from the Installed System ......................................................37
SAP Screen Personas Configuration Guide Addendum
1/2015

SAP Screen Personas Configuration Guide Addendum


6 Appendix .................................................................................................................................................38

6.1

Important Programs, Tables and Key Transactions ........................................................................38

6.1

Screen ID vs. Control ID...................................................................................................................40

6.2

Admin Transaction ..........................................................................................................................42

Troubleshooting ......................................................................................................................................43
7.1

How to Debug and open a OSS Message ........................................................................................49

Configuration Checklist ...........................................................................................................................51

Notes .......................................................................................................................................................57

SAP Screen Personas Configuration Guide Addendum


1/2015

SAP Screen Personas Configuration Guide Addendum

About This Document

1.1 Purpose and Scope


The SAP Screen Personas Configuration Guide-Addendum provides additional information on how
to configure the SAP Screen Personas. Please start with the SAP Screen Personas Configuration
Guide that is located at https://websmp106.sap-ag.de/instguides prior to consulting the
addendum.
1.1.1

Prerequisites

SAP Kernel with release 721 or release 740 or higher installation basis

SAP NetWeaver 7.0 or enhancement packages of 7.0

SAP Basis (SAP_BASIS)

Install the latest version of Silverlight version 5.0 UI technology (browser plug-in) from
Microsoft in the client machines to render rich internet content.
Please see SAP Screen Personas Configuration Guide (https://websmp106.sapag.de/instguides) for a full list of pre-requisites.

1.1.2

SAP Screen Personas Features

Render and personalize SAP Web Dynpro screens in a web browser

Deliver screen modifications in a fast and cost-effective way, without any programming

Align user interfaces to business user needs and personal work styles

Reduce screen clutter for business users, allowing them to access only the data they need to
transact business

Add extra information to screens through labels, tooltips, and sticky notes

Add images, web content, or shortcut buttons that start transactions from the screen

1.1.3 Constraints
This component supports solutions using SAP GUI screens and no other screens.

1.2 Target Audience


This document is intended for the following target audiences:

Consultants

Partners

Customers

System Administrators

Support Specialists

SAP Screen Personas Configuration Guide Addendum


1/2015

SAP Screen Personas Configuration Guide Addendum

1.3

Glossary

Term
SAP application
Business
Scenario

Component

Flavor

User
Admin User

Definition
An SAP software solution that serves a specific business area, for example, ERP,
CRM, PLM, SRM, SCM
From a microeconomic perspective, a business scenario is a cycle that consists of
several interconnected logical processes in time. Typically, a business scenario
includes several company departments and involves other business partners.
From a technical point of view, a business scenario needs at least one SAP
application (SAP ERP, SAP SCM, or others) for each cycle and possibly other
third-party systems.
A business scenario is a unit that can be implemented separately and reflects the
customers prospective course of business.
The smallest individual unit considered within the Solution Development
Lifecycle.
Components are separately produced, delivered, installed and maintained.
Flavor in SAP Screen Personas identifies a specific personalization for a particular
SAP transaction. So a Personas Flavor is always linked to a specific SAP transaction
(example VA01). On the other hand, one particular SAP transaction can have
infinite number of flavors.
Business user who uses any SAP transaction with Personas personalization.
A user who does and supports configuration and other system activities to
support business users.

1.4 Related Information


For more information about planning topics not covered in this guide, see the following content on
SAP Service Marketplace:
Content

Location on SAP Service Marketplace

Latest versions of Configuration


Documentation and Master Guide

http://service.sap.com/instguides
Focused Business Solutions
SAP Screen Personas
SAP Screen Personas 2.0
http://help.sap.com/personas

Application help for SAP Screen


Personas
SAP Service Market Place
(SAP Screen Personas Installation and
Upgrades)
Sizing, calculation of hardware
requirements - such as CPU, disk and
memory resource - with the Quick
Sizer tool
Released platforms and technologyrelated topics such as maintenance
strategies and language support
SAP Screen Personas Configuration Guide Addendum
1/2015

http://service.sap.com/

http://service.sap.com/quicksizer

http://service.sap.com/platforms
To access the Platform Availability Matrix directly, enter
http://service.sap.com/pam

SAP Screen Personas Configuration Guide Addendum


Network security
High Availability
Performance
Information about Support Package
Stacks, latest software versions and
patch level requirements
Information about Unicode technology

http://service.sap.com/securityguide
http://scn.sap.com/docs/DOC-7848
http://service.sap.com/performance
http://service.sap.com/sp-stacks

http://scn.sap.com/community/internationalization-andunicode

1.4.1
Further Useful Links
The following table lists further useful links on SAP Service Marketplace:
Content
Information about creating error messages
SAP Notes search
SAP Software Distribution Center (software
download and ordering of software)
SAP Online Knowledge Products (OKPs) rolespecific Learning Maps

1.4.2

Location on SAP Service Marketplace


http://service.sap.com/message
http://service.sap.com/notes
http://service.sap.com/swdc
http://service.sap.com/rkt

Related Master Guides

This Master Guide is based on Master Guides for cross-industry applications. You can find more
information about the relevant applications in the following documents:
Title
Master Guide - SAP ERP 6.0

SAP NetWeaver

SAP Screen Personas Configuration Guide Addendum


1/2015

Location
http://service.sap.com/instguides
SAP Business Suite Applications
SAP ERP
SAP ERP 6.0
Planning
http://service.sap.com/instguides
SAP NetWeaver
SAP NetWeaver 7.4
Planning

SAP Screen Personas Configuration Guide Addendum


1.4.3

Important SAP Notes

Latest Notes that are released can be found on this SCN Blog:
http://scn.sap.com/community/gui/blog/2013/08/28/sap-screen-personas--how-to-configure-thesystem-troubleshooting-faq

SAP Note Number


1776739

1848339

1885334

1869640

Title
Installation Note for SAP
Screen Personas 2.0

Description
The note contains information about planning the
installation of upgrades of the ABAP add on PERSOS.
https://service.sap.com/sap/support/notes/1776739
Installation and Upgrade note This note contains information on the steps for
for SAP Screen Personas
installing and getting started for both new and
(Silverlight)
existing customers.
https://service.sap.com/sap/support/notes/1848339
Feature List for Silverlight
Feature list for SAP Screen Personas Release 2.0
Silverlight
https://service.sap.com/sap/support/notes/1885334
Client copy of Personas
After Personas installation, all the SAP delivered
delivered customizing
customizing is present in client 000.
https://service.sap.com/sap/support/notes/1869640

SAP Screen Personas Configuration Guide Addendum


1/2015

SAP Screen Personas Configuration Guide Addendum

1.4.4

SAP Screen Personas Documentation Guide

The following documentation will allow you to obtain the most value from your investment in
SAP Screen Personas.
Name
Configuration
Document
2.0_SP2

Location
https://websmp106.sa
p-ag.de/instguides

Audience
SAP basis
team

https://websmp106.sa
p-ag.de/instguides

SAP Screen
Personas Users
Guide

Purpose
This document provides configuration
information for the Silverlight and HTML
components of SAP Screen Personas 2.0 and
includes additional information of the
Support Pack SP02.
It also describes all activities necessary for
the implementation and configuration of
SAP Screen Personas.
This Master Guide is the central starting
point for the technical implementation of
the SAP Screen Personas solution. You can
find cross-scenario implementation
information as well as scenario-specific
information in this guide.
The user guide is a central starting point for
Personas. The documenting is regularly
updated with new information.

SAP Screen
Personas
Optimization
Guide

The performance optimization guide


describes the best practices that are
relevant to Personas. The document is
regularly updated with new information.

http://scn.sap.com/doc
s/DOC-54574
Under: Technical
Documentation

SAP Screen
Personas
Configuration
Guide
Addendum

The addendum to the Configuration guide


but with more details and screen shots. This
document is regularly updated with new
information.

http://scn.sap.com/doc
s/DOC-54574
Under: Technical
Documentation

SAP Screen
Personas
administrators
, enterprise
application
team
Enterprise
application
team, key
users, screen
designers,
business
analysts
Enterprise
application
team, key
users, screen
designers,
application
developers
Enterprise
application
team, key
users, screen
designers,
application
developers

Master Guide
2.0_SP02

SAP Screen Personas Configuration Guide Addendum


1/2015

http://scn.sap.com/doc
s/DOC-54574
Under: Technical
Documentation

SAP Screen Personas Configuration Guide Addendum

1.4.5

Useful Links

Name

Purpose

Location

SAP Personas Application


Help

High level help that explains Personas


Initialization, Flavors and Administration
Transaction.

SAP Screen Persons


Getting Started on SCN

A compilation of links that has demo


videos, SAP Screen Personas Basic,
Scripting and Technical Documentation.
Outlines the Truth and Myth of SAP
Screen Personas

http://help.sap.com/saphelp_persona
s200_silverlight/helpdata/en/33/30f
15101d9445ee10000000a423f68/fra
meset.htm
http://scn.sap.com/docs/DOC-54574

Myth vs. Truth


Documentation

Fiori Design for SAP


Screen Personas

How to make personas look like Fiori

http://www.sap.com/bin/sapcom/e
n_us/downloadasset.2014-04-apr29-17.sap-screen-personas-mythsversus-truth-about-usability-andthe-user-experiencepdf.bypassReg.html
http://experience.sap.com/fioriguidelines/#FioriDesign

2 Configuration
Once the SAP Screen Personas is installed, the following procedures need to be competed in order to
be able perform the administration tasks.
Please make sure you have all the need pre-requisites including the SAP Kernel 7.21.

Setup Silverlight Cross Domain


Activate Services in SICF
Setup URL Handler
Test RestGUI Services

2.1 Setup Silverlight Cross Domain


2.1.1

Procedure

Transaction: RZ10
1. Create the clientaccesspolicy.xml and crossdomain.xml
2. Locate key icm/HTTP/file_access_<n> in your system profile.

SAP Screen Personas Configuration Guide Addendum


1/2015

SAP Screen Personas Configuration Guide Addendum


3. Add following line into profile: icm/HTTP/file_access_0
=PREFIX=/sap/public/icmandir/,DOCROOT=$(DIR_ICMAN_ROOT),ARCHIVE=$(DIR_EXECUTABL
E)/ITS.SAR,CACHECTRL=+28800
4. Add following lines into profile:
1. icm/HTTP/file_access_1 = PREFIX=/clientaccesspolicy.xml,DOCROOT=<absolute
path to>\clientaccesspolicy.xml,CACHECTRL=0
2. icm/HTTP/file_access_2 = PREFIX=/crossdomain.xml, DOCROOT=<absolute path
to>\crossdomain.xml,CACHECTRL=0
5. Check the clientaccesspolicy.xml and crossdomain.xml
1. http://<hostname>:<port> or https://<hostname>:<port>

Ex: http://nvpal774.pal.sap.corp:8074/clientaccesspolicy.xml

The files with example content are described here:


clientaccesspolicy.xml

<access-policy>
<cross-domain-access>
<policy>
<allow-from http-methods="*" http-request-headers="*">
<domain uri="http://*"/>
<domain uri="https://*"/>
</allow-from>
<!--<allow-from http-methods="*">
<domain uri="http://*"/>
<domain uri="https://*"/>
</allow-from>-->

SAP Screen Personas Configuration Guide Addendum


1/2015

SAP Screen Personas Configuration Guide Addendum


<grant-to>
<resource path="/" include-subpaths="true"/> <!-- test -->
</grant-to>
</policy>
</cross-domain-access>

crossdomain.xml

</access-policy>
<?xml version="1.0"?>
<!DOCTYPE cross-domain-policy SYSTEM
"http://www.adobe.com/xml/dtds/cross-domain-policy.dtd">
<cross-domain-policy>
<site-control permitted-cross-domain-policies="all"/>
<allow-access-from domain="*" secure="false"/>
<allow-http-request-headers-from domain="*" headers="*"
secure="false"/>
</cross-domain-policy>

SAP Screen Personas Configuration Guide Addendum


1/2015

SAP Screen Personas Configuration Guide Addendum

Results:

SAP Screen Personas Configuration Guide Addendum


1/2015

SAP Screen Personas Configuration Guide Addendum

2.2 Setup URL Handler


2.2.1.1 Procedure
Transaction: SICF
In the SICF transaction, check for the availability of the restgui service in the path /default_host
SAP and activate it. To activate a service, refer to the Activate Services in SICF.

If the service is not available, configure restgui service by following the steps given below:

Create a new service.

Start SICF transaction.


This needs System Administrator rights.
1. Execute F8 and navigate to default_host sap bc gui sap its webgui
service.
2. Right-click the WebGUI service.
3. Choose Copy.
4. Navigate to default_host sap and choose Paste.
5. Specify new package or choose the Local Object button.
6. Rename the newly created service to restgui.
Depending on the patch level you are using, there is a limitation in SICF transaction UI. An
already created service is not activated yet, but after copying Activate Service, the action is
disabled in popup menu. As a work around, deactivate service first, than activate it again.
1. Configure RestGUI service.
SAP Screen Personas Configuration Guide Addendum
1/2015

SAP Screen Personas Configuration Guide Addendum


2. Double-click the RestGUI service

.
The service data dialog is displayed. Once you have the restgui service in place do the
following:
1. Change Compression to Yes.

SAP Screen Personas Configuration Guide Addendum


1/2015

SAP Screen Personas Configuration Guide Addendum


2. Click Change.
3. Click the GUI Configuration button.

Modify parameters.
1. Add or set parameter ~XSRFCHECK with value 0. (This is optional but makes potential
debugging easy).
2. Add or set parameter ~WEBGUI with value 1.
3. Remove all other parameters.

4.
5.
6.
7.

Choose Copy Parameter Set


Choose the Error Pages tab.
Change the radio control from System Logon to Explicit Response Time.
Go to the handler list tab and change the handler from CL_HTTP_EXT_ITS to
CL_HTTP_EXT_ITS_BASIC.

SAP Screen Personas Configuration Guide Addendum


1/2015

SAP Screen Personas Configuration Guide Addendum


If CL_HTTP_EXT_ITS_BASIC handler is not present, apply SAP Note 1667055 .
If the SAP Note 1667055 does not apply to your system, use CL_HTTP_EXT_ITS at handler
class; ensure to point this out if issues are found later.

Click Store to save changes.


Right-click RestGUIservice and select Test Service command.
A popup dialog is displayed and you will see the actual URL for RestGUI service.
Switch to persos_app ServiceName
1. Turn Compression to Yes for persos_app

SAP Screen Personas Configuration Guide Addendum


1/2015

SAP Screen Personas Configuration Guide Addendum

SAP Screen Personas Configuration Guide Addendum


1/2015

SAP Screen Personas Configuration Guide Addendum

2.3 Activate Services in SICF


2.3.1

Procedure: Activate
As the initial page to launch SAP Screen Personas in a BSP, the following services need to be
activated in the SICF transaction:
Transaction: SICF

/sap/persos_app
/sap/bc/bsp/persos/mainapp
/sap/bc/bsp/sap/system
/sap/bc/bsp/sap/public/bc
/sap/public/bsp/sap/public/bc
/sap/public/bsp/sap/system
/sap/public/bsp/sap/htmlb
/sap/public/bc
/sap/public/bc/ur
/sap/restgui
/sap/bc/gui/sap/its/webgui (this should be already active, make sure it is
/sap/bc/bsp/persos/mainapp (this should be already active, make sure it is)
Please follow the steps given below to activate each service:

2.3.2

Launch transaction SICF.


Navigate to the specified node.
Right-click the node and select Activate Service from the context menu.
In the popup that appears, select the first button Activate.

Procedure:Test

Test RestGUI Services


It is recommended to test the RestGUI services before you proceed with further configurations.
1. Point your browser to the (actual URL for restgui service) followed by /newsession?sapclient=<client id>.
2. Copy the session ID returned by the system.
3. Point your browser to the following address: (actual URL for restgui service) followed by
/state/text. Add the session ID obtained above in the URL to the /sap/ part of the url.
The URL should look similar to the one given below:

SAP Screen Personas Configuration Guide Addendum


1/2015

SAP Screen Personas Configuration Guide Addendum


https://DOMAINNAME:PORT/sap(cz1TSUQlM2FBTk9OJTNhcGFlcjhkYl9FUjhfNTMlM2F
teUFKZWVvWElOS3pjX09GcUtVeUxEN2tRUnBIc1drajZ2UHJ0MWxsLUFUVA=)/restgui/s
tate/text
2.3.3

Result

You should be able to see a control tree in text notation.

SAP Screen Personas Configuration Guide Addendum


1/2015

SAP Screen Personas Configuration Guide Addendum

3 SPRO Transaction
You can access SAP Screen Personas SPRO Transaction under Cross Applications Component:

The following are all the configuration steps that need to be completed in the SPRO Transaction.

3.1 Maintain Controls for Control Specific Settings


Transaction: SPRO
This can be accessed at SPRO > SAP Customizing Implementation Guide > Cross-Application
Components> SAP Screen Personas > Maintain Controls for Control Specific Settings.
Here users can add new controls and new properties for the controls, apart from the SAP delivered
controls, for which the control specific profile-wide settings will be applied. Profile-wide settings
allowusers to make changes available for all screens in a system instead of a screen by screen basis.
This configuration is a two-step process:
1. Maintain Control Details - Provide the Control Name and Control ID.
2. Maintain Property Details - Select a control created in previous the step and double click
the property details node on the left side.
Here you can add new properties for the selected control. Once you have entered the details, Save
the configuration.
More details on Profile Wide settings can be found under the same header in Administration &
Troubleshooting guide.

SAP Screen Personas Configuration Guide Addendum


1/2015

SAP Screen Personas Configuration Guide Addendum

3.2 Maintain Screen ID Overwrite Logic


This can be accessed at SPRO > SAP Customizing Implementation Guide > Cross-Application
Components> SAP Screen Personas > Maintain Screen Id Overwrite Logic.
This customizing is to maintain Transaction, Program, Original Screen Number, and New Screen
Number. If for some reasons two or more screens are visually appear like one same screen, this
customizing activity will enable Personas to handle these screens as one. The entries for this
configuration are part of the delivered customizing in Personas.
Note: Personas has two types of ID Overwrite Logic: Screen ID and Control ID. Screen ID is under
the SPRO transaction, the Control ID is part of the /persos/ADMIN_UI transaction. See Appendix
for how to tell the difference between Screen ID and Control ID.
All the delivered configurations during installation process are copied to client 000. A client copies
needed to bring in these values to the client where Personas is used.

SAP Screen Personas Configuration Guide Addendum


1/2015

SAP Screen Personas Configuration Guide Addendum

3.3 Maintain Personas Global Settings


This can be accessed at SPRO > SAP Customizing Implementation Guide > Cross-Application
Components> SAP Screen Personas > Maintain Personas Global settings.
SAP Screen Personas provides a capability to group flavors. Groups can be created and maintained
via Admin transaction. Flavors can be assigned to Groups which in turn get distributed to the users
assigned to this Group. In case the Admin wants to distribute flavors to all users in a system at once,
a Global Group helps. Admin can define a Group as Global in this configuration. By doing so, all users
can access the flavors assigned to this Group by default.

SAP Screen Personas Configuration Guide Addendum


1/2015

SAP Screen Personas Configuration Guide Addendum

3.4 Maintain Whitelist URLs


This can be accessed at SPRO-> SAP Customizing Implementation Guide > Cross-Application
Components> SAP Screen Personas > Maintain Whitelist URLs.
This is a place where the allowed websites inside the HTML control should be maintained. A URL can
be used at runtime only if this whitelist is maintained.

SAP Screen Personas Configuration Guide Addendum


1/2015

SAP Screen Personas Configuration Addendum

3.5 Maintain Roles


SAP Screen Personas uses two kinds of Authorization management one used for accessing the
administration transaction and the other which is used for user permission management in the
Silverlight UI.
Backend Authorization Management is implemented using SAP Standard Roles and Authorization
framework.
This can be done in this link SPRO > SAP Customizing Implementation Guide > Cross-Application
Components > SAP Screen Personas > Maintain Personas Roles
By default the following 5 roles are delivered by SAP Screen Personas:

Rendering only (0)


oIT pre-defines the flavor to be loaded for a user/group
ono flavor switching possible

Rendering and flavor switching (1)


oUser can switch between flavors and get new ones from the Flavor Gallery
ono private flavors, therefore, no editing possible

Rendering, visual editing and sharing of flavors (Bits 0-5, and 8-13)(16191)
oUser is able to create private flavors and edit them

Restricted editing (All bits but bit 22) (29360127)


oMost editing features except the advanced scripting

Full editing rights (-1).

SAP Screen Personas Configuration Guide Addendum


7/2014

SAP Screen Personas Configuration Addendum

In addition, Admin can come up with new roles. The steps for this are mentioned in the IMG
configuration help. The following table lists down the different User Permissions per bit position.
Permission Bit Name
AccessToProfileFlavors

Permission
Bit Number
0

Permission
Bit Mask
0x1

AccessToSharedFlavors

0x2

AllowEdit

0x4

AllowGroup

0x8

AllowMove

0x10

AllowResize

0x20

AllowHide

0x40

AllowMandatory

0x80

AllowBackgroundImages

0x100

AllowRecolor

0x200

AllowCreatePostItNote

10

0x400

AllowCreateImage

11

0x800

AllowCreateGroupBox

12

0x1000

AllowCreateLabel

13

0x2000

AllowCreateLauchButton

14

0x4000

AllowCreateScriptButton

15

0x8000

AllowCreateHtmlControl

16

0x10000

SAP Screen Personas Configuration Guide Addendum


7/2014

Description
Allows switching
between flavors
that are part of the
profile
Allows searching for
flavors and adding
them to the profile,
as well as setting a
default
Allows user to enter
edit mode and copy
flavors
Allows user to
group controls and
change Z-Index

Allows user to move


controls
Allows user to
resize controls
Allows user to hide
and show controls
Allows user to
change inputs to
optional/mandatory
Allows user to
upload and set
background images
Allows user to set
color of controls
Allows creating
PostIt notes
Allows creating
image controls
Allows creating
group box controls
Allows creating
label controls
Allows creating
launch button
controls
Allows creating
script button
controls and
recording of scripts
Allows creating

Requires

AccessToSharedFlavors

Requires AllowMove &


AllowResize for
group/ungroup.
Requires
AllowEditLabels or
AllowEditComboBoxes if
they participate in
Group/Ungroup

Requires AllowMove &


AllowResize
Requires AllowMove &
AllowResize
Requires AllowMove &
AllowResize
Requires AllowMove &
AllowResize &
AllowEditLabels
Requires AllowMove &
AllowResize
Requires AllowMove &
AllowResize

Requires AllowMove &

SAP Screen Personas Configuration Addendum


AllowCreateTextBox

17

0x20000

AllowConvertInput

18

0x40000

AllowConditionalFormatting

19

0x80000

AllowEditComboBoxes

20

0x100000

AllowEditLabels

21

0x200000

AllowAdvancedScripting

22

0x400000

AllowCreateCheckBox

23

0x800000

AllowEditButtons

24

0x1000000

ShowBasicView

25

0x2000000

SAP Screen Personas Configuration Guide Addendum


7/2014

HTML controls
Allows creating text
box controls
Allows converting
inputs
Allows setting
conditional
formatting
Allows editing
combo boxes
Allows editing label
controls
Allows using
WebRFC and
JavaScript actions
as part of the Script
Button
Allows creating
Check Boxes
Allows changing
labels and icons of
buttons
Show basic view for
user.

AllowResize
Requires AllowMove &
AllowResize

Requires
AllowCreateScriptButton

SAP Screen Personas Configuration Addendum


3.5.1

Role Creation using PFCG

Roles can be created using transaction PFCG and then assigned to the user. It has to be ensured
that the authorization object /PERS/AOBJ is attached to the role and maintained. This
authorization object uses three parameters described below.
Parameter Description
Transaction Code: This limits/filters activities to a specific transaction. Wild cards are allowed, for
example * to indicate all transactions. You can specify multiple transaction codes separated by a
comma.
Flavor ID: This limits an activity to one flavor, or a pattern of flavor identifiers. Multiple flavor
patterns are separated using comma.
Note
It is mandatory to grant authorization rights to the static flavor ID SAP_PERSONAS.
Activity: The activity for which a specific authorization check is done.
There are seven activities that are allowed for a role. These activities have an increasing level of
privilege. Given below is a table consisting of different roles.
Note
It is mandatory to assign all lower privilege level activities also to the role.
Role
USE

Privilege
1

Activity
16/Execute

SWITCH

03/Display

RESHARE

78/Assign

THEMING
EDIT

4
5

A3/Change Status
02/Change

SHARE

59/Distribute

ADMIN

70/Administrate

SAP Screen Personas Configuration Guide Addendum


7/2014

Description
The user is allowed to see and use the
specific flavor.
The user is allowed to switch between a set
of available flavors.
If the user has a number of predefined
flavors (shared with this user). Then the
user can re-share his flavors with other
users.
The user is allowed to update the theme.
The user is allowed to create and maintain
flavors.
The user is allowed to share own flavors with
other users.
The user is allowed to administer flavors.

SAP Screen Personas Configuration Addendum

Note
In addition to the role, ensure that while accessing the SAP GUI for HTML, the URL parameter
sapie=edge is included in the URL. Without this parameter, the solution will not be enabled on
the UI even if the necessary authorizations are provided.
For example:...webgui?sap-ie=edge&

SAP Screen Personas Configuration Guide Addendum


7/2014

SAP Screen Personas Configuration Addendum

3.6 Maintain Systems


Transaction: SPRO
This can be done in this link SPRO > SAP Customizing Implementation Guide > Cross-Application
Components > SAP Screen Personas > Maintain Systems

SAP Screen Personas can be installed in a central system (termed as Main system) and be connected
to be used with other systems (Target systems). Both the Main and theTarget Systems need SAP
Kernel 7.21 or higher and the System settings mentioned in Section 2.

SAP Screen Personas Configuration Guide Addendum


7/2014

SAP Screen Personas Configuration Addendum

In the SPRO Node, maintain the system Details like System ID, Client, Description, Connector to
SAPSystem. The Value for Connector to SAP System is always ITS. Once the user enters all values and
clickon enter, a GUID is generated in the System Config ID which will be used as the unique ID for any
SystemClient configuration.

Maintain Target System(s)


a. System Details
SPRO> SAP Customizing Implementation Guide > Cross-Application Components > SAP Screen
Personas > Maintain Systems
System Detail

Value (Example)

System (ID)

CNS

Client

800

Group

Test System

Description

Personas Test System

Connector to SAP System

ITS (This value is fixed)

Once the System Details are maintained, select the row and double click on the System Settings on
theleft side navigation. This takes you to the Parameter Maintenance screen for each system.
Maintain the following parameters under System settings:

Service.Uri Please maintain the service name for accessing SAP Screen Personas here. The
defaultservice is /restgui.
Server.Url Please maintain the server link for the system here. For example:
https://ldfss600.pal.ess.corp:50015

SAP Screen Personas Configuration Guide Addendum


7/2014

SAP Screen Personas Configuration Addendum

b. System Setting for the Target System


You have maintained system parameters for all the target system.
Select any target system and enter the parameters and values.
Property Name

Property Value

Service.Uri

/restgui

Server.Url

http(s)://target_system_host:Port

Sap.Language (optional)

EN

Note: Ensure you are using Server.Url and Service.Uri (pay attention to server vs. service and Url
vs. Uri).

SAP Screen Personas Configuration Guide Addendum


7/2014

SAP Screen Personas Configuration Addendum

3.6.1

RFC Destination

Transaction: SM59
Maintain the RFC Destination in the HTTP Connection to ABAP System

Setup the connection

SAP Screen Personas Configuration Guide Addendum


7/2014

SAP Screen Personas Configuration Addendum

Target Host: Maintain the Server URL of the Target System


Service No.; Maintain the Target System Port

Make sure the Logon with User is: SAP RFC Logon or SAP Standard
Language: Preferred Language
Client: Should be the same as the one mentioned in SPRO> Maintain Systems
User: UserID of the target system to authenticate the connection
PW Status: Password of the target system to authenticate the connection

SPRO >Cross-Applications >SAP Screen Personas > Maintain System


SAP Screen Personas Configuration Guide Addendum
7/2014

SAP Screen Personas Configuration Addendum

4 Assign Admin Authorizations


Transaction: SU01
An Admin authorization is required for Admins to access the Admin Transaction. A backend role
/PERSOS/ADMIN_ROLE can be used to give sufficient authorizations to the Administrator. This enables
him/her to access transaction /PERSOS/ADMIN_UI where admin can do various activities like User

If you dont have the role you can use transaction PFCG to create it. See Section 3.6.1
Here is an example of how the /PERSOS/ADMIN_UI transaction is assigned to a higher role:

And the YIDES_IDA role is assigned to a user SU01

SAP Screen Personas Configuration Guide Addendum


7/2014

SAP Screen Personas Configuration Addendum

Get URL to Access SAP Screen Personas from the Installed System
SAP Screen Personas can be accessed from the users PC using a shortcut URL. This URL can be generated
by following the below steps:
1. Goto transaction SICF.
2. Select the following filters and press execute.
a. Hierarchy Type - SERVICE
ob. Service Path - /sap/bc/bsp/persos/mainapp/
3.Select"mainapp" service, right click and click on test service.
4. A GUI Security dialog pops up. Select "Allow this one time" and click ok.
5.You would be taken to the personas application in the default browser window.
This URL can be used as a shortcut to access Personas.

SAP Screen Personas Configuration Guide Addendum


7/2014

SAP Screen Personas Configuration Addendum

Appendix

6.1 Important Programs, Tables and Key Transactions


Services

restgui
: Service for communicating with ITS
/persos_app : Service for communicating with ABAP Storage

/PERSOS/CL_HTTP_HANDLER : Handler class for the service /persos_app

Classes

BSP Applications

/PERSOS/MAIN_APP : The main BSP application that hosts the Silver Light island

Programs

/PERSOS/ADMIN_UI : Personas Administration program

Transactions

/PERSOS/ADMIN_UI: Personas Administrations

Tables (Transaction SE16)


/PERSOS/CONTCHNG : Control Changes data
/PERSOS/CONTLOTR: Alias data related to Control changes
/PERSOS/CONTPROP: Control Property Changes
/PERSOS/DRTX: Delta Rendering Data
/PRESOS/FLAVGRP: Table to store Flavor Shared to a Group
/PERSOS/FLAVOR: Flavor table
/PERSOS/FLAVSYS: Flavors and Systems
SAP Screen Personas Configuration Guide Addendum
7/2014

SAP Screen Personas Configuration Addendum


/PERSOS/FLAVUSR: Table storing Flavors shared with a user
/PERSOS/FRANKENS: Franken Screen Data
/PERSOS/GROUP: Table for storing Group IProfile data
/PERSOS/GROUPS: Table for storing Group Ids
/PERSOS/GRPPFLAV: Table to store Group profile Id and flavor
/PERSOS/MCONT: Table for Media data Contents
/PERSOS/MEDIA: MediaFiles data
/PERSOS/OVRCTL: Control ID Overwrite Logic
/PERSOS/OVRSCR: Screen ID Overwrite Logic
/PERSOS/PERSOSET: Personas Settings
/PERSOS/PROFSET: Profile Wide Setting Controls data
/PERSOS/PROPCONF: List of properties for a control
/PERSOS/REDIRECT: Table for storing Redirect URL
/PERSOS/ROLES : Roles for personas
/PERSOS/SAFELINK: Table for storing Whitelist/Safelinks
/PERSOS/SCRNCHNG: Screen Changes data
/PERSOS/SHRTLINK: Table for storing Shortlinks
/PERSOS/SYSCON: Table System Configuration
/PERSOS/SYSYPROF: System Profile Controls
/PERSOS/SYSSET: System Settings data
/PERSOS/UPROFLAV: UserProfiles And Flavors Ids
/PERSOS/USRGRP: Users and Groups
/PERSOS/USRPRO: User profile date

SAP Screen Personas Configuration Guide Addendum


7/2014

SAP Screen Personas Configuration Addendum


/PERSOS/V-GRPFSY: View for Group and System Data
/PERSOS/V-GRPU: View for Group and System Data
/PERSOS/V_MGUSR: User Selection by Group
/PERSOS/V_MUSR: User Selection by System, Role
/PERSOS/V_OVRCTL: Maintain Rules for Overwrite Control ID
/PERSOS/V_OVRSCR: Maintain Rules from Overwrite Screen ID
/PERSOS/V_PROPCO: View for Property Config Table
/PERSOS/V_PROSET: View for Profile Settings Table
/PERSOS/V_SGRP: View Group and System data
/PERSOS/V-SYSC1: Maintain System details
/PERSOS/V-SYSFLA: Flavor and System data

6.1 Screen ID vs. Control ID


In SAP Screen Personas, essentially we track the changes as per transaction Code+Program Name +
Screen number. But there are certain transactions, where the Program Name and Screen Number
changes.
Why do we need Screen/Program Id OverWrite?
Lets take an example of transaction IW23.
Keep on changing the tabs and notice the ProgramName/ScreenNumber Combination.
On Location data tab, you will see that the Screen Number is 7200
Now, on Tasks tab, you will notice that the Screen Number is 7204.
In Situations like this, we just overwrite the Screen Number

SAP Screen Personas Configuration Guide Addendum


7/2014

SAP Screen Personas Configuration Addendum

In this example you would use Screen ID Overwrite in the SPRO transaction.
Why do we need Control Id Overwrite Rules?
For certain transactions, the Control Ids gets changed dynamically when you do something in that
Screen.
E.g. For ME21N, check the dropdown. Go into Edit mode, and copy its control ID from the Properties
window.

SAP Screen Personas Configuration Guide Addendum


7/2014

SAP Screen Personas Configuration Addendum

Go into Edit mode, and copy its control ID from the Properties window.
Expand/Collapse the Header Panel and then go back into edit mode and check the control id
You will notice that there is difference between the Control IDs BEFORE and AFTER

ses[0]/wnd[0]/usrUSRAREA/subcntSUB0SAPLMEGUI0016/subcntSUB3SAPLMEVIEWS1100/subc
ntSUB2SAPLMEVIEWS1200/subcntSUB1SAPLMEGUI1301/subcntSUB1SAPLMEGUI6000/cmbDYN
_6000LIST

ses[0]/wnd[0]/usrUSRAREA/subcntSUB0SAPLMEGUI0013/subcntSUB3SAPLMEVIEWS1100/subc
ntSUB2SAPLMEVIEWS1200/subcntSUB1SAPLMEGUI1301/subcntSUB1SAPLMEGUI6000/cmbDYN
_6000LIST

First line is before and 2nd line is after. You will see that the control Ids have changed.
So for Personas to have a consistent Control ID, we overwrite in this scenario which you would use the
/persos/ADMIN_UI transaction

6.2 Admin Transaction


Admin Transaction - /PERSOS/ADMIN_UI
General Actions

Flavor Maintenance

Media File Maintenance

Short Link Maintenance


SAP Screen Personas Configuration Guide Addendum
7/2014

Allows you to change and


maintain: Description, Flavor
Owner (a flavor can only have
one owner at a time), Groups
who have access to the Flavor.
You can also copy Flavor,
Delete ( only the Owner and
Admin can delete a Flavor)
Allows you to maintain your
media files. You can edit the
name, delete, and create a
media file. You can also make
the media file global, so user
can view it in their Image
Gallery.
Allows you to maintain and

SAP Screen Personas Configuration Addendum

Transport Objects

Maintain Control ID Overwrite


Logic
Enable Delta Rendering

User Management
Profile Wide Settings

Group Management
Translation
Tools

create short links to your


Flavors.
Transports objects: Flavors,
Groups, and Media Files
between environments.
Please make sure that
Personas is on the same patch
level, client, and kernel level
between the environments.
Some transaction in SAP
changes their control IDs
between tabs. If
Enable Delta Rendering helps
in performance of a
transaction.

User Maintenance
Mass User Maintenance
Control Specific Profile Settings
Type Specific Profile Settings
Global Text Replacement
Group Maintenance
Mass Group Maintenance
Prepare for Translation
Cleanup Redundant Translation
Export Flavors
Import Flavors
Configuration Check

Troubleshooting

I do not see any Personas Roles OR Screen Id Overwrite entries OR Controld ID Overwrite
entries?
SAP Screen Personas is shipped with some pre-configured values which can be found in client 000 of
your system. Follow the Implementation and Configuration Guide or note 1869640 to get these values
from client 000 to client XXX of your system.
Which kernel patch level shall I be on?
If your kernel patch is very old (120 or below), then you should upgrade your kernel patch first before
reporting any issue for unusual Personas behavior.
SAP Screen Personas Configuration Guide Addendum
7/2014

SAP Screen Personas Configuration Addendum

When do I need Screen id OR Control ID overwrite logic?


A typical symptom is when to try to change the colors in tab or even when you try to enable the tab
cache and it does not happens, then you would need either of the overwrite logics.
For e.g. from any transaction, select to see the Program Name and Screen Number as shown below
(ProgramName/ScreenNumber).

At this point, start clicking the all the tabs. For any tab, if the Screen Number changes, then we need
screen id overwrite entry for that particular transaction. For any transaction, if you are not able to figure
out the overwrite entries, please create an OSS message.
Where do I find the latest notes which are being released?
Usual support channel is the preferred way.
Silverlight is stuck on Cross Domain Setup, where do we put files clientaccesspolicy.xml
and crossdomian.xml Silverlight application for SAP web services?

The files have to be accessible at the root of the domain http(s)://host:port/clientaccesspolicy.xml


What if the files are not accessible at the root of the domain?
1. Locate the parameter icm/HTTP/file_access_0 in your system profile. If not found, create one with
the below mentioned value.

OS

Parameter Value

Windows

PREFIX=/sap/public/icmandir/,DOCROOT=$(DIR_ICMAN_ROOT),ARCHIVE=$(DIR_EX
ECUTABLE)\ITS.SAR,CACHECTRL=+28800

Linux,AIX etc.

PREFIX=/sap/public/icmandir/,DOCROOT=$(DIR_ICMAN_ROOT),ARCHIVE=$(DIR_EX
ECUTABLE)/ITS.SAR,CACHECTRL=+28800

2. Locate the parameter icm/HTTP/file_access_1 in your system profile. If not found, create one and
change the parameter value as mentioned below.
OS

Parameter Value

SAP Screen Personas Configuration Guide Addendum


7/2014

SAP Screen Personas Configuration Addendum


Windows
Linux,AIX etc.

PREFIX=/clientaccesspolicy.xml,DOCROOT=$(DIR_ICMAN_ROOT)\clientaccesspolicy.
xml,CACHECTRL=0
PREFIX=/clientaccesspolicy.xml,DOCROOT=$(DIR_ICMAN_ROOT)/clientaccesspolicy.
xml,CACHECTRL=0

3. Locate the parameter icm/HTTP/file_access_2 in your system profile. If not found, create one and
change the parameter value as mentioned below.
OS
Windows

Parameter Value
PREFIX=/crossdomain.xml,DOCROOT=$(DIR_ICMAN_ROOT)\crossdomain.xml,CACHECTRL=0

Linux,AIX
etc.

PREFIX=/crossdomain.xml,DOCROOT=$(DIR_ICMAN_ROOT)/crossdomain.xml,CACHECTRL=0

And, restart your server instance


I can see the SAP Screen Personas System but when I click on i t, it does not open SAP
Screen Personas

In IE9 Open the debug window


Select the network tab
Start Capturing
Click on the system again
You should have at least 3 calls:

service makes sure that restgui is configured correctly if it has 200 then it was configured correctly
2nd call makes sure that the url is on the whitelist and is configured correctly if it has 200 then it was
configured correctly this is only done once
3rd call is the rest gui call also seemed successful (200) this call returns and renders the screen definition
If you dont see the screen definition you want to explore more the 3rd call
Double click on that call
SAP Screen Personas Configuration Guide Addendum
7/2014

SAP Screen Personas Configuration Addendum


Select Response Body
What is expected is XML
If you see HTML
You need to go to your Rest Gui that you have configured on the SAP System
Go to SAP GUI
Transaction SICF
Check the restgui service
Check GUI Configuration
Parameter

Value

~RESTGUI

~XSRFCHECK

~WEBGUI

Check Handler List tab make sure the Handler is correct


CL_HTTP_EXT_ITS_BASIC
If the handler does not exist there is a Note: 1667055

SAP Screen Personas Configuration Guide Addendum


7/2014

SAP Screen Personas Configuration Addendum

While checking the restgui service , and trying to Setup URL Handler facing a pop up
below

Make sure when you are creating the restgui (See Section 2.2: Setup URL Hander) that you are
either Specify a new package or choosing the Local Object button.

The service path name in the SPRO transaction needs to equal the service name in the SICF
transaction.

SAP Screen Personas Configuration Guide Addendum


7/2014

SAP Screen Personas Configuration Addendum

You setup the restgui service wrong and cant delete it

Restgui service is saved into /persos/mainapp package with SAP as owner. So it is not letting you delete
it. It should have been saved into own package or as local object as specified in Section 2.2

/persos/mainapp package will be restricted package because it will contain Personas code. You can try
the following options:
Option 1 (make package modifiable)

Go to SE06 -> System change options -> in the System Components list, scroll down to Personas
and set it to Modifiable
Come back to SICF, delete restgui service and rename restgui1 to restgui
Reset package back to unmodifiable to avoid misuse of package in future.

Option 2 (change restgui service in connections)

Go to SPRO -> Cross-Application Components -> SAP Screen Personas -> Maintain Systems
Select the target system and double click on System Settings

SAP Screen Personas Configuration Guide Addendum


7/2014

SAP Screen Personas Configuration Addendum

Accessing SAP Screen Personas


If you get an access error to SAP Screen Personas URL <https://DOMAINNAME:PORT/
/sap/bc/bsp/persos/mainapp/index.html> you may test the response of following URLs:

Testing access to policy information:


Put following URL into your browser: https://DOMAINNAME:PORT/clientaccesspolicy.xml
Shows content of clientaccesspolicy.xml

If nothing is shown, check the Setup Silverlight Cross Domain section

Put following URL into your browser: https://DOMAINNAME:PORT/crossdomain.xml


Shows content of crossdomain.xml
If nothing is shown, check the Setup Silverlight Cross Domain section

7.1 How to Debug and open a OSS Message


How to debug:
1. Restart Personas with the url parameter log=debug i.e. .../index.html?sap-client=123&log=debug
2. Depending on your browser of choice (install and) open the corresponding debugging view
IE9: Tools/F12 developer tools (or press F12)
FF: We recommend installing Firebug
Chrome: Menu/Tools/Developer Tools
3. Repeat the steps that lead to the wrong behavior
4. Check the communication i.e. is there any failing call e.g. 404 Not found or 500 Server error
a. If the clientaccesspolicy.xml file is not found, make sure that you configured it correctly and
that the files are where they should be
b. If there is something wrong with calls to the restgui service
i. 404: the service is not there or reachable: check the service in SICF
ii. 500: have a look at the response, it usually indicates what it could be e.g.
Memory problem: check the amount of memory that is assigned to your ITS using
the transaction SITSPMON
Transaction dump: check the error report and identify the responsible action
c. If there is something wrong with the Personas service e.g. 500 Server error
i. Check the configuration guide for Personas and verify each step related to the
services
ii. Check the url parameter of the failing service, this usually indicates what part of the
configuration is incorrect
5. Check the console output
6. Now, you should have an idea what is wrong
SAP Screen Personas Configuration Guide Addendum
7/2014

SAP Screen Personas Configuration Addendum


a. If it is a configuration issue, correct it, and try again
b. If you cannot find it, ask an expert e.g.
i. Check on SCN
ii. Create an OSS message for the component XX-PROJ-CDP-271 with the information
outlined below.

What all information I need to provide when creating OSS message?


To decrease the turnaround time, it will be great if following information is provided when creating OSS
message:
a. Make sure you are on the latest patches and notes: See Parent Note: 1964257
b. Kernel Patch Level
b. Provide two types of connections to your environment

HTTP - according to SAP Note 592085


R/3 - according to SAP Note 812732

c. All the connections should be tested with proper credentials provided


d. Detail steps to re-create the issue
e. Please attach the related log of the issue.

SAP Screen Personas Configuration Guide Addendum


7/2014

SAP Screen Personas Configuration Addendum

8 Configuration Checklist
The latest patch of personas allows you to view a Config Checklist
Transaction
Check that you have Personas System setup correctly
/n/persos/admin_ui

Transaction
/n/persos/admin_ui

Transaction RZ10

Transaction SICF

Check your Target System setup correctly

Check the files crossdomain.xml and cientaccesspolicy.xml are uploaded to


the correct directory on the application server
If you are using http protocol to access Personas:
http://serverHost:Port/clientaccesspolicy.xml
http://serverHost:Port/crossdomain.xml
If you are using https protocol to access Personas:
https://serverHost:Port/clientaccesspolicy.xml
https://serverHost:Port/crossdomain.xml
Check the PERSOS_APP exist and the Test Service provides you with a
Personas Log in
Double check that the Compression is Enabled to Yes

SAP Screen Personas Configuration Guide Addendum


7/2014

SAP Screen Personas Configuration Addendum


Transaction SICF

Test the MAINAPP service

Test the Service


Result: You should get a log on screen. URL:
<https://DOMAINNAME:PORT/
/sap/bc/bsp/persos/mainapp/index.html>

Transaction
SE80

Make sure the following files exist under the Main App
ScreenMode.js,
- Silverlight.js,
- SilverlightBrowserIntegration.js
- Utilities.js

SAP Screen Personas Configuration Guide Addendum


7/2014

SAP Screen Personas Configuration Addendum

Transaction SPRO
Transaction SPRO

Transaction SPRO

Menu >System
>Status

Sometimes, there is no system defined. Check that at least one system is


maintained.
Check that ITS Connector is defaulted to your system

For the selected system, check that the parameter Service.Uri exists with
correct spelling and case. The value for this parameter should be maintained
as /restui.
For the selected system, check that the parameter Server.Url exists with
correct spelling and case. The value for this parameter should be maintained
in the following format.
http://<hostname>:<port> or https://<hostname>:<port>
(Some customers, face problems with https:// In such case, try using http://)
Check Basis Version, Kernel Version and Kernel Patch
- Click looking glass under the Component Version

SAP Screen Personas Configuration Guide Addendum


7/2014

Click Next button at bottom to get:

SAP Screen Personas Configuration Addendum

Transaction SICF

Test RESTGUI based on the guide


Example:
When you test the service you will get the following URL
http:// nvpal774.pal.sap.corp:8074/sap/bc/gui/sap/its/restgui?sapclient=800
You need to add the following:
http://nvpal774.pal.sap.corp:8074/sap/bc/gui/sap/its/restgui/newsession?s
ap-client=800
Result: The webpage should return the session id:

If you get a different response, check whether your service is activated and
whether you have the right authorizations.

Example:
Also restgui settings (the following example URL assumes you have configured
restgui service at /sap/restgui):
Put following URL into your browser:
https://DOMAINNAME:PORT/sap/restgui/state/text
Control Tree
--> [_][E][R][_] : CONTROL_TREE
--> [_][E][R][A] ses[0] : SESSION
--> [V][E][R][A] ses[0]/wnd[0] : SAP Easy Access :
PRIMARY_WINDOW

.
If you get different response, check whether your service is activated

SAP Screen Personas Configuration Guide Addendum


7/2014

SAP Screen Personas Configuration Addendum


Other things to consider:
Transaction SPRO

Check System Setting match

Sectio
n 3.7

Transaction SICF

Check that the services are all activated

Transaction SICF

Check that compression is ON for restgui

Transaction SICF

Check GUI Configuration button


~RESTGUI - 1
~XSRFCHECK 0
~WEBGUI - 1
Check that under Handler List tab, you have handler class as
CL_HTTP_EXT_ITS_BASIC
If mentioned handler class is not in your system, implement Note
1667055

Sectio
n 2.3
Sectio
n
2.2.1.1
Sectio
n
2.2.1.1

Transaction SICF

Transaction SICF

Test the WEBGUI service

SAP Screen Personas Configuration Guide Addendum


7/2014

Sectio
n
2.2.1.1

SAP Screen Personas Configuration Addendum

Test the service


Result: You should get a log on screen.
Transaction SICF

Transaction SU01

/PERSOS/ADMIN_UI
> General Actions >
Maintain Control ID
Overwrite Logic
/PERSOS/ADMIN_UI

Test the MAINAPP service

Test the Service


Result: You should get a log on screen.
Check in transaction /PERSOS/ADMIN_UI, if user profile for the user is
created for the system(s) with correct role assigned.

Depending on the transactions you are using, some of them might


need Control ID Overwrite
Make sure it is copied from client 000. If not copy configuration from
client 000
You have assigned the target system to a user /group and appropriate

SAP Screen Personas Configuration Guide Addendum


7/2014

Sectio
n 3.5
Sectio
n
4.1

SAP Screen Personas Configuration Addendum


>User Management

Personas Role.

9 Notes

Personas Cumulative Patch release for Personas Release 1.0/Release 2.0


Note: 1964257

Control and Screen ID Overwrite Rules


Make sure you have all of these transactions in your control and screen ID Overwrite table
Note: 1999747

Kernel Notes
You have implemented the below mentioned important kernel notes
a. 1787341 - Personas:ABAP Interface Restgui
b. 1885506 - Personas:Turn off Control (amodal) based F4 help
c. 1913055 - ABAP interface does not work correctly inside RFC calls (Only applicable for kernel patch 200
onwards)

ITS sizing
You have considered sizing your ITS memory based on note 1888428 and number of expected users.
(For a start, it is recommended to put value of em/global_area_MB as 2048 MB)
To find the current value, go to transaction RZ11 and display the parameter em/global_area_MB.
Contact your system admin if you dont have authorizations to increase this parameter.
ITS Configuration Notes
892442
885580
755726
742048

Integrated ITS configuration/performance


Integrated ITS: Configuration Parameters
Integrated ITS, CPU consumption in R/3 application
Integrated ITS, memory requirement in application

SAP Screen Personas Configuration Guide Addendum


7/2014