Show TOC

App Implementation: My Tasks 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 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.

Configuration Tasks

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

  • Define transaction type and text types

    • In Customizing for SAP CRM, define which transaction type and text types the system should use for tasks that are created, displayed, or edited from the My Tasks app.

      You find this setting in Customizing for SAP CRM under Start of the navigation path Customer Relationship Management Next navigation step Transactions Next navigation step Settings for Activities Next navigation step Define Settings for "My Tasks" App End of the navigation path

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

      Authorization Role (PFCG Role)

      Description

      SAP_CRM_MYTASKS_APP

      Role that contains only the technical access to the OData service necessary for running the app

      SAP_CRM_UIU_SLS_PROFESSIONAL or another role

      Role that covers authorizations for the business objects accessed by the app

      • 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 This step is required once for all SAP CRM apps, not once per app.
  • Assign "Employee" business partner role

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

  • Remove "Mandatory" tag for account and contact

    In the app, the Account and Contact fields are not mandatory; however, they are mandatory in the standard delivery of the CRM WebClient UI. This means that tasks that were created in the app, and to which no accounts or contacts were assigned, cannot be changed in the CRM back end without subsequently assigning an account or contact to them.

    To prevent this, in the UI configuration tool in the CRM back end (transaction BSP_WD_CMPWB), copy the configuration of the task details page, and remove the Mandatory tag for the Account and Contact fields.

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.