# 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 finance team sees how much is owed to which vendor, and for how many days it has been overdue, in one list.

- Type: Report, Custom development, ALV report
- Module: FI
- Estimated effort: M (3–5 working days)
- Last updated: 2026-11-16
- URL: https://nekuhub.com/en/reports/vendor-open-items-aging-report/


## Why is the standard not enough?

FBL1N lists items but does not total them into age buckets. S_ALR_87012078 does due-date analysis, but its output layout is limited and does not offer one Excel-ready list with vendor name and reconciliation account. Month-end reporting usually ends up as a custom report.

### Closest standard alternatives

- FBL1N: Lists open items; does not total them into age buckets.
- S_ALR_87012078: Totals by due-date intervals; the layout is limited and it does not offer one Excel-ready list.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| BSIK | Vendor open items, due-date data and amounts (driving table) | Read | - | ECC + S/4 |
| LFA1 | Vendor name | Read | LFA1-LIFNR = BSIK-LIFNR | ECC + S/4 |
| LFB1 | Reconciliation account and payment terms | Read | LFB1-LIFNR = BSIK-LIFNR AND LFB1-BUKRS = BSIK-BUKRS | ECC + S/4 |
| T001 | Company code local currency | Read | T001-BUKRS = BSIK-BUKRS | ECC + S/4 |
| I_OperationalAcctgDocItem | In S/4HANA, for reading open items together with the net due date | Read | CompanyCode = BSIK-BUKRS AND Supplier = BSIK-LIFNR | S/4HANA only |

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| S_BUKRS | Company code | Range / multiple | BSIK-BUKRS | Yes |
| S_LIFNR | Vendor | Range / multiple | BSIK-LIFNR | No |
| S_AKONT | Reconciliation account | Range / multiple | LFB1-AKONT | No |
| P_KEYDT | Key date | Single value | SY-DATUM | Yes |
| P_BKT1 | Bucket 1 upper limit (days) | Single value | - | No |
| P_BKT2 | Bucket 2 upper limit (days) | Single value | - | No |
| P_BKT3 | Bucket 3 upper limit (days) | Single value | - | No |
| P_NOTDUE | Also show items not yet due | Checkbox | - | No |

## Output columns

| Column | Source |
|---|---|
| Company code | BSIK-BUKRS |
| Vendor | BSIK-LIFNR |
| Vendor name | LFA1-NAME1 |
| Document | BSIK-BELNR |
| Fiscal year | BSIK-GJAHR |
| Posting date | BSIK-BUDAT |
| Net due date | Calculated: BSIK-ZFBDT + payment-term days (ZBD1T/ZBD2T/ZBD3T) |
| Days overdue | Calculated: Key date − net due date |
| Amount | Calculated: BSIK-DMBTR, shown as a positive payable when SHKZG = H |
| Currency | T001-WAERS |
| Age bucket | Calculated: Bucket of the days overdue by the P_BKT1, P_BKT2, P_BKT3 limits |

## How does the report work?

1. Open items posted up to the key date are read from BSIK for the selection. When a past key date is chosen, items cleared after that date are added from the cleared items table as well.
2. The net due date is derived from the baseline date (ZFBDT) and the payment-term days (ZBD1T, ZBD2T, ZBD3T) using the standard due-date calculation.
3. Days overdue = key date − net due date. Negative values are items that are not yet due.
4. The amount is signed by the debit/credit indicator (SHKZG) and shown in local currency (T001-WAERS).
5. The vendor name is added from LFA1 and the reconciliation account from LFB1; amounts are spread into the age buckets.

## Authorization objects

- F_BKPF_BUK: Accounting document authorization by company code
- F_LFA1_BUK: Vendor master authorization by company code

## Frequently asked questions

### How is the net due date calculated?

The payment-term days are added to the baseline date (BSIK-ZFBDT). For items without cash discount, the net payment days are used; the calculation follows SAP's standard due-date logic.

### Can aging be run for a past date?

Yes. With a past key date, items cleared after that date are included too, so the payables picture at a month-end close can be reproduced.

### Which source should be used on S/4HANA?

BSIK can still be read as a compatibility view. For new developments, the I_OperationalAcctgDocItem CDS view, which already provides the net due date, is preferred.

---
Let us build this report for your system: https://nekuhub.com/en/request-a-quote/?report=fi-vendor-open-items-aging
