Show TOC

 App Implementation: My Spend Locate this document in the navigation structure

System Landscape Requirements

Before you 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 components and back-end components for your app are already available in this system landscape:

SAP Fiori System Landscape Options

Configuration of Front-End Server

Configuration of SAP Fiori Infrastructure

Back-End Components Delivered with (Product Version Stack)

SAP Simple Finance add-on 1.0 SPS04 for SAP Business Suite powered by SAP HANA

Front-End Components Delivered with (Product Version Stack)

SAP Fiori for the SAP Simple Finance add-on 1.0 SPS04 for SAP Business Suite powered by SAP HANA

Ensure that the front-end component of the app is in place on your front-end server. It is automatically installed with the UI-Add-On.

Front-End Server: Front-End Component of App (Software Component)

UIAPFI70

For more information about the installation of SAP Fiori products, see Downloading and Installing Product Versions.

Required SAP Notes

For the My Spend app, the following SAP Notes must be implemented:

Back-End/Front-End Server

SAP Note Number

Description

Back-end server and front-end server

1983297Information published on SAP site

Collective SAP Note for the My Spend app

Implementation Tasks

The following sections list tasks that have to be performed to implement the My Spend app. The tables contain the app-specific data required for these tasks:

Front-End Server: Activate OData Services

Component

Technical Name

OData Service (Version Number)

FCO_MS_SPEND_SRV (0001)

For more information about activating OData services, see Front-End Server: Activate OData Services.

Front-End Server: Activate UI5 Application

Component

Technical Name

UI5 Application

FIN_MYSPEND

For more information about how to activate the ICF service, see Front-End Server: Activate ICF Services of SAPUI5 Application (for transactional apps) or Activate ICF Service of BSP Application (fact sheets).

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 require the listed data to perform these steps.

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 at   https://www.sap.com/fiori-apps-library  .

Component

Technical Name

Semantic Object

CostObjectVariance

Business Role

SAP_SFIN_BCR_COSTMANAGER

Business Catalog

SAP_SFIN_BC_COSTMANAGER

Business Catalog Group

SAP_SFIN_BCG_COSTMANAGER

Technical Role

SAP_SFIN_TCR_T

Technical Catalog

SAP_SFIN_TC_T_FI

LPD_CUST Role

UIAPFI70

LPD_CUST Instance

TRANSACTIONAL_CO

Front-End Server and Back-End Server: Assign Roles with OData Service Authorization to Users

To grant specific users access to OData services, you have to assign roles (including OData service authorization for the app) to your users. You have to make the assignment on the back-end server and on the front-end server:

  • On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can adjust this role according to your needs.

  • On the front-end server, you can assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs.

OData Service (Version Number)

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

Front-End Server: Authorization Role

FCO_MS_SPEND_SRV (1)

SAP_FIN_MYSPEND_APP

You can assign the OData service authorization to a business role, for example the delivered business role SAP_SFIN_BCR_COSTMANAGER.

You must assign OData service authorizations for the app 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:

Configuration Tasks

To enable My Spend, you must perform the following configuration tasks:

  • User role configuration:

    • Front-end system (gateway system)

      1. Run transaction SU01, specify a user and click Edit.

      2. On the Roles tab, enter the following roles:

        • SAP_FIN_TCR_FSA

        • SAP_FIN_TCR_T

        • SAP_SFIN_BCR_COSTMANAGER

      3. Click Save.

    • Back-end system (ECC system with business data)

      If the gateway system and the back-end system are on the same system, follow these steps in the same system:

      1. Run transaction PFCG, enter role SAP_FIN_MYSPEND_APP and click Copy.

      2. Enter a target role, for example, Z_FIN_MYSPEND_APP, and click Copy All.

      3. Click Edit.

      4. On the Authorization tab, click Propose Profile Name.

      5. Click Save.

      6. Click Change Authorization Data.

      7. Enter the controlling areas to which the user has access.

      8. Click Save.

      9. Enter values for other authorization objects to which the user has access.

      10. Click Save and then Generate, and the status of authorization becomes “generated”.

      11. Assign this role to the user by following the steps introduced in Front-end system (gateway system) in the back-end system.

      12. Repeat steps 1 through 11 for the following roles:

        • SAP_FIN_COSTCENTER_APP

        • SAP_FIN_CONTROLLING_DOC_APP

        • SAP_FIN_COSTCENTERGROUP_APP

        • SAP_FIN_COSTELEMENT_APP

        • SAP_FIN_COST_ELEMENT_GRP_APP

        • SAP_FIN_INTERNALORDER_APP

  • Business configuration:

    1. Run transaction FPB_MAINTAIN_PERS_S in the back-end system.

    2. Enter DIA_CCMONITOR in Personalization Dialog, enter your target user, and then click Execute.

    3. Specify your controlling area, cost center group, cost element group, and then click Save. (Cost Center Group and Cost Element Group are required, because the application cannot recognize individual values.)

    4. In the next page, enter DIA_IOMONITOR in Personalization Dialog, enter your target user, and then click Execute.

    5. Specify your controlling area, internal order group, cost element group, and then click Save. (Cost Center Group and Cost Element Group are required, because the application cannot recognize individual values.)

Creating a Custom Role

To create your own role to customize the authorizations and assign this role to users, complete the following steps:

  1. Run transaction PFCG.

  2. Enter the role name and then choose the Create Single Role pushbutton.

  3. Enter a description for the role and save your changes.

  4. Switch to the Authorization tab and choose the Change Authorization Data pushbutton.

  5. On the Change Role: Authorizations screen that appears, choose the Manually pushbutton and enter the authorization object K_CCA. Then choose the Continue (Enter) pushbutton.

  6. Edit the authorization you want to allow and choose the Generate (Shift+F5) pushbutton. Then exit the screen.

  7. Switch to the User tab and assign this role to the relevant users.

  8. Save your changes.

Jam Integration

For information on how to configure SAP Jam, see http://help.sap.com/sapjam.

More Information

For general information about the user management concept in a SAP Fiori environment, see Users in ABAP Front-End System and Users in ABAP Back-End System.