You can extend the Approve Purchase Orders app according to your business needs for different aspects. For this purpose, the following extensibility options are available:
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 |
Design Time: Gateway Entity |
Design Time: Extension Include (in DDIC Structure) |
Runtime: Superclass/ Method to Be Redefined |
S2.View.xml |
CustomerExtensionForSearchList |
SRM_PURCHASEORDER |
SRMPO_S_PO_WORKFLOW_TASK_INCL |
Superclass: CL_SRM_PURCHASEORDER_API Method:GET_PO_FROM_WI |
UI |
Back End/ABAP |
|||
---|---|---|---|---|
View |
Extension Point |
Design Time: Gateway Entity |
Design Time: Extension Include (in DDIC Structure) |
Runtime: Superclass/ Method to Be Redefined |
S3.View.xml |
CustomerExtensionFor Header |
CustomerExtensionFor Header |
SRMPO_S_HEADER_DETAILS_INC |
Superclass: CL_SRM_PURCHASEORDER_API Method: GET_HEADER |
UI |
Back End/ABAP |
|||
---|---|---|---|---|
View |
Extension Point |
Design Time: Gateway Entity |
Design Time: Extension Include (in DDIC Structure) |
Runtime: Superclass/ Method to Be Redefined |
S4.View.xml |
CustomerExtensionForItem |
SRM_PURCHASEORDER |
SRMPO_S_ITEM_DETAILS_INCL |
Superclass: CL_SRM_PURCHASEORDER_API Method: GET_ITEM_DETAILS |
CustomerExtensionForAccountHeader |
SRM_PURCHASEORDER |
SRMPO_S_HEAD_ACC_DETAILS_INC |
Superclass: CL_SRM_PURCHASEORDER Method: GET_ACCT_ASSGNMNT |
|
CustomerExtensionForAccounting |
SRM_PURCHASEORDER |
SRMPO_S_ACC_DETAIL_INC |
Superclass: CL_SRM_PURCHASEORDER Method: GET_ACCT_ASSGNMNT_ITM |
Business Add-Ins (BAdIs)
The following BAdIs are available for extensibility purposes:
BAdI_SRM001_POARL_MPC
You can use this BAdI to extend the OData model providers with new entities that the customer can define.
BAdI_SRM001_ POARL_DPC
When you extend fields in a model using the BAdI SRM001_POARL_MPC, you can use this BAdI to implement the same extension in the runtime. This BAdI is called in the model provider class CL_SRM_PURCHASEORDER_DPC
Extension Includes
In addition to the extension includes described above, the following extension includes are available:
DDIC |
Use |
---|---|
SRMPO_S_ATTACHMENTS_INC |
Allows to add more fields related to attachments |
SRMPO_S_CONTACT_DETAIL_INC |
Allows to add fields related to contact details |
SRMPO_S_FORWARDING_USER_INCL |
Allows to add fields related to forwarding user |
SRMPO_S_NOTES_INC |
Allows to add fields related to notes |
SRMPO_S_PO_LIMITS_INC |
Allows to add fields related to PO limits |
SRMPO_S_PRICING_DETAILS_INC |
Allows to add fields related to pricing details |
SRMPO_S_PRODUCT_DETAILS_INC |
Allows to add fields related to product details |
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 .
For a general description of the extensibility options and procedures of SAP Fiori apps, see http://help.sap.com/fiori_implementation .