# Payment Proposal Exceptions and Blocked Items Report

> A custom report that collects, in one ALV list, the items in an automatic payment program (F110) proposal that will not be paid and the vendor items that are due but did not make it into the proposal. For every row the type of obstacle (item block, vendor payment block, central block, proposal exception) is shown in its own column.

- Type: Report, Custom development, ALV report
- Module: FI
- Estimated effort: M (3–5 working days)
- Last updated: 2026-11-17
- URL: https://nekuhub.com/en/reports/payment-proposal-exceptions-blocked-items-report/


## Why is the standard not enough?

The F110 exception list is a text log; it cannot be filtered by vendor name, amount or block reason. FBZ0 lets you edit the proposal but does not show items that are due and never entered it. FBL1N lists blocked items without linking them to a specific payment run. Before approving payments, the question "what is not paid in this run, and why" needs one list.

### Closest standard alternatives

- F110: Gives the exception list as a text log; offers no filterable list.
- FBZ0: Lets you edit the proposal; does not show due items that were left out of it.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| REGUH | Proposal header: payee, payment document, total amount | Read | - | ECC + S/4 |
| REGUP | Items in the proposal, item block and payment method (driving table) | Read | REGUP-LAUFD = REGUH-LAUFD AND REGUP-LAUFI = REGUH-LAUFI AND REGUP-XVORL = REGUH-XVORL AND REGUP-ZBUKR = REGUH-ZBUKR AND REGUP-LIFNR = REGUH-LIFNR AND REGUP-VBLNR = REGUH-VBLNR | ECC + S/4 |
| BSIK | Open items that are due but not in the proposal | Read | BSIK-BUKRS = REGUP-BUKRS AND BSIK-BELNR = REGUP-BELNR AND BSIK-GJAHR = REGUP-GJAHR AND BSIK-BUZEI = REGUP-BUZEI | ECC + S/4 |
| LFA1 | Vendor name and central block | Read | LFA1-LIFNR = REGUP-LIFNR | ECC + S/4 |
| LFB1 | Company code payment block | Read | LFB1-LIFNR = REGUP-LIFNR AND LFB1-BUKRS = REGUP-BUKRS | ECC + S/4 |
| I_PaymentProposalItem | Payment proposal items on S/4HANA | Read | PaymentRunDate = REGUP-LAUFD AND PaymentRunID = REGUP-LAUFI | S/4HANA only |

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| P_LAUFD | Run date | Single value | REGUH-LAUFD | Yes |
| P_LAUFI | Run identification | Single value | REGUH-LAUFI | Yes |
| S_ZBUKR | Paying company code | Range / multiple | REGUH-ZBUKR | No |
| S_LIFNR | Vendor | Range / multiple | REGUP-LIFNR | No |
| S_ZLSPR | Payment block key | Range / multiple | BSIK-ZLSPR | No |
| P_NEXTD | Next payment date | Single value | SY-DATUM | No |
| P_DUE | Also show due items not in the proposal | Checkbox | - | No |

## Output columns

| Column | Source |
|---|---|
| Company code | REGUP-BUKRS |
| Vendor | REGUP-LIFNR |
| Vendor name | LFA1-NAME1 |
| Document | REGUP-BELNR |
| Fiscal year | REGUP-GJAHR |
| Reference | REGUP-XBLNR |
| Baseline date | REGUP-ZFBDT |
| Amount | REGUP-WRBTR |
| Currency | REGUP-WAERS |
| Payment method | REGUP-ZLSCH |
| Item block | REGUP-ZLSPR |
| Vendor payment block | LFB1-ZAHLS |
| Status | Calculated: Exception when REGUH-VBLNR is blank; not in proposal when missing from REGUP |
| Reason | Calculated: Item block, vendor block, central block (LFA1-SPERR) or missing payment method/bank details |

## How does the report work?

1. Proposal records are read for the selected run date and identification: REGUH and REGUP with XVORL = X.
2. Items that will not get a payment document (REGUH-VBLNR blank) are taken as exceptions; the reason is determined by checking, in this order, the item block (REGUP-ZLSPR), the vendor's company code payment block (LFB1-ZAHLS), the central block (LFA1-SPERR) and missing payment method or bank details.
3. When P_DUE is set, open items due by the next payment date are read from BSIK and those not found in REGUP are added as "not in proposal".
4. The vendor name is added from LFA1 and the payment block from LFB1; amounts are shown in document currency.
5. The list is shown with subtotals by vendor and reason.

## Authorization objects

- F_REGU_BUK: Payment program authorization by company code
- F_BKPF_BUK: Accounting document display authorization by company code
- F_LFA1_BUK: Vendor master authorization by company code

## Frequently asked questions

### Does the report change the proposal?

No. The report only reads. Removing a block or editing the proposal is done in FBZ0 or by changing the document; navigation from the report to those steps can be added.

### Does it work after the proposal has been deleted?

It works as long as the proposal data is still in REGUH/REGUP. After the payment run has been executed, the unpaid items of that run can still be listed.

### How are missing bank details detected?

When the payment method requires a bank transfer and the payee bank account in the proposal record is empty, the row is flagged as "bank details missing".

---
Let us build this report for your system: https://nekuhub.com/en/request-a-quote/?report=fi-payment-proposal-exceptions
