SAP GL Line Items Report: GL Line Items 360

What this report answers

PostNow.ai's GL Line Items 360 (FICO-07) puts the accounting document header next to every line, with account, cost centre, profit centre and partner names already resolved. It is the extract behind three jobs:

• Account analysis. What makes up the balance on this account this period: which documents, which document types, which vendors or customers?
• Reclass and coding review. Which postings hit a cost centre, profit centre or internal order they should not have, judging by item text and assignment?
• Audit and journal entry testing. Who posted what with which transaction code, with which reference, and which documents were reversed?
• Tie-out. Does the signed sum of the lines per account and period agree with the balance in FS10N or FAGLB03?

The header side gives document number, fiscal year, type, document and posting dates, period, currency, reference, user, transaction code and reversal document. The line side gives line item, G/L account, debit/credit, amounts in local and document currency, cost centre, profit centre, order, vendor, customer, item text and assignment, plus their texts.

FBL3N, FAGLL03 and FAGLL03H: the SAP standard way, and where it stops

PostNow.ai sits next to the line item displays you already know. FBL3N is the classic G/L account line item display; FAGLL03 is the new G/L version. On S/4HANA, FAGLL03H and the Fiori app Display Line Items in General Ledger (F2217) read the Universal Journal. Balances come from FS10N or, in new G/L, FAGLB03.

The limits show up at the edges. On ECC, FBL3N and FAGLL03 only list items for accounts that have line item display switched on in the account master (SKB1-XKRES), and open item lists need open item management (SKB1-XOPVW). Header fields such as user and transaction code, and the names of cost centres and partners, need layout changes or a lookup sheet. And every period you export again.

SAP tables behind it: BKPF, BSEG and what changes on S/4HANA

PostNow.ai's FICO-07 joins BKPF (header) to BSEG (lines) on company code, document number and fiscal year, then adds SKAT, CSKT and CEPCT for account, cost centre and profit centre names, LFA1 and KNA1 for partner names, T003T for document type text and T001 for the company.

• BSEG on ECC is a cluster table (cluster RFBLG, with BSEC, BSED, BSES and BSET). It cannot take part in a database join, which is why a quick SE16 join of BKPF and BSEG is a dead end and why full BSEG downloads are slow.
• On S/4HANA the Universal Journal ACDOCA holds the FI, CO and Material Ledger line items. BSEG still exists as the entry view, so totals from BSEG and from ACDOCA can differ, for example where ledger-specific lines exist. BSIS and BSAS, the old G/L open and cleared indexes, are compatibility views there.
• Texts are keyed more tightly than they look. SKAT is keyed by language, chart of accounts and account; CSKT and CEPCT by controlling area, language and a valid-to date (DATBI), so a renamed cost centre has more than one text row.
• Document splitting. In new G/L with splitting, the entry view and the G/L view of the same document can differ. FB03 shows both through the General Ledger View button.

Checks to run before you rely on the extract

1. Build a signed amount. Amount (LC) is stored unsigned; Debit/Credit tells you S (debit) or H (credit). A posted document nets to zero on the signed column when all its lines are in the selection, which is a quick completeness test.
2. Treat reversals as pairs. The original carries the reversal document number; the reversal is its own document with the debit/credit indicators swapped. For activity analysis, keep both or drop both, never one.
3. Tie out per account and period. Sum the signed local amount and compare with FS10N or FAGLB03. Differences usually mean a missing period in the filter, split lines in the G/L view, or, on S/4HANA, ledger-specific lines in ACDOCA that BSEG does not show.
4. Parked and noted documents. A parked document has a header in BKPF with status V but its lines sit in the VBSEG tables, not BSEG. Noted items such as down payment requests (status S) update no balance; leave them out of a tie-out.
5. Filter before you fetch. Company code, fiscal year and a posting date or account range first. A full year of BSEG for a busy company code can run to millions of rows.
6. Do not add document currency across rows. Amount (DC) mixes currencies; total on local currency.

How PostNow.ai runs it

In PostNow.ai you run GL Line Items 360 from the Report Library in the Excel add-in and narrow it with SAP value help on company code, fiscal year, posting date, document date, document number, document type, G/L account, cost centre, profit centre, vendor, customer and user. Rows are read-only from your own SAP session and land in Excel with the texts filled in, so the sheet is ready to pivot. A max-rows guard keeps the first run fast; widen and refresh once the selection is right, and save it to My Reports for next period. For the open-item view of the same postings, use AP Open Items + Aging or AR Open Items + Aging 360. When the review turns up miscoded postings, the reclass entries can go back in from Excel: see FB50 journal entry upload.