App Implementation: Manage Profit Centers

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 S/4HANA Finance 1605 SPS 7

  • Required product release: SAP S/4HANA FINANCE 1605

  • Required software components: SAP_FIN 730

Front-End Components Delivered with (Product Version Stack)

SAP Fiori for SAP S/4HANA Finance 1605 SPS 4

  • Required product release: SAP FIORI FOR SAP SFIN 1605

  • Required software components: UIAPFI70 300 SPS 3

  • Required software components: UIAPPL01 100 SPS 1

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.

For more information about the installation of SAP Fiori products, see SAP Help Portal at Start of the navigation path http://help.sap.com/fiori_implementationInformation published on SAP site Next navigation step System Landscape Required for SAP Fiori Next navigation step With SAP NetWeaver 7.5 Next navigation step English Next navigation step Setup of SAP Fiori System Landscape Next navigation step Downloading and Installing Product Versions End of the navigation path.

Required SAP Notes

The following SAP Notes must be available for this app:

Back-End/Front-End Server

SAP Note Number

Description

Back-end server and front-end server

2235268Information published on SAP site

Release Information Note: SAP Simple Finance, on-premise edition 1602

Back-end server and front-end server

2255079Information published on SAP site

Release Information Note: SAP Fiori for SAP S/4HANA Finance, on-premise edition 1602

Back-end server and front-end server

2030663Information published on SAP site

SAP Release Information Note for the Manage Profit Center Master Data app

Implementation Tasks

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

Note Note

This app uses a combination of SAP UI5 technology and Web Dynpro technology. SAP UI5 is used to search for profit centers and to display a profit center list. Web Dynpro is used for the screens where you actually work with the profit center master data.

You can access the app in two different ways:

  • From the SAP Fiori Launchpad

    Here, you always start by searching for a profit center. Since SAP UI5 technology is used for the search, you need to perform the tasks described in the Implementation Tasks for SAP UI5 section in addition to the tasks described in the Implementation Tasks for Web Dynpro section.

  • From within another app

    Here, you don’t need to search for a profit center because it’s already been selected in the other app. For this reason, you only need to perform the tasks described in the Implementation Tasks for Web Dynpro section.

End of the note.

Implementation Tasks for SAP UI5

Front-End Server: Activate OData Services

Component

Technical Name

OData Service (Version Number)

FAC_PC_SRV (0001)

For more information about activating OData services, see SAP Help Portal at Start of the navigation path http://help.sap.com/nw75Information published on SAP site Next navigation step Application Help Next navigation step UI Technologies in SAP NetWeaver with SAP_UI 750 Next navigation step [Language] Next navigation step SAP Fiori Launchpad Next navigation step Setting up the Launchpad Next navigation step Activating SAP Gateway OData Services End of the navigation path.

Front-End Server: Activate SAP UI5 Application

Component

Technical Name

SAP UI5 Application

FIN_PROFITCENTR

For more information, see SAP Help Portal at Start of the navigation path http://help.sap.com/nw75Information published on SAP site Next navigation step Application Help Next navigation step UI Technologies in SAP NetWeaver with SAP_UI 750 Next navigation step [Language] Next navigation step SAP Fiori Launchpad Next navigation step Setting up the Launchpad Next navigation step Configuring ICF Nodes End of the navigation path.

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

The SAP Fiori launchpad is the entry point to apps. In the launchpad, the user can see and access those apps that have been assigned by an administrator to the catalog designed for this user's role.

For more information, see SAP Help Portal at Start of the navigation path http://help.sap.com/nw75Information published on SAP site Next navigation step Application Help Next navigation step UI Technologies in SAP NetWeaver with SAP_UI 750 Next navigation step [Language] Next navigation step SAP Fiori Launchpad Next navigation step Setting up the Launchpad End of the navigation path: Configuring the Launchpad and Configuring Authorization Roles.

For more information on catalogs and roles, see 2242596Information published on SAP site.

To access this app directly in the SAP Fiori apps reference library, click the following link. Then click Implementation Information and select the relevant delivery date.

Start of the navigation path https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/index.html?appId=F0732Information published on SAP site End of the navigation path.

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).

  1. Use transaction SM59 to check whether the RFC destination SAP_ECC_Financials is available.

  2. If this RFC destination is not available, create it manually (connection type H) and configure it according to your needs (SSL).

You can also refer to Customizing Navigation Targets in the SAP Help Portal, http://help.sap.comInformation published on SAP site under Start of the navigation path Technology Next navigation step User Interface Add-On for SAP NetWeaver Next navigation step Application Help Next navigation step SAP Fiori Launchpad Next navigation step Configuring Navigation End of the navigation path.

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

You must assign OData service authorizations for the app to your users. The assignments must be made on the back-end server and on the front-end server.

For information on the Fiori authorization and user management concept, see SAP Help Portal at Start of the navigation path http://help.sap.com/fiori_implementationInformation published on SAP site Next navigation step App Implementation Information for SAP Fiori Next navigation step With SAP NetWeaver 7.5 Next navigation step English Next navigation step User Management and Authorization End of the navigation path.

Implementation Tasks for Web Dynpro

Back-End Server: Activate Web Dynpro Application

Component

Technical Name

Web Dynpro Application

FAC_PROFITCENTR

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:

  1. Copy the back-end role and enter authorization values according to your business process.

  2. Assign this role to the user in the back-end system.

Extensibility

The app is suitable to be extended. For more information, see App Extensibility: Manage Profit Centers.

More Information

For more information about the user management concept in an SAP Fiori environment, see SAP Help Portal at Start of the navigation path http://help.sap.com/fiori_implementationInformation published on SAP site Next navigation step App Implementation Information Next navigation step With SAP NetWeaver 7.5 Next navigation step English Next navigation step User Management and Authorization End of the navigation path: Users in ABAP Front-End System and Users in ABAP Back-End System.