SAP AP Open Items (Aging) Report
An AP open items report reads SAP's open accounts-payable items and joins the vendor and account, so open payables with due dates and aging buckets sit on one Excel row.
- PostNow ships this report out of the box – pick it, set filters, run, and it lands in Excel; no SE16, joins or ABAP.
- The data spans several tables. It joins BSIK, LFA1, LFB1, T003T on BUKRS + LIFNR + BELNR and resolves the text lookups.
- The standard route is manual. Teams use FBL1N (open items) for a single record, then SE16 or SQVI to stitch tables together in Excel.
- You get clean, labelled columns. LIFNR, NAME1, BELNR, GJAHR, BLART, BUDAT and more, each with a plain-English heading.
- Refreshable, not a one-off dump. Rerun the report to pull the latest, with your own SAP authorizations enforced. Works on ECC and S/4HANA.
What the AP open items report shows
A SAP AP open items report answers a simple question that SAP makes surprisingly hard: give me every AP open items record, with all the attributes that matter, in one place I can filter and share. On screen, SAP shows one record at a time and splits its attributes across several views. This report flattens all of that into a single Excel sheet, one row per record, with the codes turned into readable labels.
Because the output is a plain sheet, it becomes the starting point for the work people actually do with it: a data-quality review, a cleanup before a migration, a hand-off to an auditor, or a source for a pivot. The value is not just the extract, it is that the extract is complete and consistent every time you run it.
The SAP tables behind it
BSIK holds open accounts-payable items: vendor invoices that have not yet been paid. Each row is an open line keyed by company code, vendor and document. The baseline date ZFBDT, the payment terms ZTERM and the days ZBD1T together give the net due date, which is what aging is derived from. The vendor name is joined from LFA1, and the reconciliation account from the company-code view LFB1. The document-type text comes from T003T on BLART. The report lists open payables with due dates and aging buckets so you can see exactly what is coming due.
The joins are the whole reason this is worth automating. Miss one and the report is subtly wrong; get the key fields slightly off and rows fan out or drop. Doing it once, correctly, and then reusing it is what turns a fragile spreadsheet exercise into a reliable report.
The columns you get
Every column below is a real SAP field, labelled in plain English, with the table it is read from. These are the fields most teams want on a AP open items report; a tool like PostNow lets you add or remove columns without touching the underlying join.
| SAP field | What it is | Source |
|---|---|---|
| LIFNR | Vendor | BSIK |
| NAME1 | Name | LFA1 |
| BELNR | Document number | BSIK |
| GJAHR | Fiscal year | BSIK |
| BLART | Document type | BSIK |
| BUDAT | Posting date | BSIK |
| ZFBDT | Baseline date | BSIK |
| ZTERM | Payment terms | BSIK |
| ZBD1T | Days net | BSIK |
| DMBTR | Amount (local) | BSIK |
| WRBTR | Amount (doc) | BSIK |
| SHKZG | Debit/credit | BSIK |
| AKONT | Reconciliation acct | BSIK |
Building it yourself: FBL1N (open items), SE16 or SQVI
FBL1N shows open items for a vendor on screen and the F.4x reports give aging, but they are fixed layouts, not a flat file with the columns and buckets you want. SE16 on BSIK gives the open items, but leaves the vendor name from LFA1, the reconciliation account from LFB1 and the document text from T003T to be matched in Excel, and it does not calculate aging: you build the net due date from the baseline date and terms, then bucket it yourself. Repeating that every week is exactly the kind of task that should be automated.
None of this is impossible; people do it every month. The problem is that it is manual, easy to get subtly wrong, and stale the moment it is saved. Each refresh means repeating the same exports and the same lookups, and any new column means another round with a developer. For a one-off you can push through it. For a report you run every period, the cost adds up. If you want the general landscape of options first, see our overview of SAP reporting tools and how to get SAP to Excel.
The out-of-the-box way: PostNow's AP open items report
PostNow's Report Library already contains this exact report, pre-built. You do not assemble the joins or resolve the texts; that is done for you. You open Excel, log in to postnow.ai from the task pane, pick the AP open items report, set your range filters, and run. The governed, joined data lands in the sheet, ready to filter, pivot or share, and you can refresh it whenever you need the latest.
Two things make this different from a SE16 dump. First, it is governed: PostNow enforces your own SAP authorizations, so you only ever see the data you are entitled to, and every row can be traced back to its source. Second, it is repeatable: the same report, the same columns, refreshable on demand, with no ABAP to write or maintain. That is the payoff of teaching the hard version first, then handing you the shortcut.
Filters and selection you'll want
A good AP open items report is only as useful as the selection you can put on it. The filters most teams reach for are:
- Vendor range (LIFNR)
- Company code (BUKRS)
- Key date (open at) (BUDAT)
- Document type (BLART)
- Due date / aging (ZFBDT)
- Reconciliation account (AKONT)
You set these once as your selection, then reuse or adjust them each run. Because the selection travels with the report, a monthly extract becomes a single refresh rather than a rebuild.
ECC vs S/4HANA
BSIK is a compatibility view over the Universal Journal ACDOCA in S/4HANA, and the aging is derived from the net due date the same way on both releases. PostNow reads it directly, so the open-items report behaves the same on ECC and S/4HANA.
The practical takeaway is that a report built on the tables and read through standard interfaces survives a migration far better than one wired to a specific screen or a custom program. When you eventually move from ECC to S/4HANA, a table-based AP open items report keeps working, which is one less thing to rebuild in an already large project.
Frequently asked questions
How do I get a AP open items report out of SAP into Excel?
You can export the underlying tables with SE16 and stitch them together in Excel, build a query in SQVI, or ask a developer for an ABAP report. The quickest governed route is a tool that already has the report built: in PostNow you log in to postnow.ai from the Excel task pane, pick the AP open items report from the Report Library, set your filters and run, and the joined data lands in the sheet.
Which SAP tables hold AP open items data?
The data is spread across several tables that have to be joined on their key fields: BSIK, LFA1, LFB1, T003T. The report links them on BUKRS + LIFNR + BELNR and resolves the text tables so the output reads in plain language.
Is there a standard SAP report or transaction for AP open items?
There are standard transactions (FBL1N (open items) and others), but they are built for on-screen display or for a fixed layout, not for a clean, refreshable Excel extract with exactly the columns you want. That is why most teams fall back to SE16 exports or a custom report.
How do I export AP open items data to Excel without ABAP?
Use a tool whose SAP connection is set up once and then reads through standard interfaces, so no ABAP is needed for day-to-day reporting. PostNow reads the AP open items tables, performs the joins and text lookups, and writes the result straight into Excel, refreshable on demand, with your own SAP authorizations enforced.
Can I refresh or schedule the report?
Yes. Because the report keeps its connection and selection, you can refresh it to pull the latest data at any time rather than rebuilding the extract. This is the main advantage over a one-off SE16 dump, which is stale the moment it is saved.
Does it work in S/4HANA?
BSIK is a compatibility view over the Universal Journal ACDOCA in S/4HANA, and the aging is derived from the net due date the same way on both releases. PostNow reads it directly, so the open-items report behaves the same on ECC and S/4HANA.
How is AP aging calculated?
Aging is measured from the net due date, which comes from the baseline date ZFBDT plus the payment terms and days. Comparing the net due date to your key date places each open item in an aging bucket. A PostNow report can derive the due date and buckets for you rather than leaving it as an Excel formula exercise.
Can I get open payables as of a key date?
Yes. Open-item reporting is always as of a date: items open on that date are included. A report can take a key date and return the open payables and their aging at that point, which is what you need for a period-end payables review.