launchpad configuration

Download Launchpad Configuration

Post on 09-Oct-2015

519 views

Category:

Documents

4 download

Embed Size (px)

DESCRIPTION

SAP Fiori

TRANSCRIPT

  • SAP Fiori Launchpad configuration

    Fiori 2

  • 2013 SAP AG or an SAP affiliate company. All rights reserved. 2

    Agenda

    Concept overview

    Prerequisites

    Preparation steps

    Initial configuration

    Maintaining SAP Gateway OData Services

    Configuring ICF Nodes

    Transport request

    Configuration steps

    Register a new LPD with the LPD_CUST Transaction on the Gateway

    Create a new catalog in Launchpad designer

    Add tiles to the catalog: Target mapping and Static, Dynamic or News tiles

    Create a group and add tiles from existing catalogs

    Create a new role with the PFCG Transaction

    Adjusting the Visual Appearance of the Launchpad

    Testing the Launchpad

  • 2013 SAP AG or an SAP affiliate company. All rights reserved. 3

    Concept overview

    LPD_CUST Transaction

    Launchpad designer

    Catalogs Groups

    Target

    Mapping Static Tile

    Dynamic Tile News Tile

    Static

    Tile

    Dynami

    c Tile

    News

    Tile

    1

    2

    3

    4

    PFCG Transaction 5

    Sequence of steps for TRANSACTIONAL apps:

    1. Register a new LPD with the LPD_CUST

    transaction on the SAP NW Gateway and add

    the desired BSP apps to it.

    2. Create a new catalog in Launchpad designer

    3. Add tiles to the catalog: two types are required

    Target mapping (mandatory)

    Static, Dynamic or News

    4. Create a group and add tiles to it by taking

    already created Static, dynamic or News tiles

    from defined catalogs.

    5. Create a new role with the PFCG Transaction

    and assign the created catalog and/or group to

    it. Then assign the role to the users.

  • 2013 SAP AG or an SAP affiliate company. All rights reserved. 4

    Concept overview 1

    2

    3

    4

    5

    Sequence of steps for TRANSACTIONAL apps:

    1. Register a new LPD with the LPD_CUST

    transaction on the SAP NW Gateway and add

    the desired BSP apps to it.

    2. Create a new catalog in Launchpad designer

    3. Add tiles to the catalog: two types are required

    Target mapping (mandatory)

    Static, Dynamic or News

    4. Create a group and add tiles to it by taking

    already created Static, dynamic or News tiles

    from defined catalogs.

    5. Create a new role with the PFCG Transaction

    and assign the created catalog and/or group to

    it. Then assign the role to the users.

  • 2013 SAP AG or an SAP affiliate company. All rights reserved. 5

    Concept overview

    Catalog

    Group

    PFCG

    Role

    Provides users

    access to the

    apps in groups

    and catalogs.

    Set of apps you

    want to make

    available for one

    role

    Subset of

    catalog that

    contains the

    apps visible on

    the Fiori

    Launchpad

    entry page

  • 2013 SAP AG or an SAP affiliate company. All rights reserved. 6

    Concept overview

    Theres a distinction between Business Catalogs and Technical Catalogs (with corresponding roles)

    Business

    Catalog

    Business

    Catalog

    Group

    Apps

    relevant for a

    business role

    in a certain

    area (like

    SD, CRM,)

    Technical

    Catalog

    Apps

    relevant for

    a certain

    area (like

    SD,

    CRM,)

    Technical

    PFCG Role

    Business

    PFCG Role

  • 2013 SAP AG or an SAP affiliate company. All rights reserved. 7

    Material Management Apps

    Concept overview

    Example (1/2)

    SAP Fiori has several apps and corresponding roles for Materials Management

    Goods

    Issue

    Material Purchase

    Order

    Purchase

    Contract

    Technical Role : SAP_MM_TCR_T

    Business Role :

    SAP_MM_BCR_INVENTORYMGR

    Business Role :

    SAP_MM_BCR_BUYER

  • 2013 SAP AG or an SAP affiliate company. All rights reserved. 8

    Material Management Apps Material Management Apps

    Concept overview

    Example (2/2)

    Each user will have access to the apps based on the roles assigned to him

    Goods

    Issue

    Material Purchase

    Order

    Purchase

    Contract

    Technical Role : SAP_MM_TCR_T

    Business Role :

    SAP_MM_BCR_INVENTORYMGR

    Business Role :

    SAP_MM_BCR_BUYER

    Technical Role : SAP_MM_TCR_T

    Inventory Manager Buyer

  • Prerequisites

  • 2013 SAP AG or an SAP affiliate company. All rights reserved. 10

    Prerequisite 1 (1/3)

    Fiori App with properly implemented navigation

    You have implemented a Fiori application you want to integrate into the Fiori

    Launchpad.

    Be sure, that this application has taken into consideration the Intent-based navigation

    The Launchpad uses an intent-based navigation paradigm. This means that a source application can navigate to a target, by specifying an intent using the hash fragment of a

    standard URL

  • 2013 SAP AG or an SAP affiliate company. All rights reserved. 11

    Prerequisite 1 (2/3)

    A schematic illustration of navigation steps and URLs could be as follows:

    1 Load App 1 (View 1 is default) http://://shell.html#app1

    2 Inner-App Navig. to View 2 http://://shell.html#app1&/view2

    3 App-to-app Navigation to App 2 http://://shell.html#app2

    4 Back Navigation (Browser) http://://shell.html#app1&/view2

  • 2013 SAP AG or an SAP affiliate company. All rights reserved. 12

    Prerequisite 1 (3/3)

    Intent based navigation concept

    The Launchpad enables you to specify that the same application is launched in different views or modes

    depending on the end user's role. Each application within the Launchpad has a resource locator (URL) by

    which it can be loaded. Instead of directly encoding the (technical) name of the target application into the

    URL hash, the Launchpad performs an indirection by so-called intents. An intent is a mechanism that allows

    users to perform actions on semantic objects (such as navigating to a sales order or displaying a fact sheet),

    without worrying about the UI technology or technical implementation of the navigation target.

    Intents have the following pattern:

    #-?=

    Example:

    The intent #SalesOrder-displayFactSheet?SalesOrder=27 specifies that a fact sheet for the sales order no.27 is launched.

    The intent-based fragment identifier #SalesOrder-displayFactSheet?SalesOrder=27 may be resolved to the following URL:

    https://:/sap/bc/ui5_ui5/ShowEmployeeSalesOrders.html?id=27

    However, the URL of the Launchpad hides the actual URL under an intent-based URL.

    For example:

    https://:/sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html#SalesOrder-

    displayFactSheet?SalesOrder=27

    The same intent can be resolved differently based on the role of the user that triggers the navigation.

    For example, you may want to define that a manager can display a different version of an employee fact sheet than regular

    employees. Thus, for managers the intent #factsheet-display should resolve to view1 of your application, while for regular

    employees it should resolve to view2.

  • 2013 SAP AG or an SAP affiliate company. All rights reserved. 13

    Prerequisite 2 (1/3)

    Fiori App is based on UI5 components and runs in the Launchpad

    Apps must provide a base path of the BSP application and a root component:

    To get the base path of the BSP application:

    Go to transaction SICF on the Gateway system

    Put as Service Name, the name of your UI5 app (i.e. sd_myquotes) and click Execute

    Double click on the found ICF node (can be two, take the one under ui5_ui5 )

    In shown path 'default_host/sap/bc/ui5_ui5/sap/' + , skip the

    "/default_host (i.e. take just '/sap/bc/ui5_ui5/sap/sd_myquotes)

    To get the root component of your app:

    Go to transaction SE80 on the Gateway system

    In the BSP Application, search for the name of your app (i.e. sd_myquotes).

    Open the Page Fragments/Component.js file and check the first line:

    jQuery.sap.declare("cus.sd.myquotations.Component");

    The string in bold is the root component of your app

  • 2013 SAP AG or an SAP affiliate company. All rights reserved. 14

    Prerequisite 2 (2/3)

    To get the base path of the BSP application:

    Go to transaction SICF on the Gateway system

    Put as Service Name, the name of your UI5 app (i.e. sd_myquotes) and click Execute

    Double click on the found ICF node (can be two, take the one under ui5_ui5 )

    In shown path 'default_host/sap/bc/ui5_ui5/sap/' + , skip the

    "/default_host (i.e. take just '/sap/bc/ui5_ui5/sap/sd_myquotes)

  • 2013 SAP AG or an SAP affiliate company. All rights reserved. 15

    Prerequisite 2 (3/3)

    To get the root component of your app:

    Go to transaction SE80 on the Gateway system

    In the BSP Application, search for the name of your app (i.e. sd_myquotes).

    Open the Page Fragments/Component.js file and

    check the first line:

    jQuery.sap.declare("cus.sd.m

    yquotations.Component");

    The string in bold is the root component

    of your app

  • 2013 SAP AG or an SAP affiliate company. All rights reserved. 16

    Prerequisite 3

    User and authorization in the Gateway System

    User in client of your software component

    Authorization to crea