Show TOC

 App Implementation: My Opportunities

System Landscape Requirements

Note Note

This app version is deprecated. We recommend that you install the app available with the software component UICRM001 100. If you have already implemented the deprecated version, we recommend to switch to the version available with component UICRM001 100.

End of the note.

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 and back-end components for your app are already available in this system landscape:

SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP Environment

Configuration of Front-End Server

Configuration of SAP Fiori Infrastructure

Back-End Product Versions (with Minimum Support Package Stack) Supporting the App

  • SAP CRM 7.0 SPS 6 or higher

  • SAP enhancement package 1 for SAP CRM 7.0 SPS 3 or higher

  • SAP enhancement package 2 for SAP CRM 7.0 SPS 1 or higher

Product Version Containing Back-End and Front-End Components of the App

SAP Fiori transactional apps 1.0 for SAP CRM SPS 4

For more information on the installation of the back-end and front-end components of the app, see Installation Information.

For the app, the following software components must be available in your system landscape. These components are contained in the product SAP Fiori transactional apps for SAP CRM:

Back-End/Front-End Server

Back-End/Front-End Component

Technical Name of Software Component

Support Package Level

Back-end server

Back-end component

GBX02CRM 700

03

Front-end server

Front-end component

UIX02CRM 100

03

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 My Opportunities app, the following SAP Notes must be implemented:

Back-End/Front-End Server

SAP Note Number

Description

Back-end server (SPS04)

1997580Information published on SAP site

Employee responsible set as blank

Implementation Tasks

The following sections list tasks that have to be performed to implement the My Opportunities 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 https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/index.html?appId=F0012Information published on SAP site.

Front-End Server : Activate OData Services

Component

Technical Name

OData Service (Version Number)

/sap/opu/odata/sap/CRM_OPPORTUNITY

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

Front-End Server : Activate SAP UI5 Application

Component

Technical Name

SAP UI5 Application

/sap/bc/ui5_ui5/sap/crm_opprtnty

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

The SAP Fiori launchpad is the entry point to SAP Fiori apps. In the launchpad, the user can see and access those Fiori apps that have been assigned by an administrator to the catalog designed for this user's role.

The administrator makes these assignments in the launchpad designer. 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.

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.

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:

OData Service (Version Number)

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

Front-End Server: Authorization Role

/sap/opu/odata/sap/CRM_OPPORTUNITY

SAP_CRM_OPPORTUNITY_APP

Use an existing role or create a new one.

Assign the following authorization roles (PFCG roles) to the users of the app:

Make sure that one of the assigned authorization roles contains the following authorizations:

  • Authorization object S_RFC (Authorization Check for RFC Access), with the following values:

    Field

    Value

    ACTVT

    16

    RFC_NAME

    /IWBEP/FGR_MGW_CLIENT_IF

    RFC_TYPE

    FUGR

  • Authorization object S_RFCACL (Authorization Check for RFC User (e.g. Trusted System))

    There are no predetermined values for this.

Note Note

This task only needs to be done once for all SAP CRM apps, not for each app.

End of the note.

Prerequisites for Implementation

None

Configuration Tasks

To enable My Opportunities, you must perform the following configuration tasks:

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

    Note Note

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

    End of the note.
  • "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 under Start 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 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.