How-to Guide for Exercise – Familiarize Yourself with SAP Fiori UX (Week 1, Unit 6, Part 2)

Table of Contents Introduction ...................................................................................................................................................... 2 Connect to the openSAP instance ................................................................................................................. 3 Login to the SAPgui ........................................................................................................................................ 5 Disable Internet Explorer Enhanced Security Configuration .................................................................... 16 Login to the SAP fiori launchpad and the SAP fiori launchpad designer ............................................... 18

INTRODUCTION The goal of this exercise is to log you into the systems we will be using in subsequent weeks throughout this course. We want to make sure you know how to log in and what each of the different areas is used for when implementing and configuring SAP Fiori UX apps. First, you will log into the SAP GUI. For the purposes of the openSAP Introduction to SAP Fiori UX exercises we are using an embedded deployment option so you will only have one system to log into. From a timing perspective and efficiency in utilizing an existing SAP Fiori UX instance this was the best choice. However, if you deploy SAP Fiori UX in your own landscape we do recommend and encourage you to implement the central hub deployment option. After you log in you will enter the transactions you will be learning about over the next 6 weeks and adding them to your favorites list. This will make future exercises where we access these transactions convenient. While the transactions will be explained briefly in this exercise and in the forthcoming weeks we will not be doing any configurations or hands-on steps in this exercise. However, if you would like to look at the various transactions for a feel of what they do that is acceptable, just do not change anything at this point. The next thing you will do is log into the SAP Fiori launchpad (runtime) and the SAP Fiori launchpad Designer (design time). Again, we will not be configuring anything in this exercise but instead you have the freedom to navigate through both so that when we do the hands on part in week 3 you’re already familiar with the layout. This exercise should take only a half hour, unless you choose to spend additional time exploring.

2

CONNECT TO THE OPENSAP INSTANCE Note: If you kept the instance up and running from the part 1 exercise then you can skip to page 5 ‚Login to the SAP GUI‘. If you suspended the instance start with the steps immediately below. If you terminated your instance please reference the part 1 guide page 28: Creating the openSAP Instance.

1. Go to www.cal.sap.com and choose login from the upper right hand corner

2. Enter the login credentails you established in the previous exercise and choose ‚Log On‘

3. On the instances tab find the instance titled ‘openSAP Fiori Appliance for Learners Landscape [Trial Edition], on the Operations tab choose ‘Connect’

3

4. In the Connect to the Instance popup choose ‚Remote Desktop (SAP Frontend)

5. Open the downloaded remote desktop Note: SAP Employees need to be off the corporate network to use this remote desktop

6. Choose ‚Connect‘

7. Enter with user: Administrator and Password: Fiori2014 and choose ‚OK‘

4

8. Choose ‚Yes;

You are now logged into the remote desktop connection.

LOGIN TO THE SAP GUI

1. Open the SAP GUI by double clicking the ‘SAP Logon’ icon from your desktop

2. Double click the ‘openSAP for Fiori SAP System’

3. Enter the following logon credentials: Note: It is important to change the client! It is defaulted to 001 but needs to be manually changed to 120. If you do not change this you will receive a username/password error when you try to login.

5

Client: 120 Username: Bpinst Password: Welcome1

Hit enter from your keyboard

4. From the top menu bar choose System Status

5. Take notice of the SAP System data and the Database Data, and then choose the magnifying glass icon.

6

6. This shows you a detailed list of all the installed software components. Review this list, especially the SAP Gateway Foundation (SAP_GWFND) and User Interface Technology (SAP_UI). In week 2 Prakalp Phadnis will discuss these components with you in more detail. When you’re finished choose the ‘X’ to close out.

7

7. Close the system status popup

8. As we move through this course you will be introduced to a number of transactions you will need to use in order to successful implement and configure SAP Fiori UX. To make future navigation easier in this next step we will add the most frequently used transactions to your favorites list. By default there are already transactions in your favorites list so we will create a new folder for the transactions we will be using. Note: This step is optional as we will always tell you which transactions to go to in our guides Right click on ‘Favorites’ and choose ‘Insert Folder’

8

9. Name the folder ‘openSAP Fiori UX’ and choose the green checkmark

10. Right click on the folder you just created and choose ‘Insert Transaction’

11. In the Manual entry of a transaction popup enter: SAINT (Add-On Installation Tool) and choose the green check box

a. Transaction SAINT simplifies the installation and upgrade of add-ons, and preconfigured systems.

12. The following is a list of transactions we will discuss throughout this course. Some of these transactions may not be familiar to you at this point, however, throughout the next 6 weeks one of the instructors will discuss each one with you and detail how it relates to SAP Fiori UX. Add the following transactions to the openSAP Fiori UX folder in the same manner as described in the step 11.

a. SPAM (Support Package Manager) i. This transaction provides you with an easy and effective way of improving SAP

Support Packages into your system.

9

b. /IWFND/MAINT_SERVICE (Activate and Maintain Services) i. In this transaction you activate your services

c. SICF (HTTP Service Hierarchy Maintenance) i. This transaction brings you to a report that is used to maintain HTTP services for

HTTP communication in the SAP system using the Internet Communication Manager (ICM) and the Internet Communication Framework (ICF)

d. PFCG (Role Maintenance) i. This transaction allows you to create and maintain roles.

e. SM59 (RFC Destinations) i. Transaction to create and maintain RFC destinations

f. SU01(User Maintenance) i. Transaction where SAP users can be created. In addition users can be copied to

another user; users can be modified, deleted, locked or unlocked etc. g. LPD_CUST (Launchpad Customizing)

i. In this transaction you create and configure a launchpad and its applications. Activities that can be completed within this transaction include, creating new and editing existing launchpads, adding applications to launchpads and configuring those applications, specifying parameters, copying launchpads and performing searches in a launchpad.

h. SE80 (Object Manager/ABAP Workbench) i. This transaction takes you to a collection of tools used to develop, test and run

ABAP programs. i. /UI5/THEME_DESIGNER (UI Theme Designer)

i. Transaction that takes you out of the SAP GUI and into the SAP theme designer tool j. SE11 (ABAP dictionary maintenance)

i. This transaction is an ABAP dictionary where you can create, change and display table entries and structures.

k. SEGW (gateway service builder) i. This transaction is a design-time environment that provides developers with an

easy-to-use set of tools for creating services.

When you’re finished your favorites should now look as follows:

10

UPDATE PASSWORD FOR SECONDARY DATABASE CONNECTION You must perform the following steps; otherwise SAP<SID> HDB schema user (in this case SAPERP) will get locked.

1. In SAP ERP Easy Entry, call transaction DBCO.

2. Choose the “change” button

3. Update the Username & password w/ the master password you defined during instance creation in SAP CAL (either your own password or Fiori2014). The password needs to be entered twice.

11

4. Save your entries

CONNECTION TO HANA VIA SAP HANA STUDIO In case you encounter problems because the user already has been locked, please perform the following steps. Only do this section if your database user is locked. Otherwise, go to the next section.

1. Double click the SAP Dev Tools for Eclipse icon located on your desktop. This will launch the SAP

HANA Studio. Logon to your HANA system using HANA Use the SYSTEM user and the MASTER PASSWORD you have set for your instance.

12

2. You may receive a popup for Secure Storage, choose ‘Yes’

13

3. Enter 2 security questions and answers (whatever questions you choose are ok), then choose ‘OK’

4. Right click on HDB (SYSTEM) on the left hand side in the Systems Tab, then choose ‘Log On’

5. Enter the Master password we have set for the system. (Either your own password or the suggested Fiori2014), then choose ‘OK’.

14

6. In the Systems navigation pane you should have 5 folders (Backup, Catalog, Content, Provisioning and Security). Expand the Security folder expand the Users folder Double click on SAPERP user

15

7. Enter and Confirm a new password, then choose the Activate button Note: Your user may already be activated, if it is when you hover over the activate button it will say deactivate. If this is the case then you can move onto the next step.

DISABLE INTERNET EXPLORER ENHANCED SECURITY CONFIGURATION In order to avoid the ‚Add exception‘ popup every time you access a website, please follow the steps below to turn off the IE ESC.

1. Go to the Desktop of your RDP session and double click the Server Manager icon

2. Choose the top node of the server by clicking on it

16

3. In the menu on the right hand side, find the link to ‘Configure IE ESC’ and click on it

4. In the Internet Explorer Enhanced Security Configuration popup choose the off radio button for both Administrators and Users. When you’re finished choose ‘OK’

17

5. Close out of Server Manager by choosing the ‚X‘

LOGIN TO THE SAP FIORI LAUNCHPAD AND THE SAP FIORI LAUNCHPAD DESIGNER

1. Open the Internet Explorer browser (Start – All Programs – Internet Explorer) and launch the SAP

Fiori Launchpad using the URL below: http://vhcalhdbdb.dummy.nodomain:50000/sap/bc/ui5_ui5/ui2/ushell/shells/abap/fiorilaunchpad.html?sap-client=120&sap-language=EN

2. Enter the following login credentials User: Bpinst Password: Welcome1Bpinst Choose ‘Log On’

18

3. Once you’re logged into the launchpad feel free to look around. Examples of what you could explore:

1. Open a tile 2. Open the catalog 3. Search

You can also reference the following SAP help guide to read about the SAP Fiori launchpad and it’s features and capabilities http://help.sap.com/saphelp_uiaddon10/helpdata/en/f9/51b50a07ce41deb08ced62711fe8b5/content.htm?frameset=/en/f9/51b50a07ce41deb08ced62711fe8b5/frameset.htm&current_toc=/en/e4/843b8c3d05411c83f58033bac7f072/plain.htm&node_id=37&show_children=true#jump37

1

2 3

19

4. Open another tab and launch the SAP Fiori Launchpad Designer

http://vhcalhdbdb.dummy.nodomain:50000/sap/bc/ui5_ui5/sap/arsrvc_upb_admn/main.html?sap-client=120&sap-language=EN

5. You should be automatically logged in since we’re logged into the SAP Fiori launchpad. If you’re not logged in enter username: Bpinst and password:Welcome1

6. Have a look around the launchpad designer. The designer is used by admins and is the design time

for the launchpads. Here admins create groups, catalogs, target mapping, design tiles etc. Examples of what you could explore:

1. Look at catalogs 2. Look at groups 3. Open a target mapping tile and see what information is required 4. Open an app launcher tile (static, dynamic, news tile) and see what information is required

Congratulations! You have completed Week 1, Unit 6, Exercise Part 2 - Familiarize yourself with SAP Fiori UX. Next week you will learn more about the tasks involved in installing SAP Fiori UX.

1 2

3 4

20

www.sap.com

© 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://www.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 SE’s 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.