Perso Nw731v1 Quickguide

  • Published on
    03-Sep-2015

  • View
    216

  • Download
    3

Embed Size (px)

DESCRIPTION

SAP Screen Personas 3.0 RDS Guide

Transcript

<ul><li><p>SAP NetWeaver 7.31 </p><p>October 2014 </p><p>English </p><p>Quick Guide to Implementing SAP Screen Personas rapid-deployment solution V1 </p><p>SAP SE Dietmar-Hopp-Allee 16 69190 Walldorf Germany </p></li><li><p>SAP Best Practices Quick Guide to Implementing SAP Screen Personas rapid deployment solution </p><p> SAP SE Page 2 of 18 </p><p>Copyright </p><p> 2014 SAP SE or an SAP affiliate company. All rights reserved. </p><p>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. </p><p>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. </p><p>Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. </p><p>National product specifications may vary. </p><p>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. </p><p>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. </p>http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark</li><li><p>SAP Best Practices Quick Guide to Implementing SAP Screen Personas rapid deployment solution </p><p> SAP SE Page 3 of 18 </p><p>Icons </p><p>Icon Meaning </p><p> Caution </p><p>Example </p><p> Note </p><p> Recommendation </p><p>Syntax </p><p>Typographic Conventions </p><p>Type Style Description </p><p>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. </p><p>Cross-references to other documentation. </p><p>Example text Emphasized words or phrases in body text, titles of graphics and tables. </p><p>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. </p><p>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. </p><p>EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the </p><p>ENTER key. </p><p>Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. </p><p> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries. </p></li><li><p>SAP Best Practices Quick Guide to Implementing SAP Screen Personas rapid deployment solution </p><p> SAP SE Page 4 of 18 </p><p>Contents </p><p>1 Purpose ................................................................................................................. 6 </p><p>1.1 Basic Concept of SAP Screen Personas .............................................................. 6 </p><p>1.2 Architecture ........................................................................................................... 7 </p><p>2 Solution Overview .................................................................................................. 8 </p><p>3 System Setup &amp; Preparation ................................................................................. 9 </p><p>3.1 Release and Support Package Level .................................................................... 9 </p><p>3.2 Required Product Versions and Software Components ...................................... 10 </p><p>3.2.1 SAP Screen Personas V2.0 .................................................................................. 10 </p><p>3.2.2 Microsoft Silverlight ............................................................................................... 11 </p><p>3.3 Frontend Components ......................................................................................... 11 </p><p>3.4 SAP Notes and Messages................................................................................... 11 </p><p>4 Evaluate Business Content/Processes ............................................................... 12 </p><p>4.1 System Configuration .......................................................................................... 13 </p><p>4.1.1 Activate Services in SICF ..................................................................................... 13 </p><p>4.1.2 Setup URL Handler ............................................................................................... 14 </p><p>4.2 User Maintenance and Settings .......................................................................... 14 </p><p>4.2.1 Maintain Personas Roles ...................................................................................... 15 </p><p>4.2.2 Maintain System Details for Personas .................................................................. 15 </p><p>4.2.3 Assign Administrator Role to User ........................................................................ 16 </p><p>4.3 Review of Business Processes ........................................................................... 16 </p><p>5 Security Aspects .................................................................................................. 18 </p><p>5.1 General Security Guidelines ................................................................................ 18 </p></li><li><p>SAP Best Practices Quick Guide to Implementing SAP Screen Personas rapid deployment solution </p><p> SAP SE Page 5 of 18 </p><p>Table of Figures </p><p>Figure 1: SAP Screen Personas Architecture (Minimal) ................................................................. 7 </p><p>Figure 2: SAP Screen Personas Architecture (Productive) ............................................................. 8 </p><p>Figure 3: SAP GUI Screen for Personnel Actions (Transaction PA40) ......................................... 17 </p><p>Figure 4: Example SAP Screen Personas Flavor for Personnel Actions (Transaction PA40) ...... 17 </p></li><li><p>SAP Best Practices Quick Guide to Implementing SAP Screen Personas rapid deployment solution </p><p> SAP SE Page 6 of 18 </p><p>Quick Guide to Implementing SAP Screen Personas rapid deployment solution V1.731 </p><p>1 Purpose This quick guide provides step by step information on how you must implement the complete solution package. </p><p>Before proceeding with this document, the following activities must be completed: </p><p> You have to define the scope relevant for your project. </p><p> You have to finalize the technical prerequisites </p><p> You have to staff and make available the required resources. </p><p>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. </p><p>This document is intended for the following project roles, which already have a sound knowledge of SAP Best Practices, including tools and documentation: </p><p> System administrators and basis consultants: System set-up and preparation including troubleshooting. </p><p> Activation/implementation consultants (basis or application consultants): Activation/implementation of business content and processes. </p><p> Business consultants: Evaluate business content/processes including troubleshooting, FAQ, and further information for extended usage of the package. </p><p>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. </p><p>With these personalized flavors of SAP Screen Personas, you have the following advantages: </p><p> 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, </p><p> Increase user satisfaction by automating repetitive tasks and simplifying complex screens through pre-filled fields and pull-down menus, </p><p> Reduce the cost of personalization by eliminating the need for ABAP programmers or scripting experts, </p><p> Decrease training time for SAP users. </p><p>SAP Screen Personas 2.0 has two components: </p><p> SAP Screen Personas based on Silverlight </p><p> SAP Screen Personas based on HTML </p><p>This solution only covers the component SAP Screen Personas based on Silverlight. This is because of the functionality that is available in this component. </p>http://service.sap.com/solutionpackages</li><li><p>SAP Best Practices Quick Guide to Implementing SAP Screen Personas rapid deployment solution </p><p> SAP SE Page 7 of 18 </p><p>In this solution all references to SAP Screen Personas (or simply Personas) refer to the component SAP Screen Personas based on Silverlight. </p><p>1.2 Architecture The architecture of SAP Screen Personas and its integration into the SAP environment is displayed in the following pictures. </p><p>There are two types of system landscape for SAP Screen Personas. </p><p>Single System Landscape (Minimal System Landscape) </p><p>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. </p><p>Figure 1: SAP Screen Personas Architecture (Minimal) </p><p>Multiple System Landscape (Productive System Landscape) </p><p>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. </p><p>Alternatively, the SAP Personas add-on can be installed separately on each server in your landscape. </p></li><li><p>SAP Best Practices Quick Guide to Implementing SAP Screen Personas rapid deployment solution </p><p> SAP SE Page 8 of 18 </p><p>Figure 2: SAP Screen Personas Architecture (Productive) </p><p> 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. </p><p>2 Solution Overview SAP Screen Personas rapid-deployment solution V1.731 has the following features: </p><p> It is based on SAP NetWeaver 7.31. </p><p> It provides guidance on implementing and using SAP Screen Personas V2.0 SP01 or higher. </p><p> It provides an accelerated deployment of the required configuration settings. </p><p> It provides documentation on how to configure SAP GUI interfaces using SAP Screen Personas to tailor transactions to your organizations requirements. </p><p>This solution provides guidance on best practices for designing and developing user experiences using SAP Screen Personas. </p><p>The solution provides the following documentation: </p><p>Document Title Purpose </p><p>Quick Guide to Implementing the SAP Screen Personas V1.731 </p><p>Guidance on implementing, configuring, and using SAP Screen Personas V2.0 </p><p>Software Requirements </p><p>How-To-Guide Instruction to create SAP Screen Personas Flavor corresponding to an SAP GUI application (transaction) </p><p>Solution Details </p></li><li><p>SAP Best Practices Quick Guide to Implementing SAP Screen Personas rapid deployment solution </p><p> SAP SE Page 9 of 18 </p><p>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. </p><p>3 System Setup &amp; 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. </p><p>Additionally, the SAP Notes named in the SAP Notes and Messages section in this guide must be implemented. </p><p>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. </p><p>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. </p><p>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. </p><p>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. </p><p>Receiving the Software at the Correct SP Level </p><p>For delivery of the software, a...</p></li></ul>