MIR4 — Display Invoice Document

MIR4 opens a single invoice verification document by document number and fiscal year and renders its header, tax breakdown, and line items. The structural fact that drives most support tickets is that MIR4 is not purely a display transaction: if the document number entered belongs to a parked or held invoice rather than a posted one, MIR4 opens it in change mode, letting the user complete and post it from what looks like a display screen. A posted invoice, by contrast, is genuinely read-only in MIR4 except for a small set of fields SAP still allows to change after posting, such as payment block or baseline date. Everything else about the invoice, including quantities and amounts, is frozen once posted; correcting it means a credit memo or reversal, not editing this document.

MIR4 is reached for whenever someone needs to inspect an invoice that already exists in the system rather than create one: checking why an invoice is on payment block, confirming which GL accounts or cost objects it hit, verifying the tax code and amount the vendor was invoiced against, or resuming a parked invoice that a colleague started. It differs from MIRO, which is used to enter a new invoice, and from MIR6, which is used when the document number is not known and a list has to be searched by vendor, PO, or reference first. On S/4HANA, the equivalent Fiori app for viewing a supplier invoice is used in the same role for users working outside the SAP GUI, but MIR4 remains the faster path when the document number is already in hand from a workflow notification or an FI document reference.

In SE16N on RBKP, filter by BELNR and GJAHR for the invoice document number in question to confirm its existence and status flag before assuming the number was mistyped. Join to RSEG on the same BELNR and GJAHR to see line-level blocking indicators that the MIR4 header screen does not surface directly. To confirm the accounting document actually posted, check BKPF for an entry whose reference key matches the invoice document number and fiscal year rather than searching FB03 blind. To confirm the PO side, filter EKBE by the purchase order and line number with the transaction/event indicator for invoice receipt and compare the quantity there against RSEG.

MIR4 itself is unchanged on S/4HANA and still works against the same RBKP and RSEG structures for logistics invoice verification. The Fiori app for displaying a supplier invoice covers the same read-only use case for browser-based users and is the app to point business users toward when they do not have GUI access, but consultants troubleshooting a specific document number still tend to go straight to MIR4 because it is faster to reach with a known number.

This sits with Accounts Payable / MM functional support. A handover should include the invoice document number and fiscal year, the current status (parked, posted, blocked), the specific block reason if applicable, and whether the linked accounting document exists. Escalate to ABAP only if the document was created through an interface and the posting itself failed with a dump; Basis has no role here.

MIR7 is the transaction that parks the invoice MIR4 later displays or completes, and understanding parking behavior explains most of the change-mode confusion above. MIR5 and MIR6 are the search/list transactions used when the document number is not yet known, and are the natural predecessor step to MIR4 in a real investigation. MB03 is worth checking alongside MIR4 whenever the discrepancy under review involves a mismatch between the goods receipt and the invoice quantity, since the invoice document alone will not show the receiving side of that story.