Show TOC

App Implementation: My AccountsLocate this document in the navigation structure

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 basis for the app must be the following:

Required Back-End Product (Product Version Stack)

  • SAP enhancement package 3 for SAP CRM 7.0 (11 (01/2016))
  • SAP enhancement package 4 for SAP CRM 7.0 (01 (01/2016))
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

SAP Fiori 1.0 for SAP CRM ( 09 (01/2016)
  • CRM AS ABAP UI NW731
  • CRM AS ABAP UI NW740
  • CRM AS ABAP UI UI 2.0

UICRM001 100 (0009 )

Back-End Components

  • SAP enhancement package 3 for SAP CRM 7.0 (11 (01/2016))
  • SAP enhancement package 4 for SAP CRM 7.0 (01 (01/2016))
  • CRM Application Server ABAP
  • CRM Application Server ABAP
  • BBPCRM 713 (0011 )
  • SAP_APPL 617 (0001 )

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

System Landscape Requirements

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

1931619 Information published on SAP site

not available

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

SAP Note Number

Description

1931619 Information published on SAP site

not available

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:

https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/index.html?appId=F0002

Front-End Server : Activate OData Services

Component

Technical Name

OData Service (Version Number)

  • CRM_BUPA_ODATA/ (001 )
  • ERP_BUPA_ODATA/ (001 )

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

Front-End Server: Activate SAPUI5 Application

Component

Technical Name

SAPUI5 Application

CRM_MYACCOUNTS

For more information about how to activate the SAPUI5 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 proceed 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

  • CRM_BUPA_ODATA/ (001 )
  • ERP_BUPA_ODATA/ (001 )

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

  • SAP_CRM_MYACCOUNTS_APP

  • Not applicable

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 currency

    Define the currency in which revenue key figures and the expected sales volume of opportunities are displayed.

    You do this in Customizing for SAP CRM, under Start of the navigation path Customer Relationship Management Next navigation step Master Data Next navigation step Business Partner Next navigation step Settings for "My Accounts" and "My Contacts" Apps Next navigation step Define Settings for Business Partner OData Services End of the navigation path.

    For more information, see the documentation for this Customizing activity.

  • Configure identification of users' accounts for display in the "My Accounts" view

    You can define a user’s accounts as either of the following:

    • Accounts for which the user is employee responsible

      Ensure that each user who has access to the My Accounts app is assigned to a business partner with the Employee business partner role.

    • Accounts for which specified relationship categories exist (with back-end product version SAP enhancement package 3 for SAP CRM 7.0)

      Specify the relationship categories in Customizing for SAP CRM, under Start of the navigation path Customer Relationship Management Next navigation step Master Data Next navigation step Business Partner Next navigation step Settings for "My Accounts" and "My Contacts" Apps Next navigation step Define the Determination of Users' Accounts End of the navigation path

      For more information, see the documentation for this Customizing activity.

  • (Optional) Configure account life cycle and display “Lifecycle Stage” field

    Users can create accounts as prospects and record the lifecycle stage of accounts, using the Lifecycle Stage in the General Data view. To use the lifecycle feature, you need to do the following:

    • Define the lifecycle as described in Customizing for SAP CRM, under Start of the navigation path Customer Relationship Management Next navigation step Master Data Next navigation step Business Partner Next navigation step Define Basic Settings for Account Life Cycle End of the navigation path.
      Note You only need to make the settings described in step 1 of the documentation for this Customizing activity.
    • Show the Lifecycle Stage field in the app as described in the Extension Guide provided with SAP Note 2016653 Information published on SAP site.

  • Retrieve data for account-related key figures

    You use the Business Add-In (BAdI) CRM_BUPA_ODATA_ENHANCEMENTS for this. For more information, see App Extensibility: My Accounts.

  • Configure notes

    To display notes in the My Accounts app, you must configure the text object BUT000 so that texts are displayed in the notes log. BUT000 is the text object used for business partner texts.

    In Customizing for SAP CRM, under Start of the navigation path Customer Relationship Management Next navigation step Basic Functions Next navigation step Text Management Next navigation step Define Text Determination Procedure End of the navigation path, define the default text determination procedure for text object BUT000 as follows:

    Text Type

    Text Changes

    <text type specified in Customizing activity Define Settings for Business Partner OData Services (see above)>

    P (Log)

    If this text type is not set to P, only the latest note is displayed in the My Accounts app, with each new note replacing the old one. There is no log of all notes.

    <custom text type used to display the notes log>

    R (Display Log)

    Example

    If you are using the default text type 0001 Correspondence, proceed as follows:

    1. In Customizing for SAP CRM, under Start of the navigation path Customer Relationship Management Next navigation step Basic Functions Next navigation step Text Management Next navigation step Define Text Determination Procedure End of the navigation path, select text object BUT000 and, in the tree on the left-hand side, choose Definition of Procedure.

    2. In the Determine Work Area: Entry dialog box, make sure that text object BUT000 and text determination procedure DEFAULT are entered and confirm.

    3. On the Definition of Procedure screen, set the Changes field of text type 0001 Correspondence to P.

    4. On the same screen, set the Changes field of the text type that you want to use to display the notes log, to R.

  • (Optional) Make settings to optimize performance

    With back-end product version SAP enhancement package 3 for SAP CRM 7.0, you can improve performance by deactivating the following system behavior:

    • Exclusion of employees from the account search

    • Formatting of names when international address versions are defined in the business partner master data in SAP CRM

    • Searching for accounts by checking for the search string anywhere in the account name

    You do this in Customizing for SAP CRM, under Start of the navigation path Customer Relationship Management Next navigation step Master Data Next navigation step Business Partner Next navigation step Settings for "My Accounts" and "My Contacts" Apps Next navigation step Define Settings for Business Partner OData Services End of the navigation path.

  • (Optional) Configure images

    To deliver logos to the My Accounts app, you must store the files in the back-end system as attachments in the master data of the accounts or account groups. In the Attachments assignment block of each account or account group, make the following settings under Advanced Properties:

    • Select the Default Document checkbox.

    • Select the document type BDS_IMAGE.

    Note

    The aspect ratio of the image must be 1:1.

  • (Optional) Configure Microsoft Internet Explorer to upload files larger than 4MB

    See SAP Note 2041225 Information published on SAP site.

  • (Optional) Configure SAP Jam integration

    For more information about SAP Jam configuration, see SAP Library for user interface add-on for SAP NetWeaver on SAP Help Portal at http://help.sap.com/nw-uiaddon. Under Application Help, open the SAP Library and choose Social Media Integration.

Additional Tasks for Configuring and Installing the App for Offline Use

If you want to deploy the app for offline use, you need to implement and configure it, then package it for installation on mobile devices. For more information about packaging, see Preparing SAP Fiori Apps for Offline Use.

In step 2 of the process described in "Preparing SAP Fiori Apps for Offline Use", provide at least the following properties in the property array applications of the appConfig.js file:

Property

Value for My Accounts

Value for Reuse Library

id

cus.crm.myaccounts

sap.cus.crm.lib.reuse

title

My Accounts

-

url

/sap/bc/ui5_ui5/sap/crm_myaccounts

/sap/bc/ui5_ui5/sap/crm_lib_reuse/sap/cus/crm/lib/reuse

intent

Account-MyAccounts

-

reuse

-

true

scenario

-

true

Note

To provide common UI elements, you have to include the reuse library in each package that contains SAP CRM apps.

If you use the user interface add-on 2.0 for SAP NetWeaver on the front-end server, do not provide the following properties:
  • title
  • url
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.