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 | |
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.
For Manage Budget, the following SAP Notes must be available:
Back-End/Front-End Server | SAP Note Number | Description |
---|---|---|
Front-End and Back-End | Release Note for Fiori app Manage Budget |
The following sections list tasks that have to be performed to implement the Manage Budget app. The tables contain the app-specific data required for these tasks:
Component | Technical Name |
---|---|
OData Service (Version Number) | FCO_MS_SPEND_SRV (1) |
For more information about activating OData services, see Front-End Server: Activate OData Services.
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).
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
.Component | Technical Name |
---|---|
Semantic Object | CostObject |
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 |
To restrict access to OData services to specific users, 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 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_MB_BUDGET_SRV (1) | SAP_FIN_MANAGEBUDGET_APP | SAP_SFIN_BCR_COSTMANAGER |
You must assign OData service authorizations for the app to your users.
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.
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 copy this role and adjust it to your needs. For more information, see Back-End Server: Assign OData Service Authorization to Users.
On the front-end server, you must assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs. For more information, see Front-End Server: Assign OData Service Authorization to Users.
To enable Manage Budget, you must perform the following configuration tasks:
User role configuration:
Front-end system (gateway system)
Run transaction SU01, specify a user and click Edit.
On the Roles tab, enter the following roles:
SAP_FIN_TCR_FSA
SAP_FIN_TCR_T
SAP_SFIN_BCR_COSTMANAGER
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:
Run transaction PFCG, enter role SAP_FIN_MANAGEBUDGET_APP and click Copy.
Enter a target role, for example, Z_SAP_SFIN_TCR_T, and click Copy All.
Click Edit.
On the Authorization tab, click Propose Profile Name.
Click Save.
Click Change Authorization Data.
Enter the controlling areas to which the user has access.
Click Save.
Enter values for other authorization objects to which the user has access.
Click Save and then Generate, and the status of authorization becomes “generated”.
Assign this role to the user by following the steps introduced in Front-end system (gateway system) in the back-end system.
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_PROFIT_CENTER_APP
SAP_FIN_INTERNALORDER_APP
Business configuration:
Run transaction FPB_MAINTAIN_PERS_S in the back-end system.
On the next page, enter DIA_IOMONITOR in Personalization Dialog, enter your target user, and then click Execute.
Specify your controlling area, internal order group, cost element group, and then click Save. (Controlling Area, Internal Order Group and Cost Element Group are required, because the application cannot recognize individual values.)
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.