teachSAP: MM-IV-LIV-MRBR Invoice Release in LIV Transaction MRBR

Welcome Guest

Added by Guest , last edited by Guest on Jun 04, 2009 (view change)

Labels:

(None)

Add Labels

Wait Image

Enter labels to add to this page:

Tip: Looking for a label? Just start typing.

Content

Use and Overview

Before you can pay a blocked invoice, you must release it in a separate step. You do so by canceling the blocking indicator that was set when the invoice was posted.
Since the total invoice amount is to be paid and not individual invoice items, the blocking indicator is set in the vendor line of the accounting document. As a result, all the items in an invoice can only be released at the same time.
MR02: invoice release transaction for blocked invoices that were posted in CIV (MR01)
MRBR: invoice release transaction for blocked invoices that were posted in LIV
Releasing LIV blocked invoices that were posted before 4.6A: MR02 or MRBR if you first convert them with report RM08RBKPBLOCKED
two processes for releasing invoices for payment:
- Releasing Automatically
- Releasing Invoices Manually

Settle with transaction MBRR: selection

Move cash disc. Date:
- To specify when exactly an invoice is to be paid, you agree terms of payments with the vendor. These terms of payment contain the baseline date from which your cash discount period applies. If an invoice was blocked for payment for a long time, your cash discount deadline could expire. If you release this invoice, you can select the field Move cash discount date on the initial screen of the invoice release transaction and retain the agreed cash discount.
Canceled invoices are not taken into account.

Settlement with transaction MBRR: Releasing Automatically

Use
When you release invoices automatically, the system deletes all blocking reasons that no longer apply.
When all blocking reasons in an invoice are deleted, the system automatically releases the invoice.

Prerequisites
It is only possible to automatically release invoices if their blocking reasons are no longer valid. This can be the case for invoices blocked due to quantity, price, or schedule variance s, or due to quality inspection.
You can only use the function Release automatically for the blocking procedure Blocked due to variances.

Result
The system issues a list of the invoices released. The system will also release invoices for which a manual block was set in the document header if the blocking reasons in all items no longer apply.

Settlement with transaction MBRR: Releasing Manually

Deleting Blocking Reasons

Use
You can delete individual blocking reasons while processing a blocked invoice item.

Procedure

Place the cursor on the blocking reasons that you want to delete.
Choose Delete blocking reasons. The system highlights the deleted blocking reason in color.
Check your entries.
Choose Save changes.

Result
If there are other blocking reasons in this item or other items in the invoice, you receive a message
indicating that the selected blocking reason was deleted.
When you delete the last blocking reason in an invoice, the system automatically releases the invoice. The following message appears:
nn invoice(s) released

Releasing Invoices

Use
When you release an invoice, the system reverses the blocking indicator in the accounting document for the invoice. In the vendor line, the R in the field Payment block is deleted.

Procedure

Select the invoice document that you want to release. The system automatically selects all other items in the invoice since you cannot release individual items.
Choose !6 Release Invoice.jpg!Release invoice.
Check your entries.
Choose Save changes. The invoices selected are only released for payment when you save them.

Technical details: Database Structure

Database Structure of Incoming Invoice:

RBKP: Header data of an Incoming Invoice
RSEG: Item data (reference to a PO)
RBMA: Item data (reference to a material)
RBCO: Item data (Direct posting to G/L account)

Specialities of an Incoming Invoice blocked for payment:

There exists a record in the index table RBKP_BLOCKED (containing 10 fields for fast selection of blocked invoices)
Important field in RBKP_BLOCKED: Logistics payment block (MRM_ZLSPR) with possible values
- A Automatically blocked due to existence of blocking reasons
- S Stochastically blocked
- M Manual payment block set in header - no blocking reasons
In an automatically blocked invoice (MRM_ZLSPR = 'A') there is at least one blocking reason in RSEG / RBMA / RBCO:

Database structure of the FI follow-on document:
- First (vendor) BSEG Item: Payment Block is set (BSEG-ZLSPR = ‚R')
Attention: RBKP contains exactly the data the user has entered, so RBKP-ZLSPR is only filled when the user has entered a value. This means
- The field RBKP-ZLSPR is not necessarily set in the case of blocked invoices:
- The field RBKP-ZLSPR will never be changed in the Release process

Technical Details: RM08RELEASE - Overview Flow Logic

Technical Details: Debugging tips (1)

Why does MRBR not show an invoice as blocked for payment?

First check the corresponding database entries (RBKP_BLOCKED, first BSEG item: BSEG-ZLSPR)
Debugging: breakpoint on SELECT of RBKP_BLOCKED in RM08RELEASE:
...
START-OF-SELECTION.

* Selection from RBKP_BLOCKED -----------------------------------------*
SELECT * FROM rbkp_blocked INTO TABLE tab_rbkp_blocked
       WHERE    mrm_zlspr = f_mrm_zlspr
         AND    bukrs      IN so_bukrs
         AND    gjahr      IN so_gjahr
         AND    lifnr      IN so_lifnr
         AND    belnr      IN so_belnr
         AND    usnam      IN so_usnam
         AND    budat      IN so_budat
         AND    faell      IN so_faell
         AND    ekgrp      IN so_ekgrp.
...

Technical Details: Debugging tips (2)

Why does (does not) MRBR release an invoice automatically?

Check the prerequisites for releasing invoices automatically. Check if with processing option „release manually", blocking procedure „blocked due to variances" the blocking reason is white (~valid) or coloured (~not valid)

Why does MRBR show a blocking reason as valid (not valid)?

Check the IMG documentation of the corresponding tolerance key.
Debugging:
Put a breakpoint on:
RM08RELEASE form BLOCKING_REASON_VALIDITY_CHECK
Put another breakpoint on
function module: MRM_TOLERANCE_CHECK
(MRM_TOLERANCE_CHECK is executed e.g. in RM08RELEASE from function module MRM_BLOCK_REASON_VAL_CHECK_P which is called from BLOCKING_REASON_VALIDITY_CHECK for tolerance key PP.
MRM_TOLERANCE_CHECK is also the function module which -in general- determines whether an invoice is blocked for payment when you post it e.g. with MIRO)

Technical Details: RM08RELEASE - Summary

Transaction MRBR
Report RM08RELEASE
Works only for documents of LIV when they have a record in the index table RBKP_BLOCKED. Cancelled Invoices are not selected by MRBR because they do not have a RBKP_BLOCKED entry.
Selection Screen: like a usual report
List: ALV
Automatic Release in the background possible
Database update not immediately but after saving explicitly

Update of the Incoming Invoice

Deletion RBKP_BLOCKED
Deletion blocking reasons in RSEG if necessary
Update of FI follow-on document (Deletion BSEG-ZLSPR) via Accounting Interface (TRWPR-PROCESS = ‚PYMNTBLK')
- AC_PAYMENTBLOCK_CHECK

teachSAP

Sunday, 14 February 2010

MM-IV-LIV-MRBR Invoice Release in LIV Transaction MRBR