You can extend Approve Trading Contracts according to your business needs for different aspects. For this purpose, the following extensibility options are available:
You can add custom fields at defined extension points.
You can add custom tabs to the icon tab bar at defined extension points.
You can manipulate the standard model at predefined UI controller hooks.
You can enhance the functionality by implementing predefined Business Add-Ins.
You can include custom fields via extension includes.
Extension Points
If there are additional fields available in the OData service, you can display those fields on the UIs. Therefore you can use the following extension points:
For the master screen
Extension Point |
Use |
---|---|
extMoreObjectHeaderAttributes |
Adds additional attributes to the object header of the master screen |
For the detail screen (view name S2.view.xml)
Extension Point |
Use |
---|---|
extMoreObjectHeaderAttributes |
Adds additional attributes to the object header of the detail screen |
extInfoTabForm |
Adds additional fields to the info tab inside the form (Extends the info tab inside existing <form: content> |
extInfoTab |
Adds additional fields to the info tab outside the form (Extends the info tab outside existing <form: content>) |
extMoreIconTabFilters |
Adds new filters to the icon tab bar |
extMoreTCItemListColumns |
Adds new columns to the trading contract item list |
extMoreTCItemListCells |
Adds new cells to the trading contract item list |
extMoreData |
Adds more data to the detail screen |
For the sub detail screen (view name S3.view.xml)
Extension Point |
Use |
---|---|
extMoreObjectHeaderAttributes |
Adds additional attributes to the object header of the sub detail screen |
extMoreInfo |
Adds additional fields to the information section on sub detail screen |
extMoreInfoDelivery |
Adds additional fields to the delivery section on sub detail screen |
extMoreInfoAccounting |
Adds additional fields to the accounting section on sub detail screen |
extMoreSalesConditionsColumns |
Adds columns to the sales condition table on sub detail screen |
extMoreSalesConditionsCells |
Adds cells to the sales condition table on sub detail screen |
extMorePurchaseConditionsColumns |
Adds columns to the purchase condition table on sub detail screen |
extMorePurchaseConditionsCells |
Adds cells to the purchase condition table on sub detail screen |
extMoreData |
Adds additional fields to the sub detail screen |
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, you can use the following UI controller hooks:
Hook |
Use |
---|---|
extHookAddOrChangeSortOptions |
Allows you to add new sort options or change the predefined sort options The system calls this method within the initialization of the UI. |
extHookGetSorterForSortOptions |
Needs to be implemented for new or changed sort options to return the corresponding sort objects The system calls this method when you choose the sort option on the UI. |
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 .
Business Add-Ins (BAdIs)
The following BAdIs are available for extensibility purposes:
TCAPPROVAL_BADI_FIELD_EXTEND – BAdI: TC Approval App Field Extension
You can use this BAdI to enhance the list of fields used during the approval processes in the OData service for the app.
TCAPPROVAL_BADI_FUNC_CHECK – BAdI: TC Approval App Check Function Import
You can use this BAdI to enhance the check of approval and rejection events, and to skip the standard process triggered from the app in the OData service.
These BAdIs are available in Customizing under
.Extension Includes
You can add custom fields to database structures in your back-end system:
Extension Includes |
Use |
---|---|
WB2_S_COND_PURCH_ENH |
Adds custom fields related to purchase conditions |
WB2_S_COND_SALES_ENH |
Adds custom fields related to sales conditions |
WB2_S_FORWARDING_AGENT_ENH |
Adds custom fields related to the forwarding agent |
WB2_S_TCHEADER_ENH |
Adds custom fields related to the trading contract header |
WB2_S_TCITEMDETAIL_ENH |
Adds custom fields related to the trading contract item detail |
WB2_S_TCITEMGENERAL_ENH |
Adds custom fields related to the trading contract item general |
WB2_S_WORKITEM_ENH |
Adds custom fields related to the worklist |
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 .
In addition, you can use the following extensibility options:
You can hide all UI controls which have a tag ID assigned.
You can display custom texts on the UI by replacing the i18-file.
You can hide a standard application view and add a custom view.
You can use custom OData services by enhancing existing OData services with the service builder.
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 .