Show TOC

 App Implementation: Delayed Freight Orders In Transit

System Landscape Requirements

Before you can start to implement the app, ensure that your system landscape has been set up to enable SAP Fiori and that this system landscape already includes the front-end components and back-end components for your app:

SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with SAP HANA XS

Configuration of Front-End Server

not applicable

Back-End Components (Product Version Stack)

SAP Event Management 9.2 SPS 1

SAP HANA Content Component Delivered with (Product Version Stack)

SAP Smart Business 1.0 for SAP Event Management and SAP Transportation Management cross-analytics SPS 2

(Technical name: SAP SMART BUSINESS FOR EMX 1.0)

Instance: HANA Content TMEM Cross

Software Component Version: HANA Live Content Reuse for TMEM 100

(Technical name: HCO_HBA_R_TMEM 100)

VDM Contained (Product Version Stack)

Product Version: SAP HANA Live 1.0 for Event Management and Transportation Management cross-analytics SPS 2

(Technical name: SAP HANA ANALYTICS F. EMX 1.0)

Front-End Components Delivered with (Product Version Stack)

not applicable

For more information about the installation of the front-end components, see Installation Requirements (Analytical Apps).

Tile Type for Launching App

The Delayed Freight Orders In Transit analytical app is launched using a KPI tile.

Required SAP Notes

For the Delayed Freight Orders In Transit app, the following SAP Notes must be implemented:

Back-End/Front-End Server

SAP Note Number





Implementation Tasks

The following sections list tasks that have to be performed to implement the Delayed Freight Orders In Transit app. The tables contain the app-specific data required for these tasks.

You can find the data required to perform these tasks in the SAP Fiori apps library at published on SAP site.

HANA Server: Assign SAP HANA Roles to Users and Roles

You can find the data required to perform this step in the SAP Fiori apps reference library at published on SAP site.


Needed for ...

sap.hba.r.tmem::Transportation Manager

Read access to KPI data (views and XS OData services)

As a prerequisite for read-access to KPI definition, ensure you have assigned the generic role Smart Business Runtime Role ( to all users or roles.

As a prerequisite for KPI modeling, ensure you have assigned the generic role Smart Business Administration Role ( to specific users (e.g. key user, administrator).

For more information about SAP HANA roles, see Assigning Roles for Accessing SAP HANA Data.

HANA Server: Generate and Assign Analytic Privileges to Users and Roles

Needed for

How to generate?

Access to KPI data (only views)

Authorization Assistant cannot be used. Instead, you must manually enter Analytical Privileges and ensure consistency with entries in the back-end system.

Access to KPI definition in KPI catalog

Generated by KPI Modeler

For more information, see KPI Modeler.

Front-End Server: Activate SAP UI5 Application

SAP UI5 Application

Technical Name

Generic Drill-Down Application


For more information about how to activate the SAP UI5 application (ICF service), see Front-End Server: Activate ICF Services of SAP UI5 Application.

Front-End Server: Enable App for Access in SAP Fiori Launchpad

The SAP Fiori launchpad is the entry point to SAP Fiori apps. From a user perspective, it displays those SAP Fiori apps that have been assigned to the catalog designed for this user's role.

This presupposes that an administrator has made the necessary assignments in the launchpad designer to enable a user's access to the respective SAP Fiori apps in the SAP Fiori launchpad. For more information, see Setup of Catalogs, Groups, and Roles in the SAP Fiori Launchpad.

SAP delivers technical catalogs for groups of SAP Fiori apps as repositories to create your own catalogs in the launchpad designer. Along with these catalogs, more technical content is delivered for each SAP Fiori app. You can find the delivered technical content for each SAP Fiori app in the SAP Fiori apps reference library.

Front-End Server and Back-End Server: Assign OData Service Authorizations to Users

You must assign OData service authorizations for the KPI to your users.

Caution Caution

Several authorization default values are connected to the OData service. To ensure that all these default values are assigned to a user, you have to follow the instructions given under the documentation links provided.

End of the caution.

Make the assignment on the back-end server and on the front-end server:

OData Service (Version Number)

Back-end Server: Delivered Authorization Role (PFCG Role)

Front-End Server: AuthorizationRole

/sap/hba/r/tmem/odata/DelayedInTransitFrtOrderAndFrtBookingQuery.xsodata (1)


Note Note

In addition, this role contains authorizations to display the related business data.

End of the note.

Use an existing role or create a new one.