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 100 |
For more information about the installation of SAP Fiori products, see Downloading and Installing Product Versions.
Note
The app offers the possibility to upload documents. For security reasons, we strongly recommend that you install an appropriate virus scanner in your SAP Fiori system landscape and define sufficiently restrictive scan profiles to prevent the upload of malicious content.
For more information on virus scanning and scan profiles for SAP Fiori apps, see Virus Scanning.
For the Manage G/L Documents app, the following SAP Notes must implemented:
Back-End/Front-End Server | SAP Note Number | Description |
---|---|---|
Front-end server and back-end server | Collective SAP Note for the Manage G/L Documents app |
The following sections list tasks that have to be performed to implement the Manage G/L Documents app. The tables contain the app-specific data required for these tasks:
Component | Technical Name |
---|---|
OData Service (Version Number) | FAC_FINANCIAL_DOCUMENT_SRV_01 (1) |
For more information about activating OData services, see Front-End Server: Activate OData Services.
Component | Technical Name |
---|---|
UI5 Application | FIN_GLDOCDISP |
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 | AccountingDocument |
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 |
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 |
---|---|---|
FAC_FINANCIAL_DOCUMENT_SRV_01 (1) | SAP_FIN_GLDOCMANAGE_APP | You can assign the OData service authorization to a business role, for example the delivered business role SAP_SFIN_BCR_GLACCOUNTANT. |
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.
Note
If your PFCG role does not provide all the authorizations you need, you will not be able to carry out all required actions for managing G/L documents. Transaction SU53 in the back end logs any failed authorization checks. From this you can determine which required authorizations are missing.
In some cases failed authorization checks are not logged in SU53. For example, if not all G/L documents are displayed in the app, this could be caused by missing authorization for the company code. However, in this case the failed authorization checks are not logged. To resolve issues like this, check your PFCG role to see which authorizations it lacks. Decide which of these missing authorizations could be causing the problem, and add the authorizations to the role.
Reversals require authorization for activity 01 (Create).
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.