The new transaction for releasing invoices, MRBR, only takes into account invoices posted in Logistics Invoice Verification.
The transaction offers numerous selection options to narrow down which invoices are released. You can list invoices that:
Like the existing invoice release function, the new transaction allows automatic or manual release of invoices.
When you automatically release invoices, the system checks each blocking reason to see if it is still valid. If it is no longer valid, the system deletes the blocking reason. If all blocking reasons in an invoice are deleted, the system releases the invoice.
(Until now, the blocking reason 'price variance' only became invalid when you changed the order price. The system now takes into account subsequent credits during the check.)
You can have the system automatically release invoices in the background.
When you manually release invoices, a list of blocked invoices appears. In this list, blocking reasons that are no longer valid are indicated in color. The user can delete individual blocking reasons or flag invoices that are to be released.
Blocked invoices that were posted in conventional Invoice Verification earlier than Release 4.6A must be released using the existing invoice release transaction (MR02).
Blocked invoices that were posted in Logistics Invoice Verification earlier than Release 4.6A are not taken into account in the new invoice release transaction. You can use the existing invoice release transaction to release them. Alternatively, you can run report RM08RBKPBLOCKED; this report adds the blocked 'old documents' to the table of blocked logistics invoices so that you can process them in the new invoice release transaction.
You have to assign authorizations to the users who are to release blocked invoices.
The system checks two authorization objects when you release invoices:
If you want the system to automatically release invoices in the background, you must set up the relevant job for program RM08RELEASE.