Scribd Logo
Upload

Welcome to Scribd!

  • 4 views

    Complete Guide On How To Choose and Deploy A Fiori App in 5 Steps

    Uploaded by

    18bd1a1006

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    Complete Guide On How To Choose and Deploy A Fiori App in 5 Steps

    Uploaded by

    18bd1a1006
    4 views14 pages

    Original Title

    complete-guide-on-how-to-choose-and-deploy-a-fiori-app-in-5-steps

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    4 views14 pages

    Complete Guide On How To Choose and Deploy A Fiori App in 5 Steps

    Uploaded by

    18bd1a1006

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    of 14

    How to Choose

    and Deploy a
    Fiori App
    CHOOSE AND DEPLOY A FIORI APP
    IN 5 STEPS
    THE COMPLETE GUIDE

    BUSINESS SCENARIO
    You have heard of Fiori but don't
    know where to start?

    You have been asked to simplify the


    user experience at your company to
    save up on training for new and
    existing employees for Field Sales
    Reps?

    ABOUT THIS GUIDE


    This guide will focus on
    the installation of a ‘Create
    Sales Orders’ Transactional
    Fiori App in an ABAP
    environment on ERP 6.0 EHP 7
    running embedded Gateway.

    PREREQUISITES
    Make sure you have installed and
    configured the gateway and all necessary
    SAPUI5 components.
    STEP 1
    FIND A FIORI APP TO SIMPLIFY SALES
    ORDERS CREATION

    Access the SAP Fiori Apps Reference Library* and search


    for ‘Create Sales Orders’ app.

    The Fiori Apps library should be your main starting point


    when implementing a Fiori app. It describes the app features,
    installation information, configuration as well as extension
    points which tell you what features of the standard app can be
    enhanced. If you can’t find a relevant Fiori app, you may
    consider creating a custom one.

    DATABASE - ANY DB
    ‘Any DB’ means we don’t
    need the HANA database.
    If you have ‘HANA’ next to
    'DATABASE' then we either
    need SAP Business Suite on
    HANA or S/4HANA in order
    to install and run the app.

    *SAP Fiori Apps Reference Library: https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/


    STEP 2
    DEPLOY THE FRONT-END COMPONENTS

    Download the Front-End component files

    From the Fiori catalogue* identify the front ends components


    to be installed (Implementation Information/Installation/Front-
    End Components):

    DOWNLOAD
    the above component
    along with all the
    corresponding support
    packages 0001-0010 from the
    SAP Downloads page**.

    INSTALL THE FILES


    Log in to client 000 of your system.
    Run transaction SAINT.Install the downloaded UI
    components.
    **SAP Downloads: https://launchpad.support.sap.com/#/softwarecenter
    STEP 2
    DEPLOY THE FRONT-END COMPONENTS

    ACTIVATE THE SICF FOR APP URL


    Identify name of the app from the Fiori apps library*
    (Implementation Information/Configuration/SAPUI5
    Application).

    Run transaction SICF and use the following path:


    default_host -> sap -> bc -> UI5_UI5 -> sap -> sd_so_cre

    You can see that the service is grey which means inactive.
    Right click it and activate.
    STEP 3
    DEPLOY THE BACK-END COMPONENTS

    Download the Back-End components files

    From the Fiori apps catalogue identify the front ends


    components to be installed (Implementation
    Information/Installation/Back-End Components):

    DOWNLOAD
    the above component along
    with the support packages
    0001 – 0008 from the SAP
    Downloads page**

    INSTALL THE FILES


    Log in to client 000 of your system.
    Run transaction SAINT.
    Install the downloaded Back-End components.

    **SAP Downloads: https://launchpad.support.sap.com/#/softwarecenter


    STEP 3
    DEPLOY THE BACK-END COMPONENTS

    ACTIVATE THE ODATA SERVICE


    Identify the name of the OData Service from the Fiori apps
    catalogue (Implementation Information/Configuration/OData
    Services).

    Run transaction /IWFND/MAINT_SERVICE - Click


    Choose the System Alias and Technical Service Name:

    Select the displayed Backend Service and click on:


    You will get an ‘Add Service’ pop up. Assign a package (I am using
    a local object for test purposes) and press Continue:

    The OData service should now be visible in the Service Catalog of


    transaction /IWFND/MAINT_SERVICE

    *SAP Fiori Apps Reference Library: https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/


    STEP 4
    AUTHORIZATIONS

    SAP provides you with role templates once you install the
    relevant app components. You can either use the existing
    components or take a Z copy of the template. It is up to your
    authorization team and should be adapted to your
    authorization concept.

    Since I am using embedded Gateway the following steps may


    differ if using Gateway Central Hub Deployment where you
    need to take care of authorizations both on the ECC side and
    the Gateway side.

    Create PFCG role with Launchpad Start Authorization

    Copy role SAP_UI2_USER_700 under the Z namespace e.g.


    Z_UI_USER

    Add IWSG authorizations for: ZINTEROP_0001 and


    ZPAGE_BUILDER_PERS_0001

    Click on he ‘Menu’ tab and add


    ‘Authorization Default’
    STEP 4
    AUTHORIZATIONS

    ENTER the following details and save:

    GO TO TAB ‘Authorizations’
    Click on ‘Change Authorization Data’:
    STEP 4
    AUTHORIZATIONS

    CLICK "Manually"
    Add the following
    authorization objects:

    MAKE SURE
    the traffic lights are green by clicking on them:

    GENERATE
    the authorization profile
    and save it:

    ASSIGN the authorization role to the user in the ‘User’


    tab and click on ‘User Comparison’:
    STEP 4
    AUTHORIZATIONS

    CREATE PFCG ROLE


    for Launchpad Catalogues and Groups. Find the business
    role template in the FIORI apps library documentation
    for our SD app.

    Go to transaction PFCG and copy it into the Z namespace


    e.g. ZSAP_SD_BCR_FIELDSALESREP_X1

    In our new role we can see that the following elements


    have been copied:

    Which give users access to the tile catalogue and tile


    group in the Fiori Launchpad.

    GENERATE A PROFILE
    and assign to the user like described earlier within
    "Create PFCG role"
    STEP 4
    AUTHORIZATIONS

    CREATE PFCG role to access oData services


    --> Copy roles SAP_SD_SO_CRE_APP under Z namespace e.g.
    ZSAP_SD_SO_CRE_APP
    --> Add IWSG authorizations for:
    ZSRA017_SALESORDER_CREATE_SRV_0001
    --> Go to the ‘Menu’ tab and click on add ‘Authorization Default’
    and enter the following details:

    Save the role menu and you should see the following:

    Generate the profile and assign to the user.

    NOTE:
    In backend the user must have authorization to RFC trusted
    connection if you have a central hub gateway.
    To check for authorisation issues to the backend use transaction:
    IWFND/ERROR_LOG
    STEP 5
    TEST THE APP

    The natural environment as an entry point for Fiori apps is the


    Fiori Launchpad which is a container for all your Fiori apps and
    it should be used in the production environment. After the
    installation you may want to test if the app is working correctly
    and test it in the standalone mode before creating a Fiori
    Launchpad.

    Click on he ‘Menu’ tab and add ‘Authorization Default’In order to run


    the app in a standalone mode you need to use the following link
    format:

    <Server and Port>: This is your server name & port your app will be
    running on.
    <Component Name>: To get the name run the following link:
    http://<server>:<port>/sap/bc/ui5_ui5/sap/sd_so_cre/Component.js

    <Shell URL>: This is the URL pointing to the app resource file location
    on the server: /sap/bc/ui5_ui5/sap/sd_so_cre

    The full link will look as follows:


    NOW YOU SHOULD NOW BE ABLE TO TEST YOUR APP
    IN THE STANDALONE MODE!

    ABOUT ABSOFT
    Absoft, SAP Partner and SAP Value-Added Re-
    Seller (VAR), has been specialising in SAP® since
    1991, uniquely combining business process and
    SAP expertise to deliver best practice solutions
    in implementation, development and support of
    SAP solutions.

    In their words, our clients value our “flexibility, willingness to go the extra
    mile, full transparency, being proactive in suggesting and providing the
    right solution, not just overhead”. Eighty percent of our business is from
    repeat customers.

    You might also like