Extensibility information for SAP Fiori app.
You can add new criteria to filter opportunities for display, for example, to view the top n opportunities.
You can add new criteria to filter opportunities by their attributes. For example, user status or sales stage.
You can add new standard or custom fields to view additional details of an opportunity.
To add new selection criteria to the dropdown, the following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs:
UI |
Back End/ABAP |
|||
---|---|---|---|---|
View |
Extension Point |
Design Time: Gateway Entity |
Design Time: Extension Include |
Run Time: Superclass and Method to Be Redefined |
S1.view.xml |
extDropDown |
Opportunity |
CRMT_ODATA_SPS_OPP_EXPAND_INCL |
CL_CRM_SALESPIPELINE_S_DPC_EXT |
To add new selection criteria to filter opportunities, the following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs:
UI |
Back End/ABAP |
|||
---|---|---|---|---|
View |
Extension Point |
Design Time: Gateway Entity |
Design Time: Extension Include |
Run Time: Superclass and Method to Be Redefined |
S1.view.xml |
extDropDown |
Opportunity |
CRMT_ODATA_SPS_OPP_EXPAND_INCL |
CL_CRM_SALESPIPELINE_M_DPC_EXT |
To add new fields to the popover, the following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs:
UI |
Back End/ABAP |
|||
---|---|---|---|---|
View |
Extension Point |
Design Time: Gateway Entity |
Design Time: Extension Include |
Run Time: Superclass and Method to Be Redefined |
Opportunity.fragment.xml |
extOpportunityPopover (to add fields at the beginning) |
Opportunity |
CRMT_ODATA_SPS_OPP_EXPAND_INCL |
CL_CRM_SALESPIPELINE_M_DPC_EXT |
extOpportunityPopoverEnd (to add fields at the end) |
Business Add-Ins (BAdIs)
The following Business Add-Ins are available for extensibility purposes:
<BAdI Name 1> (<Technical name>)
You can use this BAdI to...
Extension Includes
In addition to the extension includes described above, the following extension includes are available:
DDIC |
Extension Include |
Use |
---|---|---|
CRMT_ODATA_SPS_OPPT_HEADER_MGR |
CRMT_ODATA_SPS_OPT_HEADER_INCL |
Allows you to extend the Opportunity entity |
CRMT_ODATA_SPS_OPPORT_SALESTG |
CRMT_ODATA_SPS_SALESTG_INCL |
Allows you to extend the Sales Stage entity |
CRMT_ODATA_SPS_ACCOUNTS |
CRMT_ODATA_SPS_ACCOUNTS_INCL |
Allows you to extend the Account entity |
CRMT_ODATA_SPS_CURRENCY |
CRMT_ODATA_SPS_CURRENCY_INCL |
Allows you to extend the Currency entity |
CRMT_ODATA_SPS_DATE_RANGES |
CRMT_ODATA_SPS_DATE_RANGE_INCL |
Allows you to extend the Date Range entity |
CRMT_ODATA_SPS_EMP_RESP |
CRMT_ODATA_SPS_EMP_RESP_INCL |
Allows you to extend the Employee Responsible entity |
CRMT_ODATA_SPS_OPPORT_STATUS |
CRMT_ODATA_SPS_STATUS_INCL |
Allows you to extend the Status entity |
CRMT_ODATA_SPS_OPPORT_TEAM |
CRMT_ODATA_SPS_OPPRT_TEAM_INCL |
Allows you to extend the Team entity |
CRMT_ODATA_SPS_SETTINGS_MGR |
CRMT_ODATA_SPS_SETTINGS_INCL |
Allows you to extend the Settings entity for the app |
CRMT_ODATA_SPS_USRSTATUS_CODES |
CRMT_ODATA_SPS_USR_STATUS_INCL |
Allows you to extend the Opportunity Status Code entity |
CRMT_ODATA_SPS_OPPORT_EXPAND |
CRMT_ODATA_SPS_OPP_EXPAND_INCL |
Allows you to retrieve information about related entities, based on your requirement |
CRMT_ODATA_SPS_OPP_SALESTARGET |
CRMT_ODATA_SPS_OPP_ST_INCL |
Allows you to extend the Organization Sales Target entity. |
For more information about extension includes, see the extensibility documentation for the respective SAP NetWeaver release on your front-end server at http://help.sap.com/fiori_implementation .
Extension Points
For <business case>, for example, the following extension points are available:
View |
Extension Point |
Use |
---|---|---|
<DDIC> |
<Extension point> |
|
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 .
UI Controller Hooks
To plug in and execute custom code to <business case>, for example, the following hooks are available in the controller code:
Controller |
Hook |
Use |
---|---|---|
S1.controller.js |
extHookAddViews |
Allows you to add additional views to display the direct results of the Sales Pipeline when the view is selected. This is called when you select a value from the drop-down list for VIEWS. @return {void} |
S1.controller.js |
extHookOpportunityPopover |
Allows you to set the data to additional fields that you want to display directly. This is called when you select the bubble in the Sales Pipeline. @return {void} |
S1.controller.js |
extHookAddFacetFilter |
Allows you to add additional filters to perform analysis on the Manager's Sales Pipeline. This is called when you select the Facet Filter button on the top-right. @return {void} |
If there are additional UI controller hooks available in the controller code, you can add own code. 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 .
Display of UI Controls
As an example, the following UI controls can be hidden from the app UI:
View |
Control ID |
Use |
---|---|---|
<View> |
<Control ID> |
|
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 .
For a general description of the extensibility options and procedures of SAP Fiori apps, see http://help.sap.com/fiori_implementation .