Show TOC

App Implementation: My Opportunities Locate 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

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


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

SAP Note Number


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


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


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.


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.


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

OData service authorization must be assigned.

Configuration Tasks

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

  • Notes

    To display or create a note in the My Opportunities app, you must configure the text object CRM_ORDERH in the SAP CRM back-end system. With this configuration, the text type accepts changes as P (Log). Make the following settings in Customizing for Customer Relationship Management under Start of the navigation path Basic Functions Next navigation step Test Management Next navigation step Define Text Determination Procedure End of the navigation path

    1. In this Customizing activity, select the text object CRM_ORDERH and then choose the Procedure view.
    2. Select the text determination procedure that has been specified for the transaction type of opportunities (for example, OPP00001).
    3. Select the Definition of Procedure view.
    4. Specify the value P (Log) in the Changes field for at least one text type.
      • If multiple text types are marked as P (Log), the first text type in the sequence is considered in My Opportunities.

      • If you want to display notes that were created with P (Log) on the SAP CRM UI or with the My Opportunities app, you must define an additional text type: R (Display Log). This text type is linked to the UI (as the header note) and the log entries are displayed on the SAP CRM UI. To specify this text type as a header note, you must define it as the first entry in a sequence

  • "Employee" Business Partner Role

    Ensure that each user who should have access to the My Opportunities app is assigned to a business partner with the Employee business partner role.

  • System Statuses

    When you launch My Opportunities, the default search of records is based on the user statuses that are mapped to the system statuses I1002 and I1003.

  • Searching for Opportunities

    When you search for opportunities, the search is triggered against the object ID or the description. For the purpose of better performance, it is recommended that you use keywords that are exact phrases or close variations.

  • Transaction Types of Opportunities

    When you create opportunities using the My Opportunities app, the system allows you to choose only from those transaction types that have been defined in Customizing for Customer Relationship Management underStart of the navigation path Transactions Next navigation step Settings for Opportunities Next navigation step Define Settings for the "My Opportunities" App End of the navigation path

More Information

For more information about app implementation, see Start of the navigation path App Implementation Information for SAP Fiori End of the navigation path.