SAP GL Line Items Report
A G/L line items report joins the SAP document header and line tables and resolves account and cost center texts, so every posting line reads in plain language 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 BKPF, BSEG, SKAT, CSKT on BUKRS + BELNR + GJAHR and resolves the text lookups.
- The standard route is manual. Teams use FBL3N for a single record, then SE16 or SQVI to stitch tables together in Excel.
- You get clean, labelled columns. BELNR, GJAHR, BLART, BUDAT, BLDAT, BUKRS 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 G/L line items report shows
A SAP GL line items report answers a simple question that SAP makes surprisingly hard: give me every G/L line 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
A financial document is a header plus lines. BKPF holds the header: document number BELNR, company code, fiscal year, document type and the posting and document dates. BSEG holds the line items, keyed by company code, document number and fiscal year, with the G/L account, debit or credit indicator, amounts, cost center and profit center. The account description comes from SKAT on HKONT and the cost center name from CSKT on KOSTL. BSEG is a cluster table, which is exactly why this is hard by hand: it cannot be read by a normal join in a plain SQL view. The report flattens header and lines into one row per posting line with readable texts.
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 G/L line items report; a tool like PostNow lets you add or remove columns without touching the underlying join.
| SAP field | What it is | Source |
|---|---|---|
| BELNR | Document number | BKPF |
| GJAHR | Fiscal year | BKPF |
| BLART | Document type | BKPF |
| BUDAT | Posting date | BKPF |
| BLDAT | Document date | BKPF |
| BUKRS | Company code | BKPF |
| HKONT | G/L account | BSEG |
| TXT50 | Account text | SKAT |
| SHKZG | Debit/credit | BSEG |
| DMBTR | Amount (local) | BSEG |
| WRBTR | Amount (doc) | BSEG |
| KOSTL | Cost center | BSEG |
| PRCTR | Profit center | BSEG |
| SGTXT | Line text | BSEG |
| ZUONR | Assignment | BSEG |
Building it yourself: FBL3N, SE16 or SQVI
FBL3N shows G/L line items on screen and exports them, but it is built for one account selection at a time, and FB03 shows a single document. SE16 on BSEG is where people get stuck: BSEG is a cluster table, so a plain SQL view or an SQVI query cannot join it the way it joins a normal transparent table, and large selections are slow. You end up exporting header and lines separately, matching them in Excel, then adding SKAT and CSKT for the texts. It is doable, but it is the classic case where the standard tools fight you.
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 G/L line 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 G/L line 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 G/L line items report is only as useful as the selection you can put on it. The filters most teams reach for are:
- Company code (BUKRS)
- G/L account (HKONT)
- Posting date (BUDAT range)
- Document type (BLART)
- Cost center (KOSTL)
- Fiscal year (GJAHR)
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
BSEG is a cluster table and cannot be joined in a plain SQL view, and in S/4HANA the line items move to the Universal Journal ACDOCA. PostNow reads both directly, so a G/L line-item report works 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 G/L line items report keeps working, which is one less thing to rebuild in an already large project.
Frequently asked questions
How do I get a G/L line 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 G/L line items report from the Report Library, set your filters and run, and the joined data lands in the sheet.
Which SAP tables hold G/L line items data?
The data is spread across several tables that have to be joined on their key fields: BKPF, BSEG, SKAT, CSKT. The report links them on BUKRS + BELNR + GJAHR and resolves the text tables so the output reads in plain language.
Is there a standard SAP report or transaction for G/L line items?
There are standard transactions (FBL3N 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 G/L line 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 G/L line 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?
BSEG is a cluster table and cannot be joined in a plain SQL view, and in S/4HANA the line items move to the Universal Journal ACDOCA. PostNow reads both directly, so a G/L line-item report works the same on ECC and S/4HANA.
Why is BSEG hard to report on?
BSEG is a cluster table, which means SAP stores several logical rows together in one compressed physical record. A normal SQL view or SQVI query cannot join it the way it joins a transparent table, so line-item extracts either use a purpose-built read or become slow and awkward. PostNow reads BSEG, and ACDOCA in S/4HANA, directly.
Can I get G/L line items with cost center and profit center?
Yes. The cost center KOSTL and profit center PRCTR sit on the BSEG line, and the account and cost center texts come from SKAT and CSKT. A report can show all of them per line, so you can analyse postings by account, cost center or profit center.