App Extensibility: My Accounts

Use

You can extend My Accounts according to your business needs for different aspects.

Example

To add the time zone to the address information in the General Data form, the following extensibility entities are available on the different layers. You have to extend each of these entities according to your specific business needs:

UI	Back End / ABAP
overview.GeneralData.view.xml	extDisplayFormAddress	CRM_BUPA_ODATA	CRMT_BP_ODATA_ADDRESS_INCL	Superclass: CL_CRM_BP_ODATA_RT_ADDRESS Method: READ_ADDRESSES_FOR_PARTNER

Back End / ABAP

View

Extension Point

Design Time: Gateway Entity

Design Time: Extension Include (in DDIC Structure)

Run Time: Superclass and Method to be Redefined

overview.GeneralData.view.xml

extDisplayFormAddress

CRM_BUPA_ODATA

CRMT_BP_ODATA_ADDRESS_INCL

Superclass: CL_CRM_BP_ODATA_RT_ADDRESS

Method: READ_ADDRESSES_FOR_PARTNER

For more information about extending the My Accounts app, including detailed steps and examples, see the Extension Guide provided with SAP Note 2016653 Information published on SAP site .

Back-End Extensibility

Business Add-Ins (BAdIs)

The following Business Add-In is available for extensibility purposes: CRM_BUPA_ODATA_ENHANCEMENTS.

You can use this BAdI to retrieve the following account-related key figures from the back-end OData layer and deliver them to the app:

Expected revenue of opportunities
Actual revenue (last year, current year)

You can find the BAdI in Customizing for SAP CRM, under Start of the navigation path Customer Relationship Management Next navigation step Master Data Business Partner Settings for "My Accounts" and "My Contacts" Apps BAdI: Retrieval of Data for Account-Related Key Figures End of the navigation path .

With a SAP HANA database, the example implementation CL_CRM_BP_ODATA_EX_FACTSHEET_H is active as a default, and account-related key figures are displayed automatically. You can copy the example implementation and adapt it to your needs as desired. For the actual revenue key figures, this example implementation selects and aggregates the amounts of all sales orders with the status Released or Completed. For the expected revenue of opportunities, it selects all opportunities with status In Process or Open and aggregates the expected revenue. The following authorization check is available: The example implementation selects only the sales orders and opportunities that belong to the sales organization to which the user of the app is assigned as employee responsible. If the user is not assigned to any sales organizations, no sales orders or opportunities are selected.

With any other database, there is no active default implementation, and you must implement this BAdI to be able to see account-related key figures. For this purpose, the example implementation CL_CRM_BP_ODATA_EX_FACTSHEET_L is available. For more information, see the BAdI documentation in Customizing.

Extension Includes

The following extension includes are available:

DDIC Structure	Extension Include	Use
CRMT_BP_ODATA_ACCOUNT	CRMT_BP_ODATA_ACCOUNT_INCL	Accounts
CRMT_BP_ODATA_ADDRESS	CRMT_BP_ODATA_ADDRESS_INCL	Address data
CRMT_BP_ODATA_CLASSIFICATION	CRMT_BP_ODATA_CLASSIFIC_INCL	Classification
CRMT_BP_ODATA_ACC_FACTSHEET	CRMT_BP_ODATA_ACC_FACT_INCL	Factsheet for account
CRMT_BP_ODATA_CONTACT	CRMT_BP_ODATA_CONTACT_INCL	Contacts
CRMT_BP_ODATA_ATTACHMENT	CRMT_BP_ODATA_ATTACHMENT_INCL	Attachments
CRMT_BP_ODATA_NOTE	CRMT_BP_ODATA_NOTE_INCL	Notes
CRMT_BP_ODATA_EMPLOYEE	CRMT_BP_ODATA_EMPLOYEE_INCL	Employees
CRMT_BP_ODATA_RELATIONSHIP	CRMT_BP_ODATA_RELATION_INCL	Relationship
CRMT_BP_ODATA_CUSTOMER	CRMT_BP_ODATA_CUSTOMER_INCL	Customer

If there are additional fields available in the OData service, you can display these fields on the UI. For more information, see the extensibility documentation for the respective SAP NetWeaver release on your front-end server at http://help.sap.com/fiori_implementation Start of the navigation path Extensibility Information for SAP Fiori Next navigation step Extending the UI Layer UI Extensibility Workflow Checking the SAP-Enabled Extension Options Extension Points End of the navigation path .

OData Services

If you use the app in offline mode, the wrapper service CRM_ODATA calls the app-specific OData service CRM_BUPA_ODATA internally. Therefore, if you extend the CRM_BUPA_ODATA service and use the app offline, you must ensure that the wrapper service CRM_ODATA takes these extensions into account.

You register your additional or extended entities in Customizing for SAP CRM, under Start of the navigation path Customer Relationship Management Next navigation step Master Data Business Partner Settings for "My Accounts" and "My Contacts" Apps Register Extensions for CRM OData Service End of the navigation path .

Front-End Extensibility

Extension Points

UI Controller Hooks

For more information about hiding UI controls, see the extensibility documentation for the respective SAP NetWeaver release on your front-end server at http://help.sap.com/fiori_implementation Start of the navigation path Extensibility Information for SAP Fiori Next navigation step Extending the UI Layer UI Extensibility Workflow Checking the SAP-Enabled Extension Options Hiding UI Controls End of the navigation path .

Display of UI Controls

Show Map Icon

Map integration enables users to navigate to third-party map software by clicking a map icon. Since the account address is communicated to this software, you must decide whether or not you want to use map integration and, if you do want to use it, make it active for users by showing the map icon. For more information, see the Extension Guide provided with SAP Note 2016653 Information published on SAP site . SAP does not accept any liability for the use of address data by the map software provider, nor for insecure communication of address data.

Show “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 complete the relevant configuration steps described in App Implementation: My Accounts. This includes showing the Lifecycle Stage field in the app as described in the Extension Guide provided with SAP Note 2016653 Information published on SAP site .

Change Selection Parameters for CRM Transactions

By default, only transactions with an end date within the last two years and in the future are shown in the app. If you want to show transactions for a different timeframe, refer to the Extension Guide provided with SAP Note 2016653 Information published on SAP site

More Information

For a general description of the extensibility options and procedures of SAP Fiori apps, see http://help.sap.com/fiori_implementation Start of the navigation path Extensibility Information for SAP Fiori End of the navigation path .