Perso Nw731v1 Quickguide

SAP NetWeaver 7.31

October 2014

English

Quick Guide to Implementing SAP Screen Personas rapid-deployment solution V1

SAP SE Dietmar-Hopp-Allee 16 69190 Walldorf Germany

SAP Best Practices Quick Guide to Implementing SAP Screen Personas rapid deployment solution

SAP SE Page 2 of 18

Copyright

2014 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.

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. Please see http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

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 SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE 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.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SEs or its affiliated companies strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.
http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark


SAP SE Page 3 of 18

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the

ENTER key.

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

Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.


SAP SE Page 4 of 18

Contents

1 Purpose ................................................................................................................. 6

1.1 Basic Concept of SAP Screen Personas .............................................................. 6

1.2 Architecture ........................................................................................................... 7

2 Solution Overview .................................................................................................. 8

3 System Setup & Preparation ................................................................................. 9

3.1 Release and Support Package Level .................................................................... 9

3.2 Required Product Versions and Software Components ...................................... 10

3.2.1 SAP Screen Personas V2.0 .................................................................................. 10

3.2.2 Microsoft Silverlight ............................................................................................... 11

3.3 Frontend Components ......................................................................................... 11

3.4 SAP Notes and Messages................................................................................... 11

4 Evaluate Business Content/Processes ............................................................... 12

4.1 System Configuration .......................................................................................... 13

4.1.1 Activate Services in SICF ..................................................................................... 13

4.1.2 Setup URL Handler ............................................................................................... 14

4.2 User Maintenance and Settings .......................................................................... 14

4.2.1 Maintain Personas Roles ...................................................................................... 15

4.2.2 Maintain System Details for Personas .................................................................. 15

4.2.3 Assign Administrator Role to User ........................................................................ 16

4.3 Review of Business Processes ........................................................................... 16

5 Security Aspects .................................................................................................. 18

5.1 General Security Guidelines ................................................................................ 18


SAP SE Page 5 of 18

Table of Figures

Figure 1: SAP Screen Personas Architecture (Minimal) ................................................................. 7

Figure 2: SAP Screen Personas Architecture (Productive) ............................................................. 8

Figure 3: SAP GUI Screen for Personnel Actions (Transaction PA40) ......................................... 17

Figure 4: Example SAP Screen Personas Flavor for Personnel Actions (Transaction PA40) ...... 17


SAP SE Page 6 of 18

Quick Guide to Implementing SAP Screen Personas rapid deployment solution V1.731

1 Purpose This quick guide provides step by step information on how you must implement the complete solution package.

Before proceeding with this document, the following activities must be completed:

You have to define the scope relevant for your project.

You have to finalize the technical prerequisites

You have to staff and make available the required resources.

This document does not provide a general overview and explanation of SAP Best Practices. For more information about the Best Practices concepts, see the related documentation on http://service.sap.com/solutionpackages and follow the links to the RDS Learning Maps.

This document is intended for the following project roles, which already have a sound knowledge of SAP Best Practices, including tools and documentation:

System administrators and basis consultants: System set-up and preparation including troubleshooting.

Activation/implementation consultants (basis or application consultants): Activation/implementation of business content and processes.

Business consultants: Evaluate business content/processes including troubleshooting, FAQ, and further information for extended usage of the package.

1.1 Basic Concept of SAP Screen Personas You can use SAP Screen Personas to simplify existing SAP GUI applications and configure them to your needs. Flavors can be created for any SAP GUI transaction and assigned to individual users or groups of users. This means that you can remove fields and elements of the SAP GUI that you do not need and rearrange fields and elements in a manner to support your business requirements and processes.

With these personalized flavors of SAP Screen Personas, you have the following advantages:

Improve business user productivity by providing only the essential screen elements and data to complete business transactions faster and more accurately through fewer data entry fields,

Increase user satisfaction by automating repetitive tasks and simplifying complex screens through pre-filled fields and pull-down menus,

Reduce the cost of personalization by eliminating the need for ABAP programmers or scripting experts,

Decrease training time for SAP users.

SAP Screen Personas 2.0 has two components:

SAP Screen Personas based on Silverlight

SAP Screen Personas based on HTML

This solution only covers the component SAP Screen Personas based on Silverlight. This is because of the functionality that is available in this component.
http://service.sap.com/solutionpackages


SAP SE Page 7 of 18

In this solution all references to SAP Screen Personas (or simply Personas) refer to the component SAP Screen Personas based on Silverlight.

1.2 Architecture The architecture of SAP Screen Personas and its integration into the SAP environment is displayed in the following pictures.

There are two types of system landscape for SAP Screen Personas.

Single System Landscape (Minimal System Landscape)

In this scenario, there is only one system in the system landscape. The add-on is installed on the same system. When a user launches Personas in a web browser, the request is received and processed by this system. Flavors can be created for any GUI transaction in this system and assigned to users/groups.

Figure 1: SAP Screen Personas Architecture (Minimal)

Multiple System Landscape (Productive 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 the 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 created a user profile. 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, and so on are stored in the main system.

Alternatively, the SAP Personas add-on can be installed separately on each server in your landscape.


SAP SE Page 8 of 18

Figure 2: SAP Screen Personas Architecture (Productive)

We strongly recommend that you use a minimal system landscape for test and demo purposes only. For performance, scalability, high availability, and security reasons, do not use a minimal system landscape as your production landscape.

2 Solution Overview SAP Screen Personas rapid-deployment solution V1.731 has the following features:

It is based on SAP NetWeaver 7.31.

It provides guidance on implementing and using SAP Screen Personas V2.0 SP01 or higher.

It provides an accelerated deployment of the required configuration settings.

It provides documentation on how to configure SAP GUI interfaces using SAP Screen Personas to tailor transactions to your organizations requirements.

This solution provides guidance on best practices for designing and developing user experiences using SAP Screen Personas.

The solution provides the following documentation:

Document Title Purpose

Quick Guide to Implementing the SAP Screen Personas V1.731

Guidance on implementing, configuring, and using SAP Screen Personas V2.0

Software Requirements

How-To-Guide Instruction to create SAP Screen Personas Flavor corresponding to an SAP GUI application (transaction)

Solution Details


SAP SE Page 9 of 18

These documents are available in the Service Market Place at https://service.sap.com/rds-ui-personas. In comparison to a conventional best practices solution, this Quick Guide contains a slimmed down offering of assets with the intent to offer you a direct introduction to SAP Screen Personas 2.0.

3 System Setup & Preparation Prior to installing and activating an SAP Best Practices package (SAP BP package), the target SAP Application Server (AS) must be installed together with the Support Package Stack (SPS) specified in this section.

Additionally, the SAP Notes named in the SAP Notes and Messages section in this guide must be implemented.

3.1 Release and Support Package Level The deliverables of SAP Best Practices packages have been developed and tested in a system landscape with specific release and support package (SPS) level. If the SPS level in your system is different, there may be errors during the activation. You may be able to perform the activation activities manually using the configuration guides, but errors may still occur.

Make sure that your system meets the minimum SPS level requirements. In case your system has an exceptional SPS level compared to the SAP Best Practices requirements, only limited support can be provided.

If you need a higher SPS level in your system, for example, because of additional functionality, adhere to the following order: First import and activate the SAP Best Practices package on the SPS levels as mentioned below, then update your system to the target SPS level.

The support package levels relevant for the solution package are listed together with the required components in the Required Product Versions and Software Components section.

Receiving the Software at the Correct SP Level

For delivery of the software, an installation number and a corresponding license agreement are required. An S-USER is required to order software in the Software Catalog or download from the SAP Software Download Center (SWDC) on SAP Service Marketplace (SMP). You can only order unrestricted SAP software. Contact the SAP contract department to ask for a physical shipment or create a customer message on component XX-SER-GEN-CONTR.

For downloading SPSs, use the Maintenance Optimizer in your SAP Solution Manager system. You can also select relevant SPSs manually one-by-one via the SWDC on SAP Service

Marketplace: https://service.sap.com/swdc Support Packages and Patches A-Z Index.

Only the current Service Release (SR) is delivered to SAP customers/partners via the SWDC on SMP and standard delivery (for example, the Software Catalogue). If you encounter the situation that the required SPS for correct SAP BP packages activation is based on a SPS level LOWER than the current Service Release, the request for the necessary SPS is handled by a customer message. For details, see SAP Note 925690 Standard Ordering Procedures for SAP Software.
https://service.sap.com/rds-ui-personashttps://service.sap.com/swdchttps://service.sap.com/sap/support/notes/925690


SAP SE Page 10 of 18

3.2 Required Product Versions and Software Components

The table lists all software required to implement and run the solution:

Product Product Version Component Comments

SAP NetWeaver SAP enhancement package 1 for SAP NetWeaver 7.3 SP08

Application Server ABAP

Software Component Versions:

SAP_ABA 7.31

SAP_BASIS 7.31

SAP enhancement package for SAP ERP

SAP enhancement package 6 for SAP ERP 6.0 SP08

Central Applications Check SAP Note 774615

SAP Screen Personas

SAP Screen Personas 2.0 SP01

Microsoft Silverlight

5 Download at: www.microsoft.com/silverlight/

Required software components and SPS levels are downloaded using the Maintenance Optimizer in SAP Solution Manager. Alternatively, you can download the software manually from the SAP Software Download Center (SWDC) on SAP Service Marketplace.

For detailed information about SPS definition for the SRs of SAP ERP, see SAP Note 774615 Support Package levels of ERP/ECC installations/upgrades.

3.2.1 SAP Screen Personas V2.0 Central Installation Note 1776739 Release Strategy for the ABAP add-on PERSOS provides details on how to install the solution SAP Screen Personas 2.0.

3.2.1.1 Download and Installation of Installation Product

Go to http://service.sap.com/swdc, and then choose Search for Software Downloads. Conduct a search using the following entries:

Search Term SAP SCREEN PERSONAS 2.0

Search Method Exact Term

Search Area Installation and Upgrades

Search Objects Product Versions

SAP Screen Personas is delivered as an add-on and can be installed using transaction SAINT. Detailed information on the installation process is available in note 1776739 Release Strategy for the ABAP add-on PERSOS.

3.2.1.2 Download and Installation of Maintenance Product

To download SAP Screen Personas V2.0 SP01 after you have installed the installed product, go to http://service.sap.com/swdc, and then choose Search for Software Downloads. Conduct a search using the following entries:

Search Term SAP SCREEN PERSONAS 2.0

Search Method Exact Term

Search Area Support Packages and Patches in Maintenance
https://service.sap.com/sap/support/notes/774615http://service.sap.com/swdchttp://service.sap.com/swdchttps://service.sap.com/sap/support/notes/774615https://service.sap.com/sap/support/notes/774615https://service.sap.com/sap/support/notes/1776739http://service.sap.com/swdchttps://service.sap.com/sap/support/notes/1776739https://service.sap.com/sap/support/notes/1776739https://service.sap.com/sap/support/notes/1776739http://service.sap.com/swdc



Search Objects Product Versions

Detailed information on the installation process is available in note 1776739 Release Strategy for the ABAP add-on PERSOS. Information on the content of SP01 is provided in note 1963129 Personas Admin UI Fixes: PERSOS 100 SP3 and PERSOS 200 SP1.

3.2.2 Microsoft Silverlight To work with SAP Screen Personas, the client you are using requires Microsoft Silverlight 5 and a browser that supports Microsoft Silverlight 5. You can download Microsoft Silverlight at www.microsoft.com/silverlight.

Microsoft Silverlight must be installed locally for each user using or modifying an SAP Screen Personas screen.

3.3 Frontend Components The user launches SAP Screen Personas in a web browser. This is the case both for creating and consuming SAP Screen Personas flavors.

All web browsers that are compatible with Microsoft Silverlight 5 can be used for SAP Screen Personas. For details on compatible browsers refer to http://www.microsoft.com/getsilverlight/get-started/install/default.aspx and choose the System Requirements tab page.

3.4 SAP Notes and Messages If issues become apparent after shipment of this SAP Best Practices package (and hence of this document), an SAP Note exists to document how to solve the issues.

Before you start the activation of the related SAP Best Practices scope, check the latest version of the SAP Note for the solution package to obtain updates and corrections for problems that have not become apparent until after shipment.

SAP Note # Description Component Area Remark

774615 This SAP Note contains critical information for implementing the SAP enhancement package 6 for SAP ERP 6.0 SP08

1776739

Release strategy for the ABAP add-on PERSOS

BC-UPG-ADDON

Release planning information

Always check the SAP Note of the SAP Best Practices package for updates on the implementation.

1885312 Recommended notes for SAP Screen

BC-PER-RT-SIL

Consolidated list of recommended notes for
https://service.sap.com/sap/support/notes/1776739https://service.sap.com/sap/support/notes/1776739http://service.sap.com/sap/support/notes/1963129http://service.sap.com/sap/support/notes/1963129http://www.microsoft.com/silverlighthttp://www.microsoft.com/getsilverlight/get-started/install/default.aspxhttp://service.sap.com/sap/support/notes/774615http://service.sap.com/sap/support/notes/1776739http://service.sap.com/sap/support/notes/1885312



SAP Note # Description Component Area Remark

Personas SAP Screen Personas

1848339 Installation and Upgrade note for Personas

XX-PROJ-CDP-271

Installation information

1842360 SAP Screen Personas: Prerequisites for Rel. 1.0 SP1 & Rel. 2.0

Upgrade from SAP Screen Personas 1.0 to SAP Screen Personas 2.0

1885334 Feature list Personas 2.0 Silverlight

Upgrade information

1826286 FAQ/How to Guide for SAP Screen Personas

XX-PROJ-CDP-271

Consulting FAQ for common questions in SAP Screen Personas

1888428 SAPGUI for HTML: Sizing

BC-FES-ITS Installation information

1884539 Considerations when using SAP Screen Personas

BC-PER-RT-SIL

Help for error analysis

Important considerations to be taken into account when using SAP Screen Personas.

1869640 Client copy of Personas delivered Customizing

XX-PROJ-CDP-271

Customizing

1963129 Personas Admin UI Fixes: PERSOS 100 SP3 and PERSOS 200 SP1

BC-PER-RT-SIL

Program error

1964257 Cumulative patch release for the SAP Screen Personas Release 1.0 and 2.0

XX-PROJ-CDP-271

Program error

Collection of all fixes, which will be released on a periodic basis in-order to fix all the issues reported

1980995 Personas Admin UI Flavor Maintenance - Flavor Copy Issue

BC-PER-RT-SIL

Program error

1971878 Personas Admin UI Delta Rendering Fixes

BC-PER-RT-SIL

Program error

Apply all SAP Notes to the system via the SAP Note Assistant (transaction SNOTE). All SAP Notes mentioned as following must have the implementation status Completely implemented. Some SAP Notes require manual action before you set the status to Completely implemented.

To avoid activation errors as a result of generating loads, perform a mass generation using transaction SGEN as described in SAP Note 481548.

4 Evaluate Business Content/Processes The following sections describe the activities that have to be done by the business consultant who is taking care that the business processes work as desired.

The section System Configuration outlines activities that the administrator can carry out to configure the system for SAP Screen Personas.
http://service.sap.com/sap/support/notes/1848339http://service.sap.com/sap/support/notes/1842360http://service.sap.com/sap/support/notes/1885334http://service.sap.com/sap/support/notes/1826286http://service.sap.com/sap/support/notes/1888428http://service.sap.com/sap/support/notes/1884539http://service.sap.com/sap/support/notes/1869640http://service.sap.com/sap/support/notes/1963129http://service.sap.com/sap/support/notes/1964257http://service.sap.com/sap/support/notes/1980995http://service.sap.com/sap/support/notes/1971878http://service.sap.com/sap/support/notes/481548



The section User Maintenance and Settings outlines the activities that the business consultant has to perform to enable system users to exploit the business process documentation. It describes the required user settings.

The section Review of Business Processes provides an overview of how a power user creates a flavor to simplify SAP transactions.

4.1 System Configuration Information on basic system configuration is available in SAP Screen Personas Configuration. Guidance on system configuration for SAP Screen Personas is provided for the following topics:

Setup Silverlight Cross Domain

Activate Services in SICF

Setup URL Handler

Test RestGUI Services

Performance Considerations

You must pay particular attention to the following points, which correspond to the activities documented in SAP Screen Personas Configuration.

4.1.1 Activate Services in SICF To run SAP Screen Personas in a web browser, the following services must be activated in the transaction Maintain Services:

Virtual Hosts / Services Documentation

/sap/persos_app Personas Application

/sap/bc/bsp/persos/mainapp Application launch

/sap/bc/bsp/persos/persona_images Personas Images

/sap/bc/bsp/sap/system System Services Business Server Pages

/sap/bc/bsp/sap/public/bc BASIS MIME OBJECTS

/sap/public/bsp/sap/public/bc BASIS MIME OBJECTS

/sap/public/bsp/sap/system System Services Business Server Pages

/sap/public/bsp/sap/htmlb HTMLB Public Handler

/sap/public/bc Basis Tree (Basis Functions)

/sap/public/bc/ur Unified Rendering

Procedure

1. Choose one of the following navigation options:

SAP Menu Tools Administration Administration Network HTTP Service Hierarchy Maintenance

Transaction Code SICF

2. Navigate to the specified node.

3. Right-click the service.

4. Select Activate Service in the context menu.

5. Choose Activate.
https://service.sap.com/~sapidb/011000358700000799922013E



4.1.1.1 Set Service Option for Compression

For the following services, the compression flag for response documents must be set to Yes:

Virtual Hosts / Services Documentation

/sap/persos_app Personas Application

/sap/bc/bsp/persos/persona_images Personas Images

/sap/public/bsp/sap/htmlb HTMLB Public Handler

/sap/public/bc/ur Unified Rendering

Procedure


SAP Menu Tools Administration Administration Network HTTP Service Hierarchy Maintenance

Transaction Code SICF

2. Navigate to the specified node.

3. Choose the service by double-clicking on the service node.

4. In the Create/Change a Service screen, choose Change.

5. In the Service Data tab page, enter Yes in Compression.

6. Choose Store.

4.1.2 Setup URL Handler The Service /sap/restgui is required. The process to create this is described in the section

Setup URL Handler in the SAP Screen Personas Configuration Guide.

Once the service has been created, it is important that the parameters for the service are set correctly:

The Compression parameter in the Service Data tab page is set to Yes.

The following parameters for GUI Configuration in the Service Data tab page are entered with the following values:

Parameter Name Value

~RESTGUI 1

~XSRFCHECK 0

~WEBGUI 1

The option Explicit Response Time in the Error Pages tab page is selected.

The Handler List in the Handler List tab page has the following entry:

No. Handler

1 CL_HTTP_EXT_ITS_BASIC

4.2 User Maintenance and Settings There is no separate user management for SAP Screen Personas. To access SAP Screen Personas, users must have user access to the SAP system in which SAP Screen Personas is installed.

There are two dedicated user (groups):

Administrators, who can do various activities like User Management and Flavor Management,



Power Users, who create and edit flavors,

End Users or Business Users, who can access and work with released flavors.

For more details, see sections Authorization and Role Concepts Silverlight and Administration and Management in SAP Screen Personas 2.0 Master Guide.

You must pay particular attention to the points listed as following, which correspond to the activities documented in SAP Screen Personas 2.0 Master Guide.

4.2.1 Maintain Personas Roles You can maintain roles to be assigned to the business users. It is through these Roles that the User Permissions are controlled. As a first step you must maintain at least an administrator role.

Procedure

1. Choose the following navigation option:

IMG Menu Cross-Application Components SAP Screen Personas Maintain Personas Roles

Transaction Code SPRO

2. Choose New Entries.

3. Add the following entry:

Role User Permission

ADMIN_ROLE 1-

4. Choose Save.

4.2.2 Maintain System Details for Personas You maintain the system details for those systems where SAP Screen Personas will be used.

The SAP Screen Personas landscape has one main system and can be extended to be used in multiple systems.

Procedure


IMG Menu Cross-Application Components SAP Screen Personas Maintain Systems

Transaction Code SPRO

2. Choose New Entries.

3. Enter the following entries:

Field Name Entry Value

System

Client

Group

Description

Connector to SAP System ITS

4. Mark the line containing the system details that you have added.



5. Double-click on System Settings.

6. In the Change View System Settings: Overview screen, add the following entries:

Property Name Property Value

Service.Uri /restgui

Server.Url https://:

If you have a system landscape with several servers for load balancing, the URL-address that you call to execute SAP Screen Personas must be the domain that you

enter in the property for Server.Url.

7. Choose Save.

4.2.3 Assign Administrator Role to User

Procedure

1. Enter the following transaction code:

Transaction Code /PERSOS/ADMIN_UI

2. Open the User Management folder in the left panel.

3. Choose Mass User Maintenance.

4. Enter the user names of the SAP Screen Personas administrators in User Name.

5. Enter the system configuration id in System Config ID.

6. Enter ADMIN_ROLE in Personas Role.

7. Choose Execute.

4.3 Review of Business Processes Example steps on how to create your own simplified screen transferring an SAP GUI application to an SAP Screen Personas application:

1. Open SAP Screen Personas.

2. Open target system (for example SAP ERP backend).

3. Create a flavor as a copy of the Basic View.

4. Hide unnecessary elements of the screen (for example, grids).

5. Hide unnecessary elements of the SAP Easy Access bar.

6. Hide unnecessary elements of the SAP menu bar.

7. Add your customized content.

8. Design your screen (upload of background picture, arrange buttons and other elements).

9. Connect transactions, scripts, and so on to buttons.

10. Save flavor.

The above steps show an abstract proceeding. The document How to Create Screen Personas Flavors provides further information on these topics.



The following screen shots show a comparison of example screens for SAP GUI and SAP Screen Personas for Personnel Actions (transaction PA40):

Figure 3: SAP GUI Screen for Personnel Actions (Transaction PA40)

Figure 4: Example SAP Screen Personas Flavor for Personnel Actions (Transaction PA40)



5 Security Aspects This section provides an overview of the security-relevant information that applies to the deliverables of this solution package.

5.1 General Security Guidelines This section provides an overview of security considerations that are specific to the SAP Screen Personas solution. The solution is based on SAP NetWeaver 7.31.

Therefore, the corresponding security settings also apply to this solution.

For more details, see section Security Considerations in SAP Screen Personas 2.0 Master Guide.

Documents

Perso Nw731v1 Quickguide