App Extensibility: My Tasks

Use

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

Example

To add a field on the task create view, 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 (in DDIC Structure)	Run Time: Superclass and Method to be Redefined
S4.view.xml	extTaskOverview	Task	CRMS_TASK_ODATA_INCL	CRMS_TASK_ODATA

For more information about extension hooks and extension points for the My Tasks app, visit the SAP Fiori apps reference library at https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/index.html?appId=F0003.

Note To display the extensibility information about the My Tasks app in the SAP Fiori apps reference library, click the IMPLEMENTATION INFORMATION tab on the App Details page that is displayed.

Back-End Extensibility

Business Add-Ins (BAdIs)

The following BAdI is available for extensibility purposes:

CRM_TASK_ODATA_BD in enhancement spot CRM_TASK_ODATA_ENH

You can use this BAdI to define your own logic for reading, creating, or changing tasks. This is necessary if, for example, you want to add your own fields, or use different processing logic for existing fields.

You call the BAdI by using transaction SE18.

OData Services

When you use the My Tasks app in offline mode, the wrapper service CRM_ODATA calls the app-specific OData service CRM_BUPA_ODATA internally. If you extend this service and use the app offline, you must ensure that the wrapper service CRM_ODATA takes your extensions into account.

Register your additional or extended entities in Customizing for SAP CRM, under Start of the navigation path Customer Relationship Management Next navigation step Transactions Settings for Activities Define Settings for"My Tasks" and"My Appointments" Apps Register Extensions for CRM OData Service End of the navigation path .

The CRM_ODATA service is available as of the following backend releases:

SAP enhancement package 4 (SP02) for SAP CRM 7.0
SAP enhancement package 3 (SP12) for SAP CRM 7.0

Front-End Extensibility

Extension Points

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

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

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 .