This blog is for portal content administrators who would like to learn about the setup tasks required to enable SAP Fiori Launchpad (FLP) on SAP Enterprise Portal for BI Portal scenario.

 

BI end users can run the SAP BI reports leveraging the portal configuration in a modern, multi-channel, personalized FLP user experience, after the steps below are performed by the portal administrator (for more information about the end-user experience, click here).

 

Additionally, the UI theme designer allows you to develop your company’s own themes by modifying one of the
theme templates provided by SAP.

 

Prerequisites:

Use of NW 7.31 SP15 or higher*); NW 7.4 SP10 or higher*).

*) The Fiori Launchpad  on EP functionality with reduced scope is available from NW 7.31 SP12 and NW 7.4 SP7.

 

 

Overview of Steps:

 

  1. Enabling the SAP Fiori Launchpad on Portal
  2. Reusing the existing portal content (roles, pages and iViews) to provide mobile and desktop access to the BI reports via FLP on EP. Every existing iView or page, containing several iViews, will appear on a launcher as a tile. You change/add the following :
    • Role/folder properties
    • iView properties
  3. (Optional) Using the UI theme designer for new theming and branding.

Detailed Steps:

 

  1. Enable SAP Fiori Launchpad on Portal (detailed steps). Note:
    • The categories will reflect the tile grouping in the tile catalog
    • Each iView can be assigned to one category (see the iView properties table below)
    • End user’s home page will be empty when opened for the first time unless you mark an iView as default

   2. If a role contains iViews directly, the following role properties must be set:

    • Select the Entry Point checkbox
    • Set Mobile Perspective to “Launcher”

LauncherParam.png
3. If the role configuration contains iViews separated in folders as shown below:

RoleFolder.png

 

The following folder properties should be set:

    • Select the Entry Point checkbox
    • Set Mobile Perspective to “Launcher”

  4.  The most important iView properties are listed below. For other relevant properties see Example 1 and here.

– Object ID of Device Group Example: TabletAndroid;TabletWin8;com.sap.portal.dg.desktop

This property, together with the Mobile Perspective property of a role or a folder controls an iView’s mobile enablement:

    • If a report has to run on a mobile device, Object ID of Device Group must contain at least one mobile object in addition to the “Mobile Perspective” setting (see Example 2)
    • If a report BI technology is not supported on mobile devices, it can be excluded by setting Object ID of Device Group to desktop devices only

– Default App in Home Page will always show the tile on user’s home page.

 

  5. To provide company theming and branding use SAP Fiori Launchpad Theming  (see example 4).
Example 1:
You want to enable an existing BEx report on FLP on EP with the following requirements:

 

  • The report is available only on desktop
  • The report is opened in Portal Content Area

 

BEx iView properties should be updated as below:

BexProperty1.PNG

Note: in the iView property Application Parameters you have to concatenate to a default value “sap-ie = EmulateIE8” a string “&theme = sap_tradeshow”.
BexProperty2.PNG

BexProperty3.PNG

Example 2:
You want to show the same data as in Example 1 on a mobile device. To do this, you create a new
Design Studio report and an iView with the following properties:

DSProperty1.PNG

DSProperty2.PNG

Example 3:

 

You transform your traditional portal  like on the picture below

OldPortal.PNG

Into FLP:

HomePageCloud.PNG

 

Tile catalog for the above home page looks like this:
TileCatalogCloudDemo.PNG

The category names correspond to the top navigation bar of a classic Portal experience. The groups might be smaller than categories and represent the lower hierarchy levels. You can run a report clicking on any tile or using a quick launch:
QP.PNG
The report displayed in Portal Content Area looks as below:

QuarteRevenueBuildIn.PNG

 

Example 4:

 

After using theme designer your home page might look like this:
themeWithoutCSS.PNG

 

Checking Your Work

 

After completing the procedure above, check the results by following these steps:

1. Open the FLP on EP link http://<domain>:<port>/irj/portal/flp on desktop. The tiles available for desktop and marked as “Default App in Home Page” are displayed in the Home page under the default groups (identical to the categories in tile catalog). Further personalization will be done by end-users as following:

    • Go to Tile Catalog. All the tiles appear under provided categories
    • Most of the often used tiles are usually added to Home page. For this choose a tile, click on it, create a group, and assign a tile to it.

  2.  Click the tile to open the corresponding BI report.

3. Open FLP on EP link http://<domain>:<port>/irj/portal/flp on mobile device. Verify that only mobile-enabled tiles are visible.

 

 

About Portal-BI Integration:

 

  1. BEx /WAD – EP Integration.
  2. Design Studio – EP integration  MANDATORY:To enable your application users to launch the analysis application iViews in the portal, you must configure the security zone NetWeaver.DesignStudio.
  3. Design Studio Admin Guide for NetWeaver
  4. BObj – EP integration, How-to install PIK for BI integration

 

To learn more about  FLP:

 

To report this post you need to login first.

4 Comments

You must be Logged on to comment or reply to a post.

  1. SP S

    If the role configuration contains an iView separated in a multiple folder levels then what configuration should be followed?

    (0) 
    1. Irena Kull Post author

      It is required to have one of the folders in the hierarchy with the following properties:

      • entry point = checked-in
      • visibility = checked-in
      • mobile perspective = Launcher.
      (0) 
      1. SP S

        Thanks Irena for the reply. I have the following questions.

        iView is separated by 3 folder levels. I tried the configurations suggested by you. I am able to see the iView directly in FLP without the folder structure. But my requirement is to get the iView structure in FLP same as in PCD i.e within the folder levels.

        There are multiple iViews in the same folder. So I would like to see the Folder in FLP so that if the user clicks on folder , it should navigate to next folder level and so on… till the user gets the iView.

        (0) 
        1. Irena Kull Post author

          Unfortunately folders are not relevant for FLP runtime, they are used only as a groupping of iViews visualized together. We have another hierarchy, namely categories (appear in Tile Catalog) and groups (in Home page). Groups by default can have category names or you can create them manually.

          Also you can use different searches and Quick Launcher to find and start your app.

          As you see, the navigation logic is different and is not inherited automatically. But our pilots with customers show that their everyday working tasks can be very well mapped to FLP environment: in a different way, with its own advantages.

          (0) 

Leave a Reply