Unfortunately this is a standard response of SAP on POs. There is no way to suppress this, ask your client to either change the G/L account if that is the source of the error or abandon this PO if possible. Not worth spending more analysis time on this or even looking for a solution.
↧