Payment Proposal Exceptions and Blocked Items Report
Short answer: 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.
- Estimated effort
- M · 3–5 working days
- System
- ECC and S/4HANA
- Tables
- 6
- Scope
- Global
- Built by
- NeKuDos Teknoloji
- Last updated
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.
Who uses it? Accounts payable teams, treasury and finance managers who approve payments.
Closest standard alternatives
Tables used
The tables the report reads and their join fields. ECC and S/4HANA differences are marked separately.
| Table | Role | Join | System |
|---|---|---|---|
| REGUHPayment Program Settlement Data | Proposal header: payee, payment document, total amount | — | ECC + S/4 |
| REGUPPayment Program Processed Items | Items in the proposal, item block and payment method (driving table) | 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 |
| BSIKVendor Open Items | Open items that are due but not in the proposal | BSIK-BUKRS = REGUP-BUKRS AND BSIK-BELNR = REGUP-BELNR AND BSIK-GJAHR = REGUP-GJAHR AND BSIK-BUZEI = REGUP-BUZEI | ECC + S/4 |
| LFA1Vendor Master (General Section) | Vendor name and central block | LFA1-LIFNR = REGUP-LIFNR | ECC + S/4 |
| LFB1Vendor Master (Company Code) | Company code payment block | LFB1-LIFNR = REGUP-LIFNR AND LFB1-BUKRS = REGUP-BUKRS | ECC + S/4 |
| I_PaymentProposalItemPayment Proposal Item | Payment proposal items on S/4HANA | PaymentRunDate = REGUP-LAUFD AND PaymentRunID = REGUP-LAUFI | S/4HANA only |
S/4HANA notes
- BSIK: In S/4HANA BSIK is no longer filled as a separate index table; reads work through a compatibility view. For new developments the I_OperationalAcctgDocItem CDS view is recommended.
Selection screen parameters
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| P_LAUFD | Run date | Single value | REGUH-LAUFD | Yes | 17.11.2026 |
| P_LAUFI | Run identification | Single value | REGUH-LAUFI | Yes | HAFT1 |
| S_ZBUKR | Paying company code | Range / multiple | REGUH-ZBUKR | No | 1000 |
| S_LIFNR | Vendor | Range / multiple | REGUP-LIFNR | No | 100245 |
| S_ZLSPR | Payment block key | Range / multiple | BSIK-ZLSPR | No | A |
| P_NEXTD | Next payment date | Single value | SY-DATUM | No | 24.11.2026 |
| P_DUE | Also show due items not in the proposal | Checkbox | — | No | X |
Output columns
| # | Column | Source |
|---|---|---|
| 1 | Company code | REGUP-BUKRS |
| 2 | Vendor | REGUP-LIFNR |
| 3 | Vendor name | LFA1-NAME1 |
| 4 | Document | REGUP-BELNR |
| 5 | Fiscal year | REGUP-GJAHR |
| 6 | Reference | REGUP-XBLNR |
| 7 | Baseline date | REGUP-ZFBDT |
| 8 | Amount | REGUP-WRBTR |
| 9 | Currency | REGUP-WAERS |
| 10 | Payment method | REGUP-ZLSCH |
| 11 | Item block | REGUP-ZLSPR |
| 12 | Vendor payment block | LFB1-ZAHLS |
| 13 | Status | Calculated Exception when REGUH-VBLNR is blank; not in proposal when missing from REGUP |
| 14 | Reason | Calculated Item block, vendor block, central block (LFA1-SPERR) or missing payment method/bank details |
Sample output
| Company code | Vendor | Vendor name | Document | Fiscal year | Reference | Baseline date | Amount | Currency | Payment method | Item block | Vendor payment block | Status | Reason |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1000 | 100245 | Atlas Ambalaj | 5100004211 | 2026 | FT-2026-0912 | 09/29/2026 | 125,000 | TRY | T | A | Exception | Item block (A) | |
| 1000 | 100387 | Delta Metal | 5100003902 | 2026 | DM-55102 | 10/10/2026 | 48,960 | TRY | T | B | Exception | Vendor payment block | |
| 1000 | 100512 | Ege Kimya | 5100004502 | 2026 | EK-20412 | 10/18/2026 | 25,560 | TRY | Not in proposal | Payment method missing | |||
| 1000 | 100640 | Marmara Lojistik | 5100004630 | 2026 | ML-7781 | 11/02/2026 | 18,400 | EUR | U | R | Exception | Item block (R) |
How does the report work?
- Proposal records are read for the selected run date and identification: REGUH and REGUP with XVORL = X.
- 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.
- 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”.
- The vendor name is added from LFA1 and the payment block from LFB1; amounts are shown in document currency.
- The list is shown with subtotals by vendor and reason.
Performance notes
Read REGUH/REGUP by the run key (LAUFD, LAUFI). For the BSIK comparison use the company code and a due-date range; take the vendor list from the proposal scope. On S/4HANA I_PaymentProposalItem provides the proposal items.
Features
- ALV list (sort, filter, subtotals)
- User-specific layout variants
- Double-click drill-down to the document Double-clicking the document opens FB03; double-clicking the vendor opens FBL1N.
- Export to Excel
- Send the result by email After the proposal has run, the list can be sent to the payment approver.
Authorization objects
- F_REGU_BUKPayment program authorization by company code
- F_BKPF_BUKAccounting document display authorization by company code
- F_LFA1_BUKVendor 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".
Related reports
Vendor Open Items Aging Report
A custom ALV report that ages vendor open items by net due date and spreads the amounts into not-due, 0–30, 31–60, 61–90 and 90+ day buckets. The …
Vendor Payment Advice Email Program
A custom program that, after an automatic payment run, emails every vendor a PDF payment advice listing the invoices that were paid. A preview comes …
Let us build this report for your system
Briefly describe your system and expectations. We will clarify the scope and come back with an effort and price quote.