Show TOC

 App Implementation: Bank Statement Monitor Locate this document in the navigation structure

System Landscape Requirements

Before you can start to implement the app, ensure that your system landscape has been set up to enable SAP Fiori. This also implies that the front-end and back-end components for your app are already available in this system landscape:

SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with SAP HANA XS

Configuration of Front-End Server

Configuration of SAP Fiori Infrastructure

Back-End Components (Product Version Stack)

Financials add-on 1.0 for SAP Business Suite powered by SAP HANA

SAP HANA Content Component Delivered with (Product Version Stack)

SAP Smart Business for the financials add-on 1.0 for SAP Business Suite powered by SAP HANA

VDM Contained (Product Version Stack)

SAP HANA Analytics for SFIN 1.0

Front-End Components Delivered with (Product Version Stack)

SAP Smart Business for the financials add-on 1.0 for SAP Business Suite powered by SAP HANA

Instance: Frontend Serv. Cont. SFIN Analy.

Software Component Version: UIHSFIN01 100

For more information about the installation of the front-end components, see Installation of SAP Smart Business Products on Front-End Server.

Tile Type for Launching App

The Bank Statement Monitor analytical app uses a KPI tile to launch the app.

This KPI requires an evaluation that specifies one or more input parameters. For more information see Configuration Settings: Bank Statement Monitor.

Required SAP Notes

For the Bank Statement Monitor app, the following SAP Notes must be implemented:

Back-End/Front-End Server

SAP Note Number

Description

Back-end server and front-end server

2028568

Collective SAP Note for the Bank Statement Monitor app

Implementation Tasks

The following sections list tasks that have to be performed to implement the Bank Statement Monitor app. The tables contain the tile-specific data required for these tasks.

HANA Server: Assign SAP HANA Roles to Users and Roles

SAP HANA Role

Needed for ...

Not applicable

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

Note Note

No HANA role is defined for the following reason: Data provider for this KPI is not HANA VDM view relevant. Instead, it is provided by BW query based ABAP OData.

  • BW query: FCLM_CP_BSM_Q0003

  • ABAP OData service: BANKSTATEMENTIMPORTFIORI_4_SR (1)

End of the note.

As a prerequisite for read-access to KPI definition, ensure you have assigned the generic role Smart Business Runtime Role (sap.hba.apps.kpi.s.roles::SAP_SMART_BUSINESS_RUNTIME) for read-access to KPI definition to all users or roles.

As a prerequisite for KPI modeling, ensure you have assigned the generic role Smart Business Administration Role (sap.hba.apps.kpi.s.roles::SAP_SMART_BUSINESS_MODELER) 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 definition in KPI catalog

Generated by KPI Modeler

For more information, see KPI Modeler.

Front-End Server: Activate UI5 Application

UI5 Application

Technical Name

Generic Drill-down Application

/sap/bc/ui5_ui5/sap/ca_kpi

For more information about how to activate the UI5 application (ICF service), see Activate ICF Services.

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

There are several steps to be performed to enable the app for access in the SAP Fiori launchpad. You need to assign the following PFCG roles to end users to consume this KPI:

Component

Technical Name

Business Role (Needed for Access to KPI Catalog and Generic Drill-Down Application)

SAP_KPIFRW4_TCR_S

For more information about adding an app to the SAP Fiori Launchpad, see Setup of Catalogs, Groups, and Roles in the SAP Fiori Launchpad.

Technical Data

The following table gives you an overview of important technical data for the app.

Technical Data

Technical Name

KPI Definition (Technical Name)

sap.hba.sfin.cashmgr.bankstatementmonitor

OData Services (Assigned to this KPI)

BANKSTATEMENTIMPORTFIORI_4_SR (1)

Entity Sets and Measures (Relevant for this KPI)

Entity set: FCLM_CP_BSM_Q0003Results

Measure: BANKSTMTTILEPERCENT

Semantic Object

BANKSTMTTILEPERCENT

Business Role (Needed for Access to KPI Catalog and Generic Drill-Down Application)

SAP_KPIFRW4_TCR_S

This business role comprises the following two catalog providers listed under Business Catalog.

Business Catalog

SAP_KPIFRW_TC_R (for KPI catalog)

SAP_KPIFRW_TC_S (for generic drill-down application)

Report Launchpad (for Generic Drill-Down Application)

Role: UISKPI01

Instance: ANALYTICS

Application Alias: analyzeKPIDetails

Back-End Server: Assign Role with ODATA Service Authorization to Users

To enable communication with the ABAP back-end through OData services, a role with authorization object S_SERVICE(Check at Start of External Services) with the corresponding service name has to be created and assigned to the user in SAP back-end.

  1. In transaction PFCG, create a new role.

  2. On the menu tab, insert a node into the role menu by choosing Authorization Default. Enter the following values:

    • Authorization Default: TADIR Service

    • Program ID: R3TR

    • Object Type: IWSG

    • TADIR Service: ZBANKSTATEMENTIMPORTFIORI_4_SR_0001

  3. Generate the profile in authorization maintenance.

  4. Assign the new role to the SAP Fiori app user.

Adding Remote Catalog for System Alias of ODATA Services
  1. Log on to the Fiori Designer of your system.

  2. To create a catalog, click the add button on the left bottom. You need to specify the following values in the dialogue box:

    • Select the Remote radio button.

    • Enter a title.

    • Enter an ID in the ID field. This ID is the unique key to identify your catalog and will be used later in the PFCG menu.

    • Enter HANA_CATALOG as the remote ID.

    • In the System alias field, enter the system alias of your ODATA service.

    • In the Base URL field, choose /sap/hba/apps/kpi/s/odata/hana_chip_catalog.xsodata/.

  3. In the gateway system, run transaction PFCG.

  4. On the Menu tab, choose the Insert Node pushbutton to the right of the Transaction pushbutton to display the menu. Then choose Catalog Provider.

  5. To assign a catalog, in the dialogue box, specify the following values:

    • In the Catalog Provider field, choose Remote Catalog.

    • In the Catalog ID field, enter the ID of the remote catalog you just created in Fiori Designer.

  6. Assign the PFCG role to the relevant users.

    Note Note

    To check if the PFCG role has been assigned to your users, switch to the User tab and choose the User comparison pushbutton.

    End of the note.
  7. Save your changes.

Generate Easy Query

If an easy query is not generated automatically, run transaction SE37 and call function module RSEQ_EQ_GENERATION to generate an easy query. (To check if an easy query is already generated, run transaction SE37 and call function module RSEQ_QUERY_METADATA.)

Query

FCLM_CP_BSM_Q0003

InforProvider

2O0FCLM_CP_BIC