Upload
campeador2012
View
215
Download
0
Embed Size (px)
Citation preview
7/25/2019 s Perso Nw731v1
http://slidepdf.com/reader/full/s-perso-nw731v1 1/20
SAP NetWeaver 7.31
April 2014
English
Quick Guide toImplementing SAP ScreenPersonas Rapid-Deployment Solution V1
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany
7/25/2019 s Perso Nw731v1
http://slidepdf.com/reader/full/s-perso-nw731v1 2/20
SAP Best Pract ices Quick Guide to Implementing SAP Screen Personas
© SAP AG Page 2 of 20
Copyright
© 2014 SAP AG 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 theexpress permission of SAP AG or an SAP affiliate company. The information contained herein may bechanged without prior notice.
Some software products marketed by SAP AG and its dis tributors contain proprietary software componentsof other software vendors.
National product specifications may vary.
These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informationalpurposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errorsor om issions with respect to the materials. The only warranties for SAP Group products and services arethose 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 wel l as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and other countries. Please seehttp://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark informationand notices.
7/25/2019 s Perso Nw731v1
http://slidepdf.com/reader/full/s-perso-nw731v1 3/20
SAP Best Pract ices Quick Guide to Implementing SAP Screen Personas
© SAP AG Page 3 of 20
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 fieldnames, 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 keywords 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 asnames 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.
<Example text> Variable user entry. Pointed brackets indicate that you replace thesewords and characters with appropriate entries.
7/25/2019 s Perso Nw731v1
http://slidepdf.com/reader/full/s-perso-nw731v1 4/20
SAP Best Pract ices Quick Guide to Implementing SAP Screen Personas
© SAP AG Page 4 of 20
Contents
1
Purpose .........................................................................................................6
1.1
Basic Concept of SAP Screen Personas ..........................................................6
1.2
Architecture ... .... ... .... ... .... ... .... ... ... .... .... .... ... .... .... ... .... ... .... ... .... ... .... ... .... ... ... ..7
2 Solution Overview...........................................................................................9
3 System Setup & Preparation.......................................................................... 10
3.1 Release and Support Package Level ............................................................. 10
3.2
Required Product Versions and Software Components ...... ........ ......... ........ .... 11
3.2.1
SAP Screen Personas V2.0 ........................................................................... 11
3.2.2
Microsoft Silverlight ....................................................................................... 12
3.3
Frontend Components .................................................................................. 12
3.4
SAP Notes and Messages ............................................................................. 12
4
Evaluate Business Content/Processes ........................................................... 14
4.1 System Configuration.................................................................................... 14
4.1.1
Activate Services in SICF ..... .... .... .... .... ... .... ... ... .... .... .... ... .... .... ... .... ... .... ... .... 14
4.1.2
Setup URL Handler ....................................................................................... 15
4.2 User Maintenance and Settings ........ ........ ......... ....... ........ ........ ......... ....... ..... 16
4.2.1 Maintain Personas Roles ............................................................................... 16
4.2.2 Maintain System Details for Personas ............................................................ 16
4.2.3
Assign Administrator Role to User ... .... ... .... ... .... .... ... .... ... .... ... .... ... .... ... .... ... ... 17
4.3
Review of Business Processes ...................................................................... 17
5
Security Aspects ........................................................................................... 20
5.1
General Security Guidelines .............. ......... ........ ....... ........ ......... ........ ....... .... 20
7/25/2019 s Perso Nw731v1
http://slidepdf.com/reader/full/s-perso-nw731v1 5/20
SAP Best Pract ices Quick Guide to Implementing SAP Screen Personas
© SAP AG Page 5 of 20
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) ........... ........ ......... ....... ..... 18
Figure 4: Example SAP Screen Personas flavor for Personnel Actions (transaction PA40) .... .... 19
7/25/2019 s Perso Nw731v1
http://slidepdf.com/reader/full/s-perso-nw731v1 6/20
SAP Best Pract ices Quick Guide to Implementing SAP Screen Personas
© SAP AG Page 6 of 20
Quick Guide to Implementing the SAP ScreenPersonas V1.731
1 PurposeThis quick guide provides step by step information you must implement the complete solutionpackage.
Before proceeding with this document you must have completed the following activities:
Defined the scope relevant for your project
Finalized technical prerequisites
Staffed and made available the required resources
This document does not provide a general overview and explanation of SAP Best Practices. Formore 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 includingtroubleshooting
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 PersonasYou can use SAP Screen Personas to simplify exist ing SAP GUI applications and configure them
to your needs. Flavors can be created for any SAP GUI transaction and assigned to individualusers or groups of users. This means that you can remove fields and elements of the SAP GUIthat you do not need and rearrange fields and elements in a manner to support your business
requirements and processes.
With this personalized flavors of SAP Screen Personas you
Improve business user productivity by providing only the essential screen elements anddata to complete business transactions faster and more accurately through fewer dataentry fields
Increase user satisfaction by automating repetitive tasks and simplifying complex screensthrough pre-filled fields and pull-down menus
Reduce the cost of personalization by eliminating the need for ABAP programmers orscripting 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 isbecause of the functionality that is available in this component.
7/25/2019 s Perso Nw731v1
http://slidepdf.com/reader/full/s-perso-nw731v1 7/20
SAP Best Pract ices Quick Guide to Implementing SAP Screen Personas
© SAP AG Page 7 of 20
In this solution all references to SAP Screen Personas (or simply Personas) refer tothe component SAP Screen Personas based on Silverlight.
1.2 ArchitectureThe 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 thesame 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 andassigned 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 beinstalled 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 mainsystem. On successful login to the main system, a system selection page is presented with all thesystems 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 themain system. However, all master data related to Personas like groups, user profiles, flavors andso on are stored in the main system.
Alternatively the SAP Personas add-on can be installed separately on each server inyour landscape.
7/25/2019 s Perso Nw731v1
http://slidepdf.com/reader/full/s-perso-nw731v1 8/20
SAP Best Pract ices Quick Guide to Implementing SAP Screen Personas
© SAP AG Page 8 of 20
Figure 2: SAP Screen Personas Architecture (productive)
We strongly recommend that you use a minimal system landscape for test and demopurposes only. For performance, scalability, high availability, and security reasons,do not use a minimal system landscape as your production landscape.
7/25/2019 s Perso Nw731v1
http://slidepdf.com/reader/full/s-perso-nw731v1 9/20
SAP Best Pract ices Quick Guide to Implementing SAP Screen Personas
© SAP AG Page 9 of 20
2 Solution Overview
SAP Screen Personas rapid-deployment solution V1.731 Is based on SAP NetWeaver 7.31
Provides guidance on implementing and using SAP Screen Personas V2.0 SP01 orhigher
Provides an accelerated deployment of the required configuration settings
Provides documentation on how to configure SAP GUI interfaces using SAP ScreenPersonas to tailor transactions to your organization’s requir ements.
This solution provides guidance on best practices for designing and developing user experiences
using SAP Screen Personas.
The solution provides the following documentat ion
Document Title Purpose
Quick Guide to Implementing the SAPScreen Personas V1.731
Guidance on implementing, configuring, andusing SAP Screen Personas V2.0
Software Requirements
How-To-Guide Instruction to create SAP Screen PersonasFlavor corresponding to an SAP GUI application
(transaction)
Solution Details
These documents are available in the Service Market Place at
https://service.sap.com/rds-ui-personas. In comparison to a conventional bestpractices solution this contains a slimmed down offering of assets, with the intent tooffer you a direct introduction to SAP Screen Personas 2.0.
7/25/2019 s Perso Nw731v1
http://slidepdf.com/reader/full/s-perso-nw731v1 10/20
SAP Best Pract ices Quick Guide to Implementing SAP Screen Personas
© SAP AG Page 10 of 20
3 System Setup & PreparationPrior to installing and act ivating an SAP Best Practices package (SAP BP package), the targetSAP 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 beimplemented.
3.1 Release and Support Package LevelThe deliverables of SAP Best Practices packages were developed and tested in a systemlandscape 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 activationactivities manually using the configuration guides, but errors may still occur.
Make sure that your system meets the minimum SPS level requirements. In caseyour system has an exceptional SPS level compared to the SAP Best Practicesrequirements, only limited support can be provided.
If you need a higher SPS level in your system, for example, because of additionalfunctionality, first import and activate the SAP Best Practices package on the SPSlevels 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 requiredcomponents 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 arerequired. 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 onlyorder unrestricted SAP software. Contact the SAP contract department to ask for a physicalshipment 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 ServiceMarketplace:
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 theSWDC on SMP and standard delivery (for example, the Software Catalogue). If you
encounter the situation that the required SPS for correct SAP BP packages activationis based on a SPS level LOWER than the current Service Release, the request forthe necessary SPS is handled by a customer message. For details, see SAP Note
925690 Standard Ordering Procedures for SAP Software.
7/25/2019 s Perso Nw731v1
http://slidepdf.com/reader/full/s-perso-nw731v1 11/20
SAP Best Pract ices Quick Guide to Implementing SAP Screen Personas
© SAP AG Page 11 of 20
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 enhancementpackage 1 for SAPNetWeaver 7.3
SP08
Application Server ABAP
Software ComponentVersions:
SAP_ABA 7.31
SAP_BASIS 7.31
SAPenhancementpackage for SAP
ERP
SAP enhancementpackage 6 for SAPERP 6.0 SP08
Central Applications Check SAP Note 774615
SAP ScreenPersonas
SAP ScreenPersonas 2.0SP01
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 SAPSoftware 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.0Central Installation Note 1776739 Release Strategy for the ABAP add-on PERSOS providesdetails 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 asearch 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 forthe ABAP add-on PERSOS.
7/25/2019 s Perso Nw731v1
http://slidepdf.com/reader/full/s-perso-nw731v1 12/20
SAP Best Pract ices Quick Guide to Implementing SAP Screen Personas
© SAP AG Page 12 of 20
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 asearch using the following entries:
Search Term SAP SCREEN PERSONAS 2.0
Search Method Exact Term
Search Area Support Packages and Patches in Maintenance
Search Objects Product Versions
Detailed information on the installation process is available in note 1776739 Release Strategy forthe ABAP add-on PERSOS. Information on the content of SP01 is provided in note 1963129Personas Admin UI Fixes: PERSOS 100 SP3 and PERSOS 200 SP1 .
3.2.2 Microsoft SilverlightTo 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 SAPScreen Personas screen.
3.3 Frontend ComponentsThe 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 tohttp://www.microsoft.com/getsilverlight/get -started/install/default.aspx and choose theSystem Requirements tab.
3.4 SAP Notes and MessagesIf 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 andcorrections for problems that have not become apparent until after shipment.
SAPNote #
Description Component Area Remark
1776739 Release strategy for
the ABAP add-onPERSOS
BC-UPG-
ADDON
Release
planninginformation
Always check the SAPNote of the SAP Best
Practices package for
updates on theimplementation
7/25/2019 s Perso Nw731v1
http://slidepdf.com/reader/full/s-perso-nw731v1 13/20
SAP Best Pract ices Quick Guide to Implementing SAP Screen Personas
© SAP AG Page 13 of 20
1885312 Recommended notesfor SAP Screen
Personas
BC-PER-RT-SIL
Consolidated list ofrecommended notes for
SAP Screen Personas
1848339 Installation andUpgrade note for
Personas
XX-PROJ-CDP-271
Installationinformation
1842360 SAP ScreenPersonas:
Prerequisites for Rel1.0 SP1 & Rel 2.0
Upgrade from SAP ScreenPersonas 1.0 to SAP
Screen Personas 2.0
1885334 Feature list Personas
2.0 SilverlightUpgrade
information
1826286 FAQ/How to Guidefor SAP Screen
Personas
XX-PROJ-CDP-271
Consulting FAQ for commonquestions in SAP Screen
Personas
1888428 SAPGUI for HTML:Sizing
BC-FES-ITS Installationinformation
1884539 Considerations whenusing SAP ScreenPersonas
BC-PER-RT-SIL
Help forerroranalysis
Important considerationsto be taken into accountwhen using SAP Screen
Personas.
1869640 Client copy ofPersonas delivered
Customizing
XX-PROJ-CDP-271
Customizing
1963129 Personas Admin UIFixes: PERSOS 100
SP3 and PERSOS200 SP1
BC-PER-RT-SIL
Programerror
Apply all SAP Notes to the system via the SAP Note Assistant (transaction SNOTE). All SAPNotes 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 usingtransaction SGEN as described in SAP Note 481548.
7/25/2019 s Perso Nw731v1
http://slidepdf.com/reader/full/s-perso-nw731v1 14/20
SAP Best Pract ices Quick Guide to Implementing SAP Screen Personas
© SAP AG Page 14 of 20
4 Evaluate Business Content/ProcessesThe following sections describe the activities that have to be done by the business consultantwho is taking care that the business processes work as desired.
The section System Configuration outlines activities that the administrator can carry outto configure the system for SAP Screen Personas.
The sect ion User Maintenance and Settings outlines the activities that the businessconsultant has to perform to enable system users to exploit the business processdocumentation. It describes the required user settings.
The section Review of Business Processes provides an overview of how a power usercreates a flavor to simplify SAP transactions.
4.1 System ConfigurationInformation 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 SICFTo run SAP Screen Personas in a web browser, the following services must be activated in thetransaction 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:
Transaction Code SICF
SAP Menu Tools
Administration
Administration
Network
HTTPService Hierarchy Maintenance
7/25/2019 s Perso Nw731v1
http://slidepdf.com/reader/full/s-perso-nw731v1 15/20
SAP Best Pract ices Quick Guide to Implementing SAP Screen Personas
© SAP AG Page 15 of 20
2. Navigate to the specified node.
3. Right-click the service.
4. Select Activate Service in the context menu.
5. Choose Activate.
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
Procedure1. Choose one of the following navigation options:
Transaction Code SICF
SAP Menu Tools Administration Administration Network HTTPService Hierarchy Maintenance
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, enter Yes in Compression.
6. Choose Store.
4.1.2 Setup URL HandlerThe 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 is set to Yes.
The following parameters for GUI Configuration in the Service Data tab 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 is selected.
The Handler List in the Handler List tab has the following entry:
No. Handler
1 CL_HTTP_EXT_ITS_BASIC
7/25/2019 s Perso Nw731v1
http://slidepdf.com/reader/full/s-perso-nw731v1 16/20
SAP Best Pract ices Quick Guide to Implementing SAP Screen Personas
© SAP AG Page 16 of 20
4.2 User Maintenance and SettingsThere is no separate user management for SAP Screen Personas. To access SAP ScreenPersonas, users must 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, FlavorManagement and so on.
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 correspondto the activities documented in SAP Screen Personas 2.0 Master Guide.
4.2.1 Maintain Personas RolesYou can maintain roles to be assigned to the business users. It is through these Roles that the UserPermissions are controlled. As a first s tep you must maintain at least an administrator role.
Procedure
1. Choose the following navigation option:
Transaction Code SPRO
IMG Menu Cross-Application Components SAP Screen Personas
Maintain Personas Roles
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 PersonasYou 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 beused in multiple systems.
Procedure
1. Choose the following navigation option:
Transaction Code SPRO
IMG Menu Cross-Application Components SAP Screen Personas Maintain Systems
2. Choose New Entries.
3. Add the following entry:
7/25/2019 s Perso Nw731v1
http://slidepdf.com/reader/full/s-perso-nw731v1 17/20
SAP Best Pract ices Quick Guide to Implementing SAP Screen Personas
© SAP AG Page 17 of 20
Field Name Entry Value
System <System ID>
Client <Client>
Group <Text for Group>
Description <Text for 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://<domain name>:<port>
If you have a system landscape with several servers for load balancing, the urladdress 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 Persona’s Role.
7. Choose Execute.
4.3 Review of Business ProcessesExample steps to create your own simplified screen transferring an SAP GUI application to an
SAP Screen Personas application.
– Open SAP Screen Personas
– Open target system (for example SAP ERP backend)
– Create a flavor as a copy of the Basic View
– Hide unnecessary elements of the screen (for example grids, …)
– Hide unnecessary elements of the SAP Easy Access bar
– Hide unnecessary elements of the SAP menu bar
– Add your customized content
– Design your screen (upload of background picture, arrange buttons and other elements)
– Connect transactions, scripts, and so on to buttons
– Save flavor
7/25/2019 s Perso Nw731v1
http://slidepdf.com/reader/full/s-perso-nw731v1 18/20
SAP Best Pract ices Quick Guide to Implementing SAP Screen Personas
© SAP AG Page 18 of 20
The above steps show an abstract proceeding. The document How to Create Screen PersonasFlavors provides further information on these topics.
The following screen shots show a comparison of example screens for SAP GUI and SAP ScreenPersonas for Personnel Actions (transaction PA40).
Figure 3: SAP GUI screen for Personnel Actions (transaction PA40)
7/25/2019 s Perso Nw731v1
http://slidepdf.com/reader/full/s-perso-nw731v1 19/20
SAP Best Pract ices Quick Guide to Implementing SAP Screen Personas
© SAP AG Page 19 of 20
Figure 4: Example SAP Screen Personas flavor for Personnel Actions (transaction PA40)
7/25/2019 s Perso Nw731v1
http://slidepdf.com/reader/full/s-perso-nw731v1 20/20
SAP Best Pract ices Quick Guide to Implementing SAP Screen Personas
5 Security AspectsThis section provides an overview of the security-relevant information that applies to thedeliverables of this solution package.
5.1 General Security GuidelinesThis 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.