App Implementation: Manage Cost Center Master Data

System Landscape Requirements

The app consists of the SAP Fiori launchpad configuration (such as the tiles and the navigation) and back-end components (such as the Web Dynpro application itself). The back-end and the front-end components are delivered in separate products and have to be installed in a system landscape that is enabled for SAP Fiori.

Back-End Components Delivered with (Product Version Stack)	SAP Simple Finance add-on 1.0 SPS04 for SAP Business Suite powered by SAP HANA Required product release: `SAP SFINANCIALS 1.0` Required software components: `SAP_FIN 700`
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 Required product release: `SAP FIORI FOR SAP SFIN 1.0` Required software components: `UIAPFI70`

Back-End Components Delivered with (Product Version Stack)

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

Required product release: SAP SFINANCIALS 1.0
Required software components: SAP_FIN 700

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

Required product release: SAP FIORI FOR SAP SFIN 1.0
Required software components: UIAPFI70

Required SAP Notes

For the Manage Cost Center Master Data app, the following SAP Notes must be implemented:

Back-End/Front-End Server	SAP Note Number	Description
Back-end server and front-end server	2047208	SAP Release Information Note for the Manage Cost Center Master Data app

Implementation Tasks

This app uses Web Dynpro technology.

The following sections list tasks that have to be performed to implement the Manage Cost Center Master Data 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)	`FCOM_COSTCENTER_SRV (0001)`

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

Front-End Server: Activate SAP UI5 Application

Component	Technical Name
SAP UI5 Application	`FIN_COSTCENTER`

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.

Component	Technical Name
Semantic Object	`CostCenter`
Business Role	`SAP_SFIN_BCR_GLACCOUNTANT`
Business Catalog	`SAP_SFIN_BC_GLACCOUNTANT`
Business Catalog Group	`SAP_SFIN_BCG_GLACCOUNTANT`
Technical Role	`SAP_SFIN_TCR_T`
Technical Catalog	`SAP_SFIN_TC_T_FI`
`LPD_CUST` Role	`UIAPFI70`
`LPD_CUST` Instance	`TRANSACTIONAL_CO`
System Alias	`SAP_ECC_Financials`

Carry out the following configuration tasks:

Run transaction User Maintenance (SU01), specify a user and choose Edit.
On the Roles tab, enter the SAP_SFIN_BCR_GLACCOUNTANT role.
Save your changes.

Customizing Navigation Target

Before you can access this app, you must have specified an RFC destination that points to the SAP back end where the Web Dynpro is running. The predefined system alias for the RFC destination is SAP_ECC_Financials (see transaction LPD_CUST and access the app-specific configuration).

Use transaction SM59 to check whether the RFC destination SAP_ECC_Financials is available.
If this RFC destination is not available, create it manually (connection type H) and configure it according to your needs (SSL).

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 .

You can also refer to Customizing Navigation Targets in the SAP Help Portal, http://help.sap.com under Technology User Interface Add-On for SAP NetWeaver Application Help SAP Fiori Launchpad Configuring Navigation .

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

In the front-end system, you can assign the OData service authorization to a business role, for example, the delivered business role SAP_SFIN_BCR_GLACCOUNTANT. For more information, see Front-End Server: Assign OData Service Authorization to Users.

In the back-end system, perform the following steps to create a role with OData service authorization and assign this role to users:

Run transaction Role Maintenance (PFCG).
Enter a role name, such as ZSAP_FIN_COSTCENTER_APP, and click Create Single Role.
Save the role.
On to the Menu tab, open the menu of the pushbutton for adding objects (+ pushbutton) and choose the object type Authorization Default.
From the Authorization Default menu, choose TADIR Service and enter the following data:
- Program ID: R3TR
- Object Type: IWSV
In the table, enter FCOM_COSTCENTER_SRV, that is, the name of the activated OData service for your app.
On to the Authorizations tab, choose the pushbutton next to Profile Name to generate the authorization profile for the role.
Choose Change Authorization Data and enter values according to your business process.
Choose Save and then Generate.
Run transaction User Maintenance (SU01) and assign the role to the user.

Back-End Server: Activate Web Dynpro Application

Component	Technical Name
Web Dynpro Application	`FCOM_COSTCENTER`

Use transaction sicf and make sure that the ICF service for the Web Dynpro application is activated.

Back-End Server: Assign Role with Start Authorization for Web Dynpro Application

Component	Technical Name
Back-End Role	`SAP_SFIN_ACC_MASTERDATA`

Carry out the following configuration tasks in the back-end system:

Copy the back-end role and enter authorization values according to your business process.
Assign this role to the user in the back-end system.

Extensibility

This app is suitable to be extended. For more information, see App Extensibility: Manage Cost Center Master Data.

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.