3723065 - Restrict editing of 'G/L account' field in Purchase Orders and Requisitions

• In SAP S/4HANA Cloud, the G/L Account field in Purchase Requisitions and Purchase Orders remains editable during document creation and modification.
• There is a requirement to restrict or block changes to the G/L Account field, but standard field control and available BAdIs do not expose this field for dynamic UI control.

SAP S/4HANA Cloud Public Edition

1. Open the app Manage Purchase Requisitions – Professional or Manage Purchase Orders in SAP S/4HANA Cloud.
2. Create a new document with an account assignment category.
3. Enter a G/L Account and save the document.
4. Reopen the document in edit mode.
5. Change the G/L Account value.
6. Result: The system allows the G/L Account field to be edited

This is standard system behavior by design.

1. Use the check BAdI BD_MMPUR_FINAL_CHECK_PO.
2. Implement validation logic to monitor changes to the G/L Account field.
3. Raise an error (E) message to block the change, or a warning (W) message if only notification is required.

g/l account, purchase order, requisition, field control, mm_pur_s4_po_fldcntrl_simple, bd_mmpur_final_check_po, sap customer influence, feature request, warning message, field restriction, procurement , KBA , MM-FIO-PUR-PO-2CL , Fiori UI for Purchase Orders (Public Cloud) , Problem