Symptom
- While creating a purchase order using ME21n, a custom field is set to obligatory in MM_PUR_S4_PO_FLDCNTRL_SIMPLE_H.
- The check for obligatory is not executed if the custom fields tab is not opened.
- The issue arises because the field can be saved without any entry if the custom tab is not opened.
Environment
SAP S/4HANA Cloud Public Edition
Reproducing the Issue
- Create a purchase order using ME21n.
- Do not open the custom fields tab.
- The check for obligatory is not executed.
Cause
The issue arises because the field can be saved without any entry if the custom tab is not opened.
Resolution
- The app “Manage Purchase Order” is implemented in a way that the business logic ensures that mandatory fields have a value and not the field control.
- To ensure that a custom field has a value before the purchase order is saved, use either the BAdI MM_PUR_S4_PO_MODIFY_HEADER or BD_MMPUR_FINAL_CHECK_PO to implement the check.
Keywords
ME21n, Purchase Order, Custom Field, Obligatory, MM_PUR_S4_PO_FLDCNTRL_SIMPLE_H, BAdI, MM_PUR_S4_PO_MODIFY_HEADER, BD_MMPUR_FINAL_CHECK_PO, Mandatory Fields, Business Logic, Manage Purchase Order. , KBA , MM-PUR-PO-2CL , Purchase Orders (Public Cloud) , Problem
Product
SAP S/4HANA Cloud Public Edition all versions