Symptom
There is bad performance on Purchase Orders
Environment
SAP S/4HANA Cloud Public Edition
Cause
When using the BAdI BAdI MM_PUR_S4_PO_FLDCNTRL_SIMPLE to update fields content.
However this is not the purpose of this BADI; it is used to change the field control in the purchase order apps.
The Field Control BAdI is NOT the place to update fields content. Due to the purpose of field control, this Badi is called N times which is intended. But coding which updates the field via a very expensive HTTP call is also called N times and causes performance issues .
Resolution
Use the Field Control BADI only for changing Fields properties as it is documented on the BADI itself and explained on the coding examples.
Other BAdIs are available to update field content.
The available fields to be changed for this purpose must be checked in the following BAdIs:
- Modify Purchase Order Schedule Line Data ( MM_PUR_S4_PO_MODIFY_SCHEDULE)
- Modify Purchase Order Item Delivery Address (MM_PUR_S4_PO_MODIFY_DELIV_ADDR)
- Modify Purchase Order Item (MM_PUR_S4_PO_MODIFY_ITEM)
- Modify Purchase Order Header (MM_PUR_S4_PO_MODIFY_HEADER)
- Modify Purchase Order Account Assignment Data (MM_PUR_S4_PO_MODIFY_ACCOUNT)
- Modify Tax Jurisdiction Code of Purchase Order Item (MM_PUR_S4_PO_MODIFY_TAXJURCODE)
Keywords
KBA , MM-PUR-PO , Purchase Orders , Problem