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:
SAP Fiori System Landscape Setup | 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) |
|
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.
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 ( 10 (07/2016) ) |
|
UICRM001 100 (0010 ) |
Back-End Components |
|
|
BBPCRM 713 (0002 ) |
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.
On the back-end server, the following SAP notes must be implemented for this app:
SAP Note Number |
Description |
---|---|
not available |
not available |
On the front-end server, the following SAP notes must be implemented for this app:
SAP Note Number |
Description |
---|---|
not available |
not available |
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=F0004Front-End Server : Activate OData Services
Component |
Technical Name |
---|---|
OData Service (Version Number) |
CRM_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_MYCONT |
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.
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.
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 ) |
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. |
To be able to implement the app, you must perform the following configuration tasks in the back-end system:
Configure identification of users' accounts for determining users' contacts
You can define a user’s accounts as being either of the following:
Accounts for which the user is employee responsible
Ensure that each user who has access to the My Contacts app is assigned to a business partner with the Employee business partner role.
Accounts for which specified relationship categories exist
Specify the relationship categories in Customizing for SAP CRM, under
For more information, see the documentation for this Customizing activity.
Configure notes
To display a contact’s notes in the My Contacts 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 BUT000 as follows:
, define the default text determination procedure for text object
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 Contacts 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) |
If you are using the default text type 0001 Correspondence, proceed as follows:
In Customizing for SAP CRM, under BUT000 and, in the tree on the left-hand side, choose Definition of Procedure.
, select text objectIn the Determine Work Area: Entry dialog box, make sure that text object BUT000 and text determination procedure DEFAULT are entered and confirm.
On the Definition of Procedure screen, set the Changes field of text type 0001 Correspondence to P.
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) Activate creation of contacts with role "Contact Person" automatically assigned
You make this setting in Customizing for SAP CRM, under
.(Optional) Define text type
In Customizing for SAP CRM, define the text type to be used for the notes section of the contact information.
You do this in Customizing for SAP CRM, under
.For more information, see the documentation for this Customizing activity.
(Optional) Configure images
To deliver photos to the My Contacts app, you must store the files in the back-end system as attachments in the master data of the contacts. In the Attachments assignment block of each contact, make the following settings under Advanced Properties:
Select the Default Document checkbox.
Select the document type BDS_IMAGE.
The aspect ratio of the image must be 1:1.
(Optional) Optimize performance by deactivating name formatting
You can improve performance by deactivating the formatting of names when international address versions are defined in the business partner master data in SAP CRM.
You do this in Customizing for SAP CRM, under
.(Optional) Configure Microsoft Internet Explorer to upload files larger than 4MB
See SAP Note 2041225 .
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.
Property |
Value for My Contacts |
Value for Reuse Library |
---|---|---|
id |
cus.crm.mycontacts |
sap.cus.crm.lib.reuse |
title |
My Contacts |
- |
url |
/sap/bc/ui5_ui5/sap/crm_mycont |
/sap/bc/ui5_ui5/sap/crm_lib_reuse/sap/cus/crm/lib/reuse |
intent |
ContactPerson-MyContacts |
- |
reuse |
- |
true |
scenario |
- |
true |
title
url
For more information about app implementation, see http://help.sap.com/fiori_implementation .