Using t-code OMR6 we set the upper and lower limit tolerances for blocking invoice. We can use different standard tolerance keys based on scenarios. Here we can give the tolerances based on ABOSULTE value and percentage limits for both upper and lower tolerance.
Here I am considering the tolerance key price variance (PP).
Upper Limit Tolerance
Considering an example where we had a PO for 100$ and after complete GR we received an invoice of 1050$ from vendor. In this case the upper tolerance key will play a role by getting the invoice blocked as it exceeds the limit and this will not let paying the additional amount to vendor.
In technical terms, when limit exceeds in table RSEG the field SPGRP (Block reason: price) will be marked ‘X’ and this is block the invoice.
Lower Limit Tolerance
In case of lower tolerance the setup little different here when the lower limit is reached a warning message is given which does not blocks invoice and posts it. Here SPGRP (Block reason: price) is NOT marked as ‘X’ which will not block the invoice.
Most of the clients have no issue with this setup as paying less is not an issue but there are few areas where lower tolerance is also important as upper tolerance.
So if you have such a requirement where you want the SPGRP as marked as ‘X’ for the lower tolerances then you can refer pilot note 2957295 – MIRO: Invoice Block for Price Shortfall or can ask SAP for note to implement.
Hope this will be helpful basically for the VIM and MM consultants.
Thank you and Happy New Year.