Problem: When posting non-goods receipt invoices in MIRO, G/L account and acct assignment object are proposed by purchase order, but they can be overwritten by users with no validation, often resulting in incorrect posting.
Such validation controls are in place for ME51N and ME21N. That is, the combination of GL account and account assignment are validated/checked against Field Status Group (FSTAG u2013 based on G/L master) as well as Account Assignment Category (in PO). I want to extend those controls to MIRO non-GR invoices.
This problems fits description in OSS Note 522101. The solution recommended in the Note is u201CPossible incorrect entries could be checked or corrected by validation or substitution if necessary.u201D
If I create a validation in OB28, how should I express the logic in "Check"?
Appreicate any help on this.