App Extensibility: My Travel and Expenses

Use

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

UI Extension

To add a customer field to the app, 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 Name / Purpose	Design Time: Gateway Entity	Runtime: Superclass
DuplicateDialog	topDuplicateDialog / Dialog for duplicate of expense report - top belowDuplicateDialogInfo / Dialog for duplicate of expense report - below information bottomDuplicateDialog / Dialog for duplicate of expense report - below duplicate	SAP_FIN_TE_CRE_APP	Superclass: IF_PAOC_MY_TRAVEL_EXPENSES
GenericClaim	topExpenseDetails / Expense Details - top processing belowExpenseCostAssignment / Expense Details - cost assignment bottomExpenseDetails / Expense Details - below processing topExpenseAttachments / Expense Details - top attachment handling bottomExpenseAttachments / Expense Details - below attachment handling belowExpenseItemTotal / Expense Details - below total bottomExpenseItems / Expense Details - below	SAP_FIN_TE_CRE_APP	Superclass: IF_PAOC_MY_TRAVEL_EXPENSES
MileageClaim	topMileageDetails / Mileage expense details - top processing mileage belowMileageDestinations/ Expense Details - below Destinations Mileage belowMileageCostAssignments / Expense Details - below cost assignment bottomMileageDetails / Mileage Expense Details - below processing mileage topMileageVehicle / Expense Details - top vehicle processing bottomMileageVehicle / Mileage Expense Details - below vehicle processing	SAP_FIN_TE_CRE_APP	Superclass: IF_PAOC_MY_TRAVEL_EXPENSES
PerDiemClaim	topPerDiem / Per Diem Deductions - top processing belowPerDiemAmount / Per Diem Deductions - below Amount processing	SAP_FIN_TE_CRE_APP	Superclass: IF_PAOC_MY_TRAVEL_EXPENSES
S3	topReportReadOnlyDetail / Read Only View Expense Report Header - top processing belowReportReadOnlyDetailDates / Read Only View Expense Report Header - below detail dates belowReportReadOnlyDetailDestinations / Read Only View Expense Report Header - below detail destinations belowReportReadOnlyDetailTypes / Read Only View Expense Report Header - below detail types belowReportReadOnlyDetailComment / Read Only View Expense Report Header - below detail comment belowReportReadOnlyDetailCostAssignments / Read Only View Expense Report Header - below cost assignment bottomReportReadOnlyDetail / Read Only View Expense Report Header - below details	SAP_FIN_TE_CRE_APP	Superclass: IF_PAOC_MY_TRAVEL_EXPENSES
S4	topReportDetail / Expense Report Header - top details belowReportDetailDates / Expense Report Header - below dates belowReportDetailDestinations / Expense Report Header - below destinations belowReportDetailTypes / Expense Report Header - below detail types belowReportDetailComment / Expense Report Header - below detail comment belowReportDetailCostAssignments / Expense Report Header - below cost assignment bottomReportDetail / Expense Report Header - below details topReportAttachments / Expense Report Header - top attachments belowReportAttachments / Expense Report Header - below attachments topReportExpenses / Expense Report Header - top expenses belowReportExpenseTotal/ Expense Report Header - top expenses total bottomReportExpenses / Expense Report Header - below expenses	SAP_FIN_TE_CRE_APP	Superclass: IF_PAOC_MY_TRAVEL_EXPENSES
S6	topBorderCrossingLeaving / Border Crossing Details - top leaving bottomBorderCrossingLeaving / Border Crossing Details - below leaving topBorderCrossingReturn / Border Crossing Details - top return bottomBorderCrossingReturn / Border Crossing Details - below return	SAP_FIN_TE_CRE_APP	Superclass: IF_PAOC_MY_TRAVEL_EXPENSES
S7	topDestinationAddress / Destination Details (main and additional) - top address bottomDestinationAddress/ Destination Details (main and additional) - below address topDestinationDetails / Destination Details (main and additional) - top destinations bottomDestinationDetails / Destination Details (main and additional) - below destinations	SAP_FIN_TE_CRE_APP	Superclass: IF_PAOC_MY_TRAVEL_EXPENSES
S8	topExpenseAddress / Address Details for Expenses - before address bottomExpenseAddress / Address Details for Expenses - below address	SAP_FIN_TE_CRE_APP	Superclass: IF_PAOC_MY_TRAVEL_EXPENSES
S9	topExpenseItemDetails / Item Details for Expenses - before the expense details bottomExpenseItemDetails / Item Details for Expenses - at bottom of the expense details	SAP_FIN_TE_CRE_APP	Superclass: IF_PAOC_MY_TRAVEL_EXPENSES
SubmitDialog	topSubmitDialog / Submit Dialog for Expense Report - top belowSubmitDialogApprover / Submit Dialog for Expense Report - below the submit dialog approver bottomSubmitDialog / Submit Dialog for Expense Report - at the bottom of the submit dialog	SAP_FIN_TE_CRE_APP	Superclass: IF_PAOC_MY_TRAVEL_EXPENSES
StartDateDialog	topStartDateDialog / Dialog for managing overlapping Expense Reports - top dialog belowStartDateDialogInputTime / Dialog for managing overlapping Expense Reports - below time input bottomStartDateDialog / Dialog for managing overlapping Expense Reports - below start date	SAP_FIN_TE_CRE_APP	Superclass: IF_PAOC_MY_TRAVEL_EXPENSES
ChangeRatePopover	topChangeRatePopover / Change Rate Popover – before content bottomChangeRatePopover / Change Rate Popover – after content	SAP_FIN_TE_CRE_APP	Superclass: IF_PAOC_MY_TRAVEL_EXPENSES

Additional Extensibility Entities

Business Add-Ins (BAdIs)

The following BAdIs are available for extensibility purposes:

PAOC_MY_TRAVEL_EXPENSES_BADI

You can use this BAdI to extend the data model used by the app to include or remove fields.

UI Controller Hooks

To plug in and execute custom code, the following hooks are available in the controller code:

Controller	Hook	Use
GenericClaim.controller.js	extHookOnDataReceived	This hook will be called just before the context is set on the view. Customers will have all the required information for acting on the data or the view before the binding mechanism is applied .
MileageClaim.controller.js	extHookOnDataReceived	This hook will be called just before the context is set on the view. Customers will have all the required information for acting on the data or the view before the binding mechanism is applied.
PerDiemClaim.controller.js	extHookOnDataReceived	This hook will be called just before the context is set on the view. Customers will have all the required information for acting on the data or the view before the binding mechanism is applied.
S2.controller.js	extHookOnDataReceived	This hook will be called just before the context is set on the view. Customers will have all the required information for acting on the data or the view before the binding mechanism is applied.
S3.controller.js	extHookOnDataReceived	This hook will be called just before the context is set on the view. Customers will have all the required information for acting on the data or the view before the binding mechanism is applied.
S4.controller.js	extHookOnDataReceived	This hook will be called just before the context is set on the view. Customers will have all the required information for acting on the data or the view before the binding mechanism is applied.
S5.controller.js	extHookOnDataReceived	This hook will be called just before the context is set on the view. Customers will have all the required information for acting on the data or the view before the binding mechanism is applied.
S6.controller.js	extHookOnDataReceived	This hook will be called just before the context is set on the view. Customers will have all the required information for acting on the data or the view before the binding mechanism is applied.
S7.controller.js	extHookOnDataReceived	This hook will be called just before the context is set on the view. Customers will have all the required information for acting on the data or the view before the binding mechanism is applied.
S8.controller.js	extHookOnDataReceived	This hook will be called just before the context is set on the view. Customers will have all the required information for acting on the data or the view before the binding mechanism is applied.
S9.controller.js	extHookOnDataReceived	This hook will be called just before the context is set on the view. Customers will have all the required information for acting on the data or the view before the binding mechanism is applied.

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 .

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 .