You are on page 1of 18

PUBLIC

2017-05-15

Configuration Guide
Content

1 Implementation Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2 Pre-Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

3 Installation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

4 Configuring SAP Screen Personas 3.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

5 Configuring Authorizations and Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Configuration Guide
2 PUBLIC Content
1 Implementation Considerations

This page provides an overview of implementation requirements for SAP Screen Personas 3.0 SP05.

This document describes all necessary activities for the implementation and initial configuration of SAP Screen
Personas 3.0 SP05 . In addition, it provides information about the components and guides that are required
during the process.

Validate that you have appropriate patches, notes, and kernel levels.

Table 1:

SAP Basis Minimum SP Additional Required Notes Supported Kernel Releases

700 SP25 SAP Notes: 722


1648418 , 2206295 ,
2136360 , 2185530 ,
2223578 , 2140417

701 SP10 SAP Notes: 722


1648414 , 2206295 ,
2136358 , 2185526 ,
2223624 , 2140417

702 SP09 SAP Notes: 722


1648418 , 2219194 , 2136356
, 2223629

731 SP07 Yes - 722

See Pre-Installation Checklist


[page 5]

740 SP03 Yes - 742*, 745, 749**

See Pre-Installation Checklist


[page 5]

750 All None 745, 749

S/4HANA All None 749

742* - We recommend upgrading to kernel releases 745 or 749 which are downward compatible to SAP Basis
740.

749** - To use this kernel release, SAP_BASIS SP08 or higher is required.

Install the required minimum kernel patch level according to SAP Note 2447934 for SAP Screen Personas 3.0
SP05.

Configuration Guide
Implementation Considerations PUBLIC 3
Note
Please note the following regarding SAP NetWeaver releases older than 740:

There are no plans to support any older SAP NetWeaver Basis Release or service packs that are not listed
above. There are also no plans to support SAP Screen Personas 3.0 on an older kernel release than 722.

The development team designed and tested SAP Screen Personas 3.0 on the above SAP NetWeaver releases
and Basis service packs. However, a number of issues have been addressed and due to technical constraints
have not been down-ported to older support packages (for example, SAP Note 2207791 SAP GUI for
HTML:Whitelist-Service for Clickjacking Framing Protection). Therefore, we strongly advise to run SAP Screen
Personas 3.0 only on:

SAP_BASIS 700 SP29+


SAP_BASIS 701 SP14+
SAP_BASIS 702 SP14+
SAP_BASIS 731 SP09+

For service packs lower than these, only limited support is offered and known issues exist that can only be
addressed via an SAP_BASIS upgrade.

For roadmap information on kernel releases and basis service packs, please read SAP Note 1969546.

Related Information

Pre-Installation Checklist [page 5]


Installation Steps [page 7]

Configuration Guide
4 PUBLIC Implementation Considerations
2 Pre-Installation Checklist

This page provides an overview of requirements of pre-installation steps for SAP Screen Personas 3.0 SP05.

Up to SAP NetWeaver Basis 740 SP08, certain notes need to be implemented to enable SAP Screen Personas
3.0, otherwise the solution will not be available or work correctly.

Enabling SAP NetWeaver Basis 731 for Personas:

Apply the following SAP Notes:

2219194
2135723
2223645

For SP07 or SP08

1. Apply SAP Note 2007072 , Class include is not activated following implementation of SAP note.

Note
Close your current SAP GUI session, and reconnect to your system before proceeding.

Enabling SAP NetWeaver Basis 740 SP03 - SP08

Depending on the installed basis service pack, a corresponding SAP Screen Personas 3.0 enablement note has to
be applied. Before the note can be implemented, the following steps must be executed, otherwise there is a risk to
bring your system into an inconsistent state.

1. Apply SAP Note 2007072 - Class include is not activated following implementation of SAP note.

Note
Close your current SAP GUI session, and reconnect to your system before proceeding

2. Depending on your NW Basis SP level you have to implement one of the following notes:
SP03: Apply SAP Note 1918906
SP04 - SP07: Apply SAP Note 2044643

Note
Before installing SAP Screen Personas 3.0, if you are on SAP NetWeaver Basis SP03 or SP04, apply SAP
Note 2218621 .

Exchanging the kernel

Please check SAP Note 2447934 for the recommendation on kernel patch level.

For more information about kernel exchanges, please read SAP Note 19466 .

Configuration Guide
Pre-Installation Checklist PUBLIC 5
Note
The kernel is composed of multiple components that do not always have the same version number, that is,
some components are updated more frequently. When a kernel patch is recommended by the Personas Team,
this refers to the patch level of the "disp+work" package found under section "Database Independent", based
on your kernel and OS in Service Marketplace. Please make sure that you keep all components up-to-date.

Recommended basis and Internet Transaction Server (ITS) notes

Please check SAP Note 2447934 for the list of required and recommended ITS/BASIS notes. Depending on
your SAP_BASIS release and support package level, SNOTE tells you whether a note is needed or not.

Configuration Guide
6 PUBLIC Pre-Installation Checklist
3 Installation Steps

This page provides an overview of requirements of installation steps for SAP Screen Personas 3.0 SP05

Procedure

1. Deploy the necessary kernel release and patch. Pre-Installation Checklist [page 5] See Exchanging the
Kernel section.
2. For SAP NetWeaver 731 SP07 -SP08 and 740 SP03 - SP08:
Implement SAP Note 2007072 . Pre-Installation Checklist [page 5]
3. According to your SAP NetWeaver release, implement the following notes. Implementation Considerations
[page 3]
4. Depending whether this is a new Personas installation or an upgrade from an earlier support package, select
one of the following:
In case of new installation, install the Personas 3.00 add-on and support packages SP01 - SP05.
If upgrading from an earlier support package, install the new support package(s).
5. SAP05 XPRA (eXecution of PRogram After Import) Report
When upgrading from SP04 to SP05, an XPRA report automatically runs and upgrades data between the
two SPs. Any errors during this XPRA report execution would be added to the upgrade transport log.
Refer to SAP Note 2465796 for details on how to resolve these errors.
When upgrading from SP03 or lower to SP05, the XPRA report will not upgrade the data to SP05. Refer to
SAP Note 2465796 for details on how to upgrade data from such SPs to SP05.
6. See SAP Note 2447934 for a list of all relevant notes. Implement the basis and Internet Transaction Server
(ITS) related notes as applicable to your environment. Adjust the System Change Option via transaction SE03
or SE06 so that software component PERSONAS and namespace /PERSONAS/ are set to "Modifiable". Also
apply all Personas-specific (client/frontend, backend, overwrite entries) notes listed in this note.
SAP Note 2447934 is always kept up-to-date to include all notes relevant for SAP Screen Personas 3.0
SP05. Subscribe to this note to help keep your Personas installation current.
You can use the "Personas Notes Checker" function in the Health Check to verify whether your
Personas installation is missing any of the required notes.

Related Information

Implementation Considerations [page 3]


Pre-Installation Checklist [page 5]

Configuration Guide
Installation Steps PUBLIC 7
4 Configuring SAP Screen Personas 3.0

This page provides an overview of requirements of configuration for SAP Screen Personas 3.0 SP05

Procedure

1. Configure the following instance profile parameters using transaction RZ10, then restart the system:
Update the current value of parameter em/global_area_MB to at least 1GB. For further details, check
SAP Note 1888428 .
Check SAP Note 2299342 to see whether a change to parameter ztta/diag_area is necessary. If your
system uses a kernel patch below the listed ones or in doubt, set it to at least 10MB (10000000 bytes).
For further details regarding this parameter, also check SAP Note 204502 .
2. Complete the service configuration
Activate the following services in transaction SICF:
/default_host/sap/bc/personas
/default_host/sap/bc/personas3
/default_host/sap/bc/gui/sap/its/webgui
Ensure and test that the webgui service is fully operational
Verify that the personas service has the following GUI Configuration parameters:

Table 2:

Parameter Name Value

WEBGUI 1

XSRFCHECK 1

THEME sap_bluecrystal

WEBGUI_DLGAREA2 1

WEBGUI_DLGAREA2_MBAR 1

SAP-IE edge

SAP-HTMLRENDERMODE standards

Additional required parameters for SAP NetWeaver Basis 700 and 701:

Parameter Name Value

WEBGUI_NEW_DESIGN 1

3. Assign Roles
In this step, you assign Personas role(s) for the specified user(s). You can either use the preconfigured
shipped roles or create new ones.

Configuration Guide
8 PUBLIC Configuring SAP Screen Personas 3.0
Go to transaction SU01, select a user and under the Roles tab, enter one of the following preconfigured
roles:
/PERSONAS/ADMIN_ROLE for full right to all Personas features
/PERSONAS/ANALYTICS_ROLE for analytics features
/PERSONAS/CONSUMER_ROLE for standard user with authorization to manage flavors
/PERSONAS/EDITOR_ROLE for business user with full editing rights
/PERSONAS/SUPPORT_ROLE for displaying or editing flavor sharing .
/PERSONAS/TRANSLATE_ROLE for translation rights
Alternatively, you can also create new roles.
4. Use the Configuration Checklist
Go to transaction /PERSONAS/ADMIN and press Run Health Check Tool button under Additional
Administrative Tasks. Look through all the entries and ensure that there are no red status lights.
Make sure you are using the latest version of your web browser to edit flavors. Please see SAP Note
2050838 for browser considerations.
5. Test Configuration
In this step, you launch SAP Screen Personas 3.0
Option 1:
In transaction SICF, select Hierarchy Type SERVCIE and Service Name personas
In the Services tree list, right click the personas service and select Test Service.
Option 2:
Test the following URL by replacing host, domain, and port with your values: http(s)://
host.domain:port/sap/bc/personas?sap-ie=edge
Your default web browser opens and the SAP GUI for HTML appears. After some initial compilation and
decompression time (on first load per application server) , the browser shows a blue line on top with four
dots in the middle. Upon hovering over the blue line, the Personas icon appears. Click this icon to start
SAP Screen Personas 3.0

Configuration Guide
Configuring SAP Screen Personas 3.0 PUBLIC 9
5 Configuring Authorizations and Roles

This page provides an overview of requirements for roles and authorizations for SAP Screen Personas 3.0 SP05

SAP Screen Personas 3.0 is only enabled for a user when the relevant authorizations (based on a user role) are
granted. This is essential, since without the necessary authorization, the solution will not be available. Role
assignment happens through the regular user administration process.

Procedure

The standard product delivery includes a set of roles. You can use these roles to allow users access to the system
via Personas. After installation of the Personas add-on, these roles do not yet have the necessary authorization
profile. Please ensure that you create the authorization profile for each role via transaction PFCG to activate them
fully before assignment.

If these roles are not sufficient, new roles can also be created using transaction PFCG. Based on the standard
delivered roles, and using the below authorization objects, you can define custom roles to achieve the desired
level of granularity to control access to various functions.

SAP Screen Personas 3.0 uses the following authorization objects:

Transaction code check at the star of a transactiont (S_TCODE)


This is the usual object, which determines what transaction codes the user is allowed to run.

Administrative Authorizations( P_ADMIN)


This object controls the Personas Administration features

Authorization Value Description

Admin Activity 01 Admin

Full administrative access to all features in transaction /PERSONAS/ADMIN

02 Support

Access to transaction /PERSONAS/USERSand /PERSONAS/FLAVORS.


Ability to share or assign flavors to user or roles.

03 Analytics

Access to the analytics features

04 Translate

Access to flavor translation without permitting other admin functions ( via


transaction /PERSONAS/FLAVORS)

Edit Authorizations (P_EDIT)


This object controls the features that allow accessing various activities while editing flavors or themes

Configuration Guide
10 PUBLIC Configuring Authorizations and Roles
Authorization Value Description

Edit Activity 01 Position_Size

Allows setting the coordinates and size parameters of screen


controls.

02 Set_Defualt

Set default field values for text fields, checkboxes, radio button etc.

03 Font

Set font family, color, size, and other properties of controls texts.

04 Style

Style group functions, like Fill Color, Border Style, Read Only,
Suggested etc.

05 Annotate

Access to the "Insert" table. Add labels, sticky notes, images, HTML
viewer. Access Toolbox (deleting and cloning objects).

06 Macros

Add buttons, dropdowns, checkboxes, and text fields. Assign scripts


to control or screen events. Access to "Tables" tab.

07 Advanced

Permits the use of Conditional Formatting in the Tables tab.

08 Admin_Edit

Access to Compress Undo History and Versioning in the Release Tab.

Framework 01 Dynpro

Allows the selected activities for the specified traditional Dynro-based


transactions

02 Web Dynpro

Allows the selected activities for the specified WDA application(s).

Application ID Transaction code(s) or WDA application name(s).

Runtime authorizations (P_RUNTIME)


This object controls the activities the user can perform with a flavor, or a theme.

Authorization Value Description

Runtime activity 01 Use Flavors and Themes

Configuration Guide
Configuring Authorizations and Roles PUBLIC 11
Authorization Value Description

Allows running the assigned default


flavor and theme.

02 Selecting flavors

Allows selection of the desired flavor


via the Flavor Bar.

03 Manage flavors

Access to flavor sharing, editing,


creation, and deletion.

04 Editing flavors

Access to flavor sharing, editing ,


creation, and deletion.

05 Creating and editing scripts

Permits the use of the Script Editor.

06 Theming and templates

Allows using the Theme and


Template editor.

07 Runtime administration

Permits editing of flavors that are


owned by other users.

Framework 01 Dynpro

Allows the selected activities for the


specified traditional Dynpro-based
transaction.

02 Web Dynpro

Allows the selected activities for the


specified WDA application(s).

Application ID Transaction code(s) or WDA


application name(s).

Administration authorizations (/P30/ADMIN)


The following are the administration authorization objects.

Authorization Value Description

Field Activity 01 Create

Configuration Guide
12 PUBLIC Configuring Authorizations and Roles
Authorization Value Description

02 Change

03 Display

06 Delete

08 Display change documents

21 Transport

60 Import

61 Export

67 Translate

90 Copy

Field P_30 Object- for the following USERCONFIG Configuring user for Personas.
Objects

ROLECONFIG Configuring roles for Personas.

MEASUREMENT For configuring Analytics

Note
The /P30/ADMIN authorization object is a more granular level of authorizations then the P_ADMIN
authorization object. In future releases of SAP Screen Personas 3.0 additional objects like Flavor, Theme,
Resources etc. will be supported by the /P30/ADMIN.

The following matrix explains how these authorizations are distributed in case of the standard delivered roles.
There are additional roles that are shipped with SAP Screen Personas 3.0 but only 3 main roles are document in
the table.

Values Consumer Role Editor Role Admin Role

Transaction Code

/PERSONAS/* X

/PERSONAS/ADMIN X

/PERSONAS/FLAVORS X

/PERSONAS/RESOURCES X

/PERSONAS/ROLES X

Configuration Guide
Configuring Authorizations and Roles PUBLIC 13
Values Consumer Role Editor Role Admin Role

/PERSONAS/TEST X

/PERSONAS/THEMES X

/PERSONAS/USERS X X

Admin Activity

01 - Admin X

02 - Support X

03 - Analytics X

04 - Translate X

Edit Activity

01 - Position_Size X X

02 - Set X X

03 - Font X X

04 - Style X X

05 - Annotate X X

06 - Macros X X

07 - Advanced X X

08 - Admin_Edit X X

Runtime Activity X

01 - Use Flavors and Themes X X X

02 - Selecting Flavors X X X

03 - Manage Flavors X X X

04 - Editing Flavors X X

05 - Creating and editing X X


scripts

06 - Theming and templates X X

07 - Runtime administration X

Configuration Guide
14 PUBLIC Configuring Authorizations and Roles
Framework Consumer Role Editor Role Admin Role

01 - Dynpro X X X

02 - Web Dynpro X X X

03 - UI5 X X X

TCode/Application ID * * *

Configuration Guide
Configuring Authorizations and Roles PUBLIC 15
Important Disclaimers and Legal Information

Coding Samples
Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system
environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and
completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP
intentionally or by SAP's gross negligence.

Accessibility
The information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be a
binding guideline on how to ensure accessibility of software products. SAP in particular disclaims any liability in relation to this document. This disclaimer, however, does
not apply in cases of willful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect contractual obligations of SAP.

Gender-Neutral Language
As far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as "sales
person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does not
exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.

Internet Hyperlinks
The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not
warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages
caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for transparency
(see: http://help.sap.com/disclaimer).

Configuration Guide
16 PUBLIC Important Disclaimers and Legal Information
Configuration Guide
Important Disclaimers and Legal Information PUBLIC 17
go.sap.com/registration/
contact.html

2017 SAP SE or an SAP affiliate company. All rights reserved.


No part of this publication may be reproduced or transmitted in any
form or for any purpose without the express permission of SAP SE
or an SAP affiliate company. The information contained herein may
be changed without prior notice.
Some software products marketed by SAP SE and its distributors
contain proprietary software components of other software
vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company
for informational purposes only, without representation or warranty
of any kind, and SAP or its affiliated companies shall not be liable for
errors or omissions with respect to the materials. The only
warranties for SAP or SAP affiliate company 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 SE (or an SAP affiliate company) in Germany and other
countries. All other product and service names mentioned are the
trademarks of their respective companies.
Please see http://www.sap.com/corporate-en/legal/copyright/
index.epx for additional trademark information and notices.