My Notes

Extensibility information for SAP Fiori app.

You can extend the app according to your business needs for different aspects. For this purpose, the following extensibility options are available:

You can add new customer fields and controls to the detailed view (S3 view) of notes and note sections or change or replace the standard content. You can for example change the default creation and change date of a note or add an additional customer field (such as priority). You can change the standard layout of the note sections as a whole or you can change or extend this within specific sections.
You can display or hide standard fields in the list view (S2 view), extend controls or change or replace the standard content. You can for example change the default attributes displayed (note title and creation and change date) for items in the notes list.
You can change the default buttons and actions in the footer toolbar or add customer-specific buttons and actions to this toolbar (see Toolbar).
You can add new customer actions or change the default actions available on the Add To dialog box. You can for example support the inclusion of notes for other business transactions (opportunities are supported in the standard system).

Extensibility of the Detailed View

To change the detailed view of the notes and the sections they contain, 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
View	Extension Point	Design Time: Gateway Entity	Design Time: Extension Include	Run Time: Superclass and Method to Be Redefined
S3.view.xml	noteDetailExtension	NoteHeader	No include available	CRM_S_NOTE_HEADER (No standard enhancement available)
	noteSectionContentExtension	NoteSection	CRM_S_NOTE_SECTION_EXT	CRM_S_NOTE_SECTION
	noteSectionListExtension (Overwrite standard content)
	noteSectionItemExtension (Overwrite standard content)

Extensibility of the List View

To change the list view of notes and the items it contains, 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
S2.view.xml	noteAttributeExtension	NoteHeader	No include available	CRM_S_NOTE_HEADER (No standard enhancement available)
noteItemExtension (Overwrite standard content)	No include available

Back End/ABAP

View

Extension Point

Design Time: Gateway Entity

Design Time: Extension Include

Run Time: Superclass and Method to Be Redefined

S2.view.xml

noteAttributeExtension

NoteHeader

No include available

CRM_S_NOTE_HEADER

(No standard enhancement available)

noteItemExtension

(Overwrite standard content)

No include available

Extensibility of the Footer Toolbar

To change the footer toolbar and the buttons and the actions it contains, 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
S3.view.xml	Extensibility of hooks delivered with the standard system — see section UI Controller Hooks
S2.view.xml	Extensibility of hooks delivered with the standard system — see section UI Controller Hooks

Back End/ABAP

View

Extension Point

Design Time: Gateway Entity

Design Time: Extension Include

Run Time: Superclass and Method to Be Redefined

S3.view.xml

Extensibility of hooks delivered with the standard system — see section UI Controller Hooks

S2.view.xml

Extensibility of hooks delivered with the standard system — see section UI Controller Hooks

Extensibility of the Add To Dialog Box

To change the list page (entry page with selection of business transaction categories) and the item page (detail page with items for a business transaction category) on the Add To dialog box, 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
View	Extension Point	Design Time: Gateway Entity	Design Time: Extension Include	Run Time: Superclass and Method to Be Redefined
AddToDialog.fragment.xml	addToPageExtension	No reference to the back end
	addToItemExtension	No reference to the back end
	addToOpportunityExtension (Overwrite standard content)	No reference to the back end
	addToOpportunityItemExtension (Overwrite standard content)	Opportunity	CRMT_ODATA_OPPT_HEADER_INCL	CRM_S_NOTES_OPPT
	addToOpportunityListExtension (Overwrite standard content)	Opportunity	CRMT_ODATA_OPPT_HEADER_INCL	CRM_S_NOTES_OPPT

Further Extensibility Entities

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
<DDIC>	<Extension include>

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 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 Includes End of the navigation path .

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 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 .

UI Controller Hooks

To extend the functions in the footer toolbar, the following hooks are available in the controller code:

Controller	Hook	Use
S2.controller.js	extHookGetHeaderFooterOptions	You can extend the footer toolbar functions in the list view, for example the sorting of the list in the attribute oSortOptions.
S3.controller.js	extHookGetHeaderFooterOptions	You can add customer-specific functions to the footer toolbar functions in the detailed view.

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 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 UI Controller Hooks End of the navigation path .

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 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 .

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 .