You can extend the Approve Requisitions app for different aspects. For this purpose, the following extensibility options are available:
Add fields to master list (S2.view.xml)
Add fields to the purchase requisition item overview (if you use the overall approval of purchase requisitions) (S3_header.view.xml)
Add fields to the purchase requisition item details view (if you use overall approval) (ItemDetails.view.xml)
Add fields to the purchase requisition item details view (if you use item-based approval) (S3.view.xml)
Add fields to the service line details view (ItemServiceLine.view.xml)
Add fields to the limit details of service items (Limit.view.xml)
To add customer fields to each work item in the master list, 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 |
Design Time: Name of Entity Set |
Design Time: Extension Include (in DDIC Structure) |
Runtime: BAdI to Be Implemented |
S2.view.xml |
extListItemInfo |
WorkflowTaskCollection |
GBAPPS_PR_WORKFLOW_TASK_INCL |
BAdI: GBAPP_APV_PR_RDP Method: IF_GBAPP_EX_APV_PR_RDP~CHANGE_DATA_WORKFLOW_INBOX_API |
To add customer fields to the header area and to the Information area of the purchase requisition item overview, 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 |
Design Time: Name of Entity Set |
Design Time: Extension Include (in DDIC Structure) |
Runtime: BAdI to Be Implemented |
S3_header.view.xml |
extHeaderInfoOverallRelease |
HeaderDetailCollection |
GBAPPS_PR_HEADER_DETAILS_INCL |
BAdI: GBAPP_APV_PR_RDP Method: IF_GBAPP_EX_APV_PR_RDP~ CHANGE_DATA_HEADER_DETAILS_API |
extInformationOverallRelease |
To add customer fields to the header area and to the Information area of the purchase requisition item details view, 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 |
Design Time: Name of Entity Set |
Design Time: Extension Include (in DDIC Structure) |
Runtime: BAdI to Be Implemented |
ItemDetails.view.xml |
extMaterialHeaderInfo |
HeaderItemDetailCollection |
GBAPPS_PR_ITEM_DETAILS_INCL |
BAdI: GBAPP_APV_PR_RDP Method: IF_GBAPP_EX_APV_PR_RDP~CHANGE_DATA_ITEM_DETAILS_API |
extServiceHeaderInfo |
||||
extInformation |
To add customer fields to the header area and to the Information area of the purchase requisition item details view, 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 |
Design Time: Name of Entity Set |
Design Time: Extension Include (in DDIC Structure) |
Runtime: BAdI to Be Implemented |
S3.view.xml |
extHeaderInfo |
ItemDetailCollection |
GBAPPS_PR_ITEM_DETAILS_INCL |
BAdI: GBAPP_APV_PR_RDP Method: IF_GBAPP_EX_APV_PR_RDP~CHANGE_DATA_ITEM_DETAILS_API |
extInformationS3 |
To add customer fields to the header area of the service line details view, 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 |
Design Time: Name of Entity Set |
Design Time: Extension Include (in DDIC Structure) |
Runtime: BAdI to Be Implemented |
ItemServiceLine.view.xml |
extServiceLineHeaderInfo |
ServiceLineCollection |
GBAPPS_PR_SERVICE_LINE_INCL |
BAdI: GBAPP_APV_PR_RDP Method: IF_GBAPP_EX_APV_PR_RDP~CHANGE_DATA_ITEM_DETAILS_API |
To add customer fields to the header area of the limit details view of a service item, 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 |
Design Time: Name of Entity Set |
Design Time: Extension Include (in DDIC Structure) |
Runtime: BAdI to Be Implemented |
Limit.view.xml |
extServiceLimitHeaderInfo |
LimitCollection |
GBAPPS_PR_LIMITS_INCL |
BAdI: GBAPP_APV_PR_RDP Method: IF_GBAPP_EX_APV_PR_RDP~CHANGE_DATA_ITEM_DETAILS_API |
UI Controller Hooks
To plug in and execute custom code, the following hooks are available in the controller code:
Controller |
Hook |
Use |
---|---|---|
ItemDetails.controller.js |
|
|
Limit.controller.js |
|
|
ItemServiceLine.controller.js |
|
|
S2.controller.js |
|
|
S3.controller.js |
|
|
S3_header.controller.js |
|
|
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:
GBAPP_APV_PR_MDP
You can use this BAdI to enhance the entities, that is, the OData model, of the gbapp_prapproval Gateway service of the Approve Requisitions app. You can do this to add your own fields, for example.
GBAPP_APV_PR_RDP
You can use this BAdI to change the runtime data that is returned by the Gateway service and displayed on the user interface of the Approve Requisitions app. This includes the use of pictures, changing the list of attachments and notes displayed, and changing the workflow. For more information, see the BAdI documentation and the example implementation.
The above described BAdIs are available in Customizing for Materials Management under .
For a general description of the extensibility options and procedures of SAP Fiori apps, see http://help.sap.com/fiori_implementation .