Show TOC

 App Implementation: Post G/L Document Locate this document in the navigation structure

System Landscape Requirements

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

Configuration of SAP Fiori Infrastructure

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

End of the note.

Required SAP Notes

For the Post G/L Document app, the following SAP Notes must implemented:

Back-End/Front-End Server

SAP Note Number

Description

Front-end server and back-end server

2062970Information published on SAP site

Collective SAP Note for the Post G/L Document app

Implementation Tasks

The following sections list tasks that have to be performed to implement the Post G/L Document 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)

FAC_FINANCIALS_POSTING_SRV (1)

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

Front-End Server: Activate UI5 Application

Component

Technical Name

UI5 Application

FIN_GLDOCPOST

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.

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  .

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

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

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_FINANCIALS_POSTING_SRV (1)

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

End of the caution.

Make the assignment on the back-end server and on the front-end server:

Note Note

If your PFCG role does not provide all the authorizations you need, you will not be able to post G/L documents. Transaction SU53 in the back end logs any failed authorization checks. From this you can determine which required authorizations are missing.

End of the note.

Configuration Tasks

The following configuration tasks need to be carried out in the back end:

  • Field Status Variants

    In Customizing under   Financial Accounting (New)   Financial Accounting Global Settings (New)   Ledgers   Fields  , perform the following IMG activities:

    • Define Field Status Variants

      Define the field status variants and field status groups that you require. These allow you to control which input fields are visible in the app, and whether input is mandatory or optional.

      For detailed information, see the documentation for this IMG activity.

    • Assign Company Code to Field Status Variants

      Assign the company codes in which you want to use identical field status groups to the same field status variant.

      For detailed information, see the documentation for this IMG activity.

  • Editing Options

    Individual users should make the following user-specific settings in the SAP Menu under   Accounting   Financial Accounting   General Ledger   Document Entry   Enter G/L Account Document   by choosing   Settings   Editing Options  :

    • No Company Code Proposal: This checkbox should be deselected so that the default company code is proposed in the Company Code field.

    • Under Special options for single screen transactions, the document type option Document type ready for input should be selected. This allows the user to select the document type in the app.

    Note Note

    Changes made to other editing options will not be reflected in the app.

    End of the note.

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.