App Implementation: Manage Profit CentersThe 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
|
|---|---|
Front-End Components Delivered with (Product Version Stack) | SAP Fiori for SAP S/4HANA Finance 1605 SPS 4
|
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 .
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 | Release Information Note: SAP Simple Finance, on-premise edition 1602 | |
Back-end server and front-end server | Release Information Note: SAP Fiori for SAP S/4HANA Finance, on-premise edition 1602 | |
Back-end server and front-end server | SAP Release Information Note for the |
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
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.
Component | Technical Name |
|---|---|
OData Service (Version Number) |
|
For more information about activating OData services, see SAP Help Portal at .
Component | Technical Name |
|---|---|
| SAP UI5 Application |
|
For more information, see SAP Help Portal at .
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 : Configuring the Launchpad
and Configuring Authorization Roles
.
For more information on catalogs and roles, see 2242596
.
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.
.
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).
You can also refer to Customizing Navigation Targets
in the SAP Help Portal, http://help.sap.com
under .
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 .
Component | Technical Name |
|---|---|
Web Dynpro Application |
|
Use transaction sicf
and make sure that the ICF service for the Web Dynpro application is activated.
Component | Technical Name |
|---|---|
Back-End Role |
|
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.
The app is suitable to be extended. For more information, see App Extensibility: Manage Profit Centers.
For more information about the user management concept in an SAP Fiori environment, see SAP Help Portal at : Users in ABAP Front-End System
and Users in ABAP Back-End System
.