App Implementation: My Accounts

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	04
Front-end server	Front-end component	UIX02CRM 100	04

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

Back-End/Front-End Server	SAP Note Number	Description
Front-end server	2009161	Corrections for SAP Fiori CRM My Accounts App

Implementation Tasks

The following sections list tasks that have to be performed to implement the My Accounts 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 (1)

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	CRM_MYACCOUNTS

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 Roles with OData Service Authorization 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:

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. For more information, see Back-End Server: Assign OData Service Authorization to Users.
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. For more information, see Add Start Authorizations for OData Services to Role on Front-End and Front-End Server: Assign Roles to Users.

OData Service (Version Number)	Back-End Server: Delivered Authorization Role (PFCG Role)	Front-End Server: Assignment to Authorization Role
CRM_BUPA_ODATA (1)	OData service authorization is included in the example role SAP_CRM_MYACCOUNTS_APP. Note In addition, this role contains authorizations to display the related business data. End of the note.	OData service authorization must be assigned.

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.

Field	Value
ACTVT	16
RFC_NAME	/IWBEP/FGR_MGW_CLIENT_IF
RFC_TYPE	FUGR

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

There are no prerequisites for implementing the My Accounts app.

Configuration Tasks

To be able to implement the app, you must perform the following configuration tasks:

Configure images (optional)
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.

End of the note.
Define currency
The currency in which revenue key figures and the expected sales volume of opportunities are displayed is defined as follows:

If the standard user parameter for currency (FWS) is set, the currency used is always that of the user parameter. Otherwise the default currency used is USD.
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 Microsoft Internet Explorer to upload files larger than 4MB (optional)
See SAP Note 2041225.
Configure SAP Jam integration (optional)
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.

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.