You can extend Approve Travel Requests according to your business needs for different aspects. For this purpose, the following extensibility options are available:
Extension Points
UI Controller Hooks
BAdIs
Extension Points
To extend Approve Travel Requests, you can use the following extension points:
Name: extInfoAdditionalData
Location: Details.view.xml
Purpose: Add information below the additional data
Name: extTabs
Location: Details.view.xml
Purpose: Add a new tab to the tab container
Name: extAdditionalTravelRequestInformation
Location: Details.view.xml
Purpose: Add additional travel request information above the cost assignment
Name: extEstimatedCostsTable
Location: EstimatedCost.fragment.xml
Purpose: Add information above the estimated costs
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, the following hooks are available in the controller code:
Controller |
Hook |
Use |
---|---|---|
Details.controller.js |
additionalButtons |
Allows you to add buttons to the footer toolbar. |
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 .
BAdIs
SRA009_BADI_APV_TRAVEL_REQ
You can use this BAdI to adapt the travel request information shown in the approval.
For a general description of the extensibility options and procedures of SAP Fiori apps, see http://help.sap.com/fiori_implementation .