Show TOC

App Implementation: Monitor Capacity UtilizationLocate this document in the navigation structure

Implementation information for SAP Fiori app.

System Landscape Requirements

In order to be able to implement this app, your system landscape has to be enabled for SAP Fiori. Depending on the database type serving as the basis in your system landscape, it has to be set up for SAP Fiori and has to meet the respective prerequisites:

The SAP product version in the back-end system serving as the the basis for the app must be the following:

Required Back-End Product (Product Version Stack)

Each SAP Fiori app consists of front-end components and back-end components:
  • The front-end components of the app consist of the user interfaces and content required for launching the app on the SAP Fiori launchpad. These components have to be installed on your front-end server.

  • The back-end components of the app mainly consist of the OData services required for the app. These components have to be installed in your back-end system.

The front-end and back-end components of the app are delivered with the following SAP product versions as part of the listed software components. The required software components for the app are contained in the listed product instances:

App Component

Required SAP Product Version (Support Package Stack)

Available Instances Containing Software Component

Software Component Required for App (Support Package)

Front-End Components

( ) ( )

Back-End Components

() ( )

For more information about the installation of front-end components, see http://help.sap.com/fiori_implementation.

The app offers the possibility to upload documents. For security reasons, we strongly recommend that you install an appropriate virus scanner in your respective back-end system and define sufficiently restrictive scan profiles to prevent the upload of malicious content. For more information about virus scanning and scan profiles for SAP Fiori apps, see Virus Scanning.

Required SAP Notes

On the back-end server, the following SAP notes must be implemented for this app:

SAP Note Number

Description

On the front-end server, the following SAP notes must be implemented for this app:

SAP Note Number

Description

Implementation Tasks

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

You can find the data required to perform these tasks in the SAP Fiori apps reference library at:

Front-End Server : Activate OData Services

Component

Technical Name

OData Service (Version Number)

( )

For more information about how to activate the OData service, see Front-End Server: Activate OData Services .

Front-End Server: Activate SAP UI5 Application

Component

Technical Name

SAP UI5 Application

For more information about how to activate the SAP UI5 application (ICF service), see Front-End Server: Activate ICF Services.

Enable App for Access in SAP Fiori Launchpad

To define the access of single users to this app in the SAP Fiori launchpad, technical content is delivered, such as catalogs and example roles.

You can find an overview of the delivered technical content for this SAP Fiori app in the SAP Fiori apps reference library.

For more information about how to procede with this content, see Enable App for Access in SAP Fiori Launchpad.

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.

Note

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.

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

OData Service (Version Number)

Back-End Server: Delivered Authorization Role (PFCG Role)

Front-End Server : Assignment to Authorization Role

( )

In addition, this role contains authorizations to display the related business data.

Note

In addition, this role contains authorizations to display the related business data.

OData service authorization must be assigned.

Prerequisites for Implementation

Before implementing the app, you must ensure the following:

  • You have configured the SAP APO on ERP component in the back-end system. For more information, see Customizing for SAP APO on ERP.

  • You have assigned the authorizations in the back-end system that are required for using the linked transactions to the business users of this app.

  • In transaction RFC Destinations (SM59), you have configured the RFC connection SAP_ERP_PP with connection type H and chosen Trusted Relationship as the Logon Procedure. This RFC connection is used for navigating to the back-end system.

    If you use a different name for the RFC connection, you have to change the system alias for the following entries in transaction Launchpad Customizing (LPD_CUST):

    Role

    Instance

    Description

    UIAPPDS01

    TRANSACTIONAL

    Resource Planning Table

    UIAPPDS01

    TRANSACTIONAL

    Detailed Scheduling Planning Board

Configuration Tasks

To be able to implement the app, you must perform the following configuration tasks in the back-end system:

Default configuration settings are provided for this app in Customizing for SAP APO on ERP under Apps for Material Requirements Planning. Check if the SAP standard configuration settings in the following Customizing activities meet your business requirements. If this is the case, no further changes are necessary. Otherwise you can tailor the following Customizing settings to your needs:

  • Define Evaluation Profile for Capacity Utilization:

    In the activity Define Evaluation Profile for Capacity Utilization, you can create your own capacity utilization profile. The system uses this profile for calculating the capacity utilization of the resources. In the profile, you define which orders or operations the system takes into account as well as the threshold percentages for underutilization and full utilization.

  • Assign Evaluation Profile to User:

    In the activity Assign Evaluation Profile to User, you can assign capacity utilization profiles to users to control which evaluation profiles the user can choose when working in the app. If you make no changes here, the system automatically uses the SAP standard capacity utilization profile.

More Information

For more information about app implementation, see http://help.sap.com/fiori_implementation Start of the navigation path App Implementation Information for SAP Fiori End of the navigation path.