Release of payment block using FB02, overrides variance (R) block

[Former Member]

Hi,

We have a requirement where we created new payment terms for one time vendors (OTV) with payment blocks (O).

So all MM invoices for these One time vendors are blocked for payment.

Now, we have developed 2 new Z report which will display all one time vendors and allow one set of users to update the bank details and the other report will allow other users to review these bank details and remove the payment block and release the invoice.

Issue: For invoices that have a price or quantity variance the invoices appear in MRBR

- when the invoice is released using MRBR first, we get a message invoice is blocked with payment block 'O' and we can go ahead and use our report to release it(internally calling FB02). Note: The block here shows 'O' not R

However, when we release it first using our Zreport which inturns calls FB02 and removes the payment block. This picks the invoice during payment run. Overriding the price /qty block which is set by the system. The invoice will still appear in MRBR but the invoice can be paid in FI.

The problem is that we have different users using MRBR and those using the Zreport are meant to review only the bank details.we cant restrict which process to be followed first.

The only solution so far seems to be to code in our program that reads if there are automatic variance blocks, then not to display it in our program until the variance blocks are released.

Is there a better way of doing this?

Regards,

Simi

[adam_kavanagh]

Hi Simi,

This type of behaviour is documented in SAP note 394370:

"A document generated with MIRO was blocked for payment.You cancel the

payment block from the vendor line item in the FI follow-up

document.Transaction MRBR then displays the invoice document

nevertheless. Why?

The invoice document itself cannot be changed by changes to the

follow-up documents; this is not programmed.Transaction MRBR therefore

continues to display the document as blocked. If this document is

released from an MM point of view, the FI follow-up document remains

released.Thus the damage caused is restricted to unnecessary work by the

user.

SAP recommends that you only use the release transactions for releasing

invoices."

MRBR generates its list of blocked invoices from table RBKP_BLOCKED and is the

only transaction which deletes entries from this table thats why when your report

calls FB02 to remove the payent block MRBR will still show the invoice as blocked.

You could code in a pop up message in your report that prevents the user from

deleting the payment block and to advise using MRBR instead to delete the block.

Hope this helps,

Adam.