Analytics Catalog/SAP S/4HANA/General Ledger/Financial Statement
Explore the catalogTrial BalanceG/L line itemsACDOCAExtraction
SAP S/4HANA · General Ledger (FI-GL)

Financial Statement

The balance sheet and income statement (P&L) — account balances rolled up the FSV hierarchy into assets, liabilities, equity, revenue, and expenses, and reconciled back to the trial balance. Built on I_GLAccountLineItemCube.

Sample build of the Financial Statement — balances arranged on the FSV hierarchy into a balance sheet and P&L, with period vs prior-period comparison, and rendered tool-neutral so it runs in Power BI, SAC, or Tableau.

Financial Statement sample
balanced · FSV CORP · period 04 / 2026
Filters
Ledger
0L · Leading
Company code
1010
Statement version
CORP
Period
04 · 2026
102.70M
Total assets
102.70M
Liab + equity
31.00M
Revenue
6.30M
Net income
Statement itemThis periodPrior periodΔ
Total assets102,700,00099,400,000+3.3%
Total liabilities41,100,00039,800,000+3.3%
Total equity61,600,00059,600,000+3.4%
Revenue31,000,00028,500,000+8.8%
Operating expenses24,700,00023,900,000+3.3%
Net income6,300,0004,600,000+37.0%
AI Analyst · active
reading

Account balances — including the Period 0 carryforward — are rolled up the FSV hierarchy: assets, liabilities, and equity for the balance sheet; revenue and expense for the P&L. Net income falls out as revenue minus expense, and assets equal liabilities plus equity, so the statement balances.

flag

Net income is up 37% year on year, driven by one revenue node with no matching expense movement. Worth confirming it isn't a period-cutoff or accrual-timing effect before it posts to retained earnings.

root cause & next step

A statement only shows accounts the FSV maps. An account missing from the FSV silently drops off the statement while still showing in the trial balance — so reconcile the statement total back to the trial balance to catch unassigned accounts.

Illustrative data · assets = liabilities + equity · reconciled to the trial balance · runs on your warehouse. See it live →
ACDOCA · incl. Period 0+FSV hierarchy────▶Financial Statement

The report's query logic — it sums I_GLAccountLineItemCube to an account balance, then rolls each account up the FSV hierarchy to its statement line. The same SQL becomes a dbt model in your warehouse.

How it interconnects: it reads the released cube (including the Period 0 carryforward, so balances are right), then joins the FSV hierarchy — the account-to-statement-line mapping maintained in Manage Global Hierarchies (config table T011). It never reads the legacy FAGLFLEXT / GLT0 balance views.
SQL data set · genericized · parameterized · balances rolled up the FSV hierarchy
Show / hide SQL
WITH bal AS (
  SELECT c.RACCT AS gl_account,
         SUM(c.AmountInCompanyCodeCurrency) AS balance   -- incl. Period 0 carryforward
  FROM   I_GLAccountLineItemCube AS c
  WHERE  c.Ledger       = :P_LEDGER
    AND  c.CompanyCode  = :P_COMPANY_CODE
    AND  c.FiscalYear   = :P_FISCAL_YEAR
    AND  c.FiscalPeriod <= :P_TO_PERIOD                    -- 0 = carryforward .. period
  GROUP  BY c.RACCT
)
SELECT f.StatementType            AS statement_type,       -- BS = balance sheet, PL = P&L
       f.FSVNode                  AS fsv_node,
       f.FSVNodeText              AS fsv_node_text,
       SUM(b.balance)             AS node_balance
FROM   bal b
JOIN   I_FinancialStatementVersionNode AS f                -- the FSV hierarchy mapping
       ON  b.gl_account = f.GLAccount
WHERE  f.FinancialStatementVersion = :P_FSV                 -- e.g. CORP
ORDER  BY f.StatementType, f.FSVNode;
One rule that catches people: an FSV has to be replicated to the hierarchy runtime before the statement will use it, and any account not assigned to the FSV drops silently off the statement — while still showing in the trial balance. Reconciling the statement total to the trial balance each close is how you catch unassigned accounts (SAP KBA 2829249).

The data-warehouse model — one balance fact surrounded by conformed dimensions (what you slice by) and measures (what you aggregate), expressed as dbt so it migrates with you. Grain: one row per account · ledger · period; the FSV hierarchy is a conformed dimension.

dim_gl_accountaccount · master dim_fsv_nodeFSV hierarchy · BS / PL dim_company_codeledger · segment dim_datefiscal period fct_gl_balancefact · one row per account · periodbalance · this period · prior period
●— fact → dimension join
ElementTypeDefinition
dim_gl_accountdimensionAccount master (SKA1 / SKAT)
dim_fsv_nodedimensionFSV hierarchy — statement line, balance-sheet / P&L side
dim_company_codedimensionCompany code & ledger context (RLDNR)
dim_datedimensionConformed calendar — fiscal year & period
balancemeasureAccount balance incl. the Period 0 carryforward
period_balancemeasureBalance for the reporting period
comparison_balancemeasureBalance for the prior comparison period
Runs on your cloud warehouse — Snowflake, BigQuery, Redshift, or Synapse on AWS, Google Cloud, or Azure. Assets equal liabilities plus equity, and the statement reconciles to the trial balance — 0% variance by design. You own the code, the model, and the data.
How the data gets here: a SAP-compliant extract of ACDOCA — released CDS view via SLT, or Table / Table-CDC — never ODP-RFC (prohibited under SAP Note 3255746, blocked June 2026). See the extraction pattern & data flow →
See the complete model
How this report's fact and dimensions fit the full ACDOCA-centered picture, via conformed keys.
General Ledger data model → Enterprise model →

Every source object behind this report. Each linked object has its own page — with its fields and its real S/4HANA status, so you build on the right thing.

ObjectRoleKey fieldsS/4HANA status
I_GLAccountLineItemCubeReleased cube over ACDOCA incl. the Period 0 carryforward — the read objectreleasedReleased CDS view
ACDOCAUniversal Journal — the balances behind every statement line6 PK · 360+Transparent table
FSV hierarchy (T011)Financial Statement Version — maps each account to its statement lineconfigGlobal hierarchy
SKA1 / SKATG/L account master & textSAKNRTransparent table
Trial BalanceThe flat balance the statement reconciles to — catches unassigned accountsreportReconcile target
FAGLFLEXT / GLT0Legacy G/L balance tables — reference only, do not extractCompat view → ACDOCA
Key fields = the primary key plus the columns this report selects; S/4HANA status = whether the object is a live transparent table, a released CDS view, or a compatibility view over ACDOCA. The compat views are referenced by legacy joins but are never the extraction source — that's the point, not a gap.
Want this built & owned?
A reconciled, customer-owned financial statement on ACDOCA, on your cloud — your team owns the code. Ten-day proof of concept.
Download the GL pack → Talk to us →
Terms on this page
Financial statement
The official balance sheet and income statement produced from the ledger.
FSV
Financial Statement Version — the hierarchy that maps each account to a statement line.
Balance sheet
A snapshot of assets, liabilities, and equity at a point in time.
Income statement
Revenue minus expenses for a period — the P&L; its result is net income.
Net income
Profit for the period — revenue less expenses — which flows into equity.
Contra node
An FSV node where an account shows on the debit or credit side by its balance.
Balance carryforward
The year-end run that brings balance-sheet openings into the new year.
Period 0
How ACDOCA stores the carryforward — a special "period zero" document.
ACDOCA
SAP's single table holding every finance posting (the "Universal Journal").
I_GLAccountLineItemCube
The released view that includes the carryforward, so balances come out right.
Ledger
A parallel set of books (local GAAP, IFRS, group) — 0L is the leading ledger.