Professional Documents
Culture Documents
PUBLIC
Typographic Conventions
Type Style
Description
Example
Words or characters quoted from the screen. These include field names, screen titles,
pushbuttons labels, menu names, menu paths, and menu options.
Textual cross-references to other documents.
Example
EXAMPLE
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
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
Exact user entry. These are words or characters that you enter in the system exactly as they
appear in the documentation.
<Example>
Variable user entry. Angle brackets indicate that you replace these words and characters
with appropriate entries to make entries in the system.
EXAMPLE
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
Document History
Version
Date
Change
1.0
2013-07-31
First release
1.1
2013-08-23
1.2
2014-10-07
Document History
PUBLIC
2013 SAP AG or an
SAP affiliate company. All
rights reserved.
Table of Contents
1
1.1
1.2
1.3
2
2.1
2.2
2.4
3
3.1
5
5.1
5.2
5.3
6
6.1
6.2
References .................................................................................................................................................... 24
2.3
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
Getting Started
1.1
Purpose
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.
Note
The central starting point for the technical upgrade of your SAP solution is the Master Guide, which you
can find on SAP Service Marketplace at http://service.sap.com/instguides.
Use the Master Guide to get an overview of SAP Screen Personas, its software units, and its scenarios from a
technical perspective. The Master Guide is a planning tool that helps you to design your system landscape. It
refers you to the required detailed documentation, mainly:
SAP Notes
Configuration documentation
Section 7, References
This section lists of the SAP Notes and documents that are mentioned in this Master Guide.
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
Note
You can find the most current information about the technical implementation of SAP Screen Personas
and the latest installation and configuration guides on SAP Service Marketplace at
http://service.sap.com/instguides.
We strongly recommend that you use the documents available here. The guides are regularly updated.
Constraints
The business scenarios that are presented here serve as examples of how you can use SAP software in your
company. The business scenarios are only intended as models and do not necessarily run the way they are
described here in your customer-specific system landscape. Ensure to check your requirements and systems
to determine whether these scenarios can be used productively at your site. Furthermore, we recommend
that you test these scenarios thoroughly in your test systems to ensure they are complete and free of errors
before going live.
This Master Guide primarily discusses the overall technical implementation of SAP Screen Personas rather
than its subordinate components. This means that additional software dependencies might exist without
being mentioned explicitly in this document. You can find more information on component-specific software
dependencies in the corresponding installation guides.
1.2
Related Information
1.2.1
Planning Information
For more information about planning topics not covered in this guide, see the following content on SAP Service
Marketplace:
Content
http://service.sap.com/instguides
http://service.sap.com/instguides
Focused Business Solutions
SAP Screen Personas
SAP Screen Personas 2.0
http://help.sap.com/personas
http://service.sap.com/businessmaps
PUBLIC
6
Content
http://service.sap.com/quicksizer
http://service.sap.com/platforms
To access the Platform Availability Matrix directly,
enter
http://service.sap.com/pam
Network security
http://service.sap.com/securityguide
High Availability
http://scn.sap.com/docs/DOC-7848
Performance
http://service.sap.com/performance
http://service.sap.com/sp-stacks
http://scn.sap.com/community/internationalizationand-unicode
1.2.2
The following table lists further useful links on SAP Service Marketplace:
Content
http://service.sap.com/message
http://service.sap.com/notes
http://service.sap.com/swdc
http://service.sap.com/rkt
1.2.3
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
Location
http://service.sap.com/instguides
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
Title
Location
SAP Business Suite Applications
SAP ERP
SAP ERP 6.0
Planning
SAP NetWeaver
http://service.sap.com/instguides
SAP NetWeaver
SAP NetWeaver 7.4
Planning
1.3
You must read the following SAP Notes before you start the installation. These SAP Notes contain the most recent
information on the installation, as well as corrections to the installation documentation.
Make sure that you have the up-to-date version of each SAP Note, which you can find on SAP Service Marketplace
at http://service.sap.com/notes.
SAP Note Number
1776739
Title
Description
Installation Note for SAP
Screen Personas 2.0
1848339
1885334
PUBLIC
8
Solution Overview
2.1
The following software units are of relevance when setting up the solution:
SAP Kernel
The solution is based on ITS (Internet Transaction Server) of SAP Kernel and hence requires SAP Kernel with
release 721 as installation basis.
Component
Release
Support Package
SAP_BASIS
700
SAPKB70017
SAP_BASIS
701
SAPKB70102
SAP_BASIS
702
SAPKB70200
SAP_BASIS
731
SAPKB73100
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
2.2
System Landscape
Since there are two components to this solution, the system landscapes for both the components of SAP Screen
Personas 2.0 are given below.
2.2.1
Figure 1
Multiple-System Landscape
In this scenario, there is more than one system in the system landscape. The add-on can be installed on one of the
systems, which then becomes the main system for Personas. When user launches Personas, in a web browser,
the request is received and processed by the main system. On successful login to the main system, a system
selection page is presented with all the systems in which the user has a user profile created. The user can select
the system and login to it. Users can then create flavors for transactions in any of the connected system including
the main system. However, all master data related to Personas like Groups, User profiles, Flavors etc. are stored
in the main system.
PUBLIC
10
Figure 2
Caution
We strongly recommend that you use a minimal system landscape for productive environment. This will
ensure a smoother migration to Personas 3.0.
2.3
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.
Assign Admin Authorizations
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 Management, Flavor
Management, and Group Management etc. More details about these activities can be found in the SAP Library
documentation.
Maintain Main and Target System List
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 the Target Systems need SAP Kernel 7.21 and the
System settings.
In the SPRO Node, maintain the system Details like System ID, Client, Description, Connector to SAP System. The
Value for Connector to SAP System is always ITS. Once the user enters all values and click on enter, a GUID is
generated in the System Config ID which will be used as the unique ID for any System Client configuration.
Once the System Details are maintained, select the row and double click on the System Settings on the left side
navigation. This takes you to the Parameter Maintenance screen for each system. Maintain the following
parameters under System settings:
SAP Screen Personas 2.0
Solution Overview
PUBLIC
11
Service.Uri Please maintain the service name for accessing SAP Screen Personas here. The default service is
/restgui.
Server.Url Please maintain the server link for the system here. For example:
https://ldfss600.pal.ess.corp:50015
PUBLIC
12
2.
3.
You would be taken to the personas application in the default browser window.
This URL can be used as a shortcut to access Personas.
Maintain Roles
Backend Authorization Management is implemented using SAP Standard Roles and Authorization framework.
By default the following 5 roles are delivered:
Rendering, visual editing and sharing of flavors (Bits 0-5, and 8-13)(16191)
o User is able to create private flavors, edit, and share them.
In addition, the administrator can come up with new roles. More information on Roles is provided in the related
IMG document in the Solution Manager documentation.
The following table lists down the different User Permissions per bit position.
Permission Bit Name
Permission
Bit Number
Permission
Bit Mask
Description
AccessToProfileFlavors
0x1
Allows switching
between flavors
that are part of the
profile
AccessToSharedFlavors
0x2
Requires
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
13
Permission
Bit Number
Permission
Bit Mask
Description
Requires
AllowEdit
0x4
AccessToSharedFlavors
AllowGroup
0x8
Allows user to
group controls and
change Z-Index
AllowMove
0x10
AllowResize
0x20
Allows user to
resize controls
AllowHide
0x40
AllowMandatory
0x80
Allows user to
change inputs to
optional/mandatory
AllowBackgroundImages
0x100
Allows user to
upload and set
background images
AllowRecolor
0x200
AllowCreatePostItNote
10
0x400
Allows creating
PostIt notes
AllowCreateImage
11
0x800
Allows creating
image controls
AllowCreateGroupBox
12
0x1000
Allows creating
group box controls
AllowCreateLabel
13
0x2000
Allows creating
label controls
AllowCreateLauchButton
14
0x4000
Allows creating
launch button
controls
AllowCreateScriptButton
15
0x8000
Allows creating
script button
controls and
PUBLIC
14
Permission
Bit Number
Permission
Bit Mask
Description
Requires
recording of scripts
AllowCreateHtmlControl
16
0x10000
Allows creating
HTML controls
AllowCreateTextBox
17
0x20000
AllowConvertInput
18
0x40000
Allows converting
inputs
AllowConditionalFormatting
19
0x80000
Allows setting
conditional
formatting
AllowEditComboBoxes
20
0x100000
Allows editing
combo boxes
AllowEditLabels
21
0x200000
AllowAdvancedScripting
22
0x400000
Allows using
WebRFC and
JavaScript actions
as part of the Script
Button
AllowCreateCheckBox
23
0x800000
Allows creating
Check Boxes
AllowEditButtons
24
0x1000000
Allows changing
labels and icons of
buttons
ShowBasicView
25
0x2000000
Requires
AllowCreateScriptButton
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
15
2.3.1
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.
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.
PUBLIC
16
Role
Privilege Level
Activity
Description
USE
16/Execute
SWITCH
03/Display
RESHARE
78/Assign
THEMING
A3/Change Status
EDIT
02/Change
SHARE
59/Distribute
ADMIN
70/Administrate
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&
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
17
2.5
Purpose
The following table describes the overall installation sequence for SAP Screen Personas 2.0. This table contains
all available software units.
Process
Implementation Sequence
Step
Action
Remarks/Subsequent Steps
[Required Documentation]
1
PUBLIC
18
The following business scenarios are available for SAP Screen Personas 2.0.
3.1
UI Customization
Overview
In this business scenario, the system is customized in order to enable the admin user to perform necessary
activities that will allow the business user to use this solution.
Under this business scenario, the following business processes are provided:
5.
6.
Managing Flavors
You can use this process to transport objects, export, and import flavors.
For information about technical system landscape, software units, and implementation sequence, see section 2,
Solution Overview.
Further Information
The following documents provide more information about UI Customization.
Content
Location
Configuration Documentation
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
19
Solution-Wide Topics
SAP provides the SAP Solution Manager as the highly recommended platform to efficiently support the
implementation of your solution. Using SAP Solution Manager will significantly accelerate the implementation
process and help you to achieve your business goals. At the same time, SAP will be able to deliver support
services based on the business scenarios designed and documented in SAP Solution Manager. Implementation
content for your solution may further accelerate the implementation process.
For information about availability of content specifically tailored to SAP Screen Personas 2.0, see the SAP
Solution Manager Business Process Repository on SAP Service Marketplace at http://service.sap.com/bpr. On
the right page, follow the link provided in the section Available implementation content.
The Solution Manager content for SAP Screen Personas 2.0 is delivered via the support package SP38, which is
available from SAP Software Distribution Center at http://service.sap.com/swdc.
For more information about SAP Solution Manager, see SAP Service Marketplace at
http://service.sap.com/solutionmanager.
20
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
Security Considerations
This section provides an overview of the security considerations that are specific to the SAP Screen Personas
solution. The solution is based on SAP NetWeaver 7.0 with SAP Kernel 7.21. Therefore, the corresponding security
settings also apply to this solution.
5.1
For a complete list of the available SAP security guides, see SAP Security Guides on SAP Service Marketplace at
http://service.sap.com/securityguide. The current version of the SAP NetWeaver security guide, which deals
with general security issues, is also available via this quick link.
Additional Information
For more information about specific security topics, see the following locations on SAP Service Marketplace:
Content
Location
Security
http://service.sap.com/security
Security Guides
http://service.sap.com/securityguide
Released Platforms
http://service.sap.com/platforms
Network Security
http://service.sap.com/securityguide
Infrastructure Security
http://service.sap.com/securityguide
http://service.sap.com/solutionmanager
5.2
Solution uses the underlying softwares user management and administration framework.
5.3
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
21
Operations Information
This chapter contains important information on how to smoothly operate SAP Screen Personas. The major topics
are monitoring, administration, software change management, and high availability. This chapter describes the
tasks to execute and the tools to use.
SAP Screen Personas can be installed on any SAP system. Therefore, the general operations information that is
covered in the related Operations Guides also applies to SAP Screen Personas. For more information about
related guides, see the corresponding resources on SAP Service Marketplace at
http://service.sap.com/instguides
For a complete list of available SAP Operations Guides, see SAP Service Marketplace at
http://service.sap.com/instguides.
The operations information specific to SAP Screen Personas is described in the following chapters. The following
areas are covered:
6.1
All the backend operations like User Management and Flavor Management are to be performed by the
Administrator. The Application Help defines in detail the functionality and steps to perform these operations.
Please refer to the Application Help in Service Market Place under SAP Screen Personas.
6.1.1
Periodic Tasks
Administrator would be assigning System and Roles to users as and when a new user is added. He would also be
responsible for Group creation and assigning users and flavors to groups. In addition, he also sets a Global group
through which he can distribute flavors to all users.
6.1.2
User Management
There is no separate User Management for SAP Screen Personas. To access SAP Screen Personas, users should
have SAP user access to the system in which SAP Screen Personas is installed. In order to login to other target
systems which are connected to the Main system, a user is required there too. For details on User Authorization
Management in the backend and User Role and Permissions, refer to the Solution Manager document.
22
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
6.2
SAP Screen Personas 2.0 is delivered as an Add-On and can be installed using SAINT. Detailed steps for
installation can be found in the installation Note 1776739.
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
23
References
List of Documents
The following table lists all documents mentioned in this Master Guide.
Title
Where to Find
Solution Manager
http://service.sap.com/solutionmanager
http://service.sap.com/instguides
--- Focused Business Solutions
--- SAP Screen Personas 2.0
http://help.sap.com/personas
Title
Description
1776739
1848339
1885334
24
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
Media List
All deliverables for SAP Screen Personas 2.0 are shipped electronically. The software and documentation
download package is available on SAP Service Marketplace at http://service.sap.com/swdc --- Support Packages
and Patches --- A - Z Index --- P ---SAP Screen Personas 2.0.
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
25
For more information about currently available releases for the SAP Screen Personas solution, and for each
release, the SAP standard software required to install and use the solution, see
http://www.service.sap.com/fbs/availability.
26
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
www.sap.com/contactsap