The income statements the migration leaves behind
Decades of management reporting live in painter libraries: hundreds of reports whose rows and columns encode how the business reads its numbers. The vendor’s roadmap for the tool is the subject of a support note, and the replacement is not one thing.
◆ The note and the fragmentationone tool retired, several partial successors.
SAP support note 3539674 covers the future roadmap of transaction GR55, the entry point for Report Painter and Report Writer report groups. Teams reading it are being pointed away from the tool their statement library is built in. The replacement path is fragmented: some delivered apps cover common financial statements, embedded analytical queries can be rebuilt line by line, and other needs route to separate analytics products.
The gap shows in the questions practitioners still ask in 2024 and 2025: what, concretely, replaces a multi-step income statement built in painter rows. A library of hundreds of painter reports is not decoration. Each one encodes a statement definition, which accounts roll into which named line, in which order, against which comparison columns. That encoding is the asset, and it does not migrate by itself.
◆ What the library actually encodesand where each piece goes in the rebuild.
| In the painter library | In the rebuild |
|---|---|
| Row definitions: account sets rolling into named statement lines | A versioned row-definition table, one row per statement line per version. |
| Column definitions: periods, plan versions, comparisons | Query logic over the same table, parameterized by period and version. |
| Report groups: which statements run together | A model layer in the warehouse, built and scheduled as one unit. |
| Undocumented fixes accumulated over years | Reviewed changes with history, because the definitions are code now. |
◆ The owned rebuildstatement logic as code, on data you extracted.
The build reproduces management income statement formats on universal-journal data landed by the extraction pattern. The row-definition table is the heart of it: every statement line is a row that maps accounts to a position, and every change to it is versioned, reviewed, and tested before the statement moves. Queries join postings to definitions, so a hundred statements are one join with a hundred parameter sets, not a hundred rebuilt screens.
-- a statement is a join, not a screen
SELECT rd.line_no, rd.line_label, SUM(j.amount) AS amount
FROM fct_journal j
JOIN dim_stmt_row rd
ON j.account BETWEEN rd.acct_from AND rd.acct_to
AND rd.stmt_id = 'MGMT_PL_V4'
WHERE j.fiscal_month = '2026-06'
GROUP BY 1, 2 ORDER BY 1
The delivered financial statement report and its limits are covered under general ledger. This page is for the layouts the delivered formats never matched, which is what the painter library was for.
- SAP
- The vendor. Systems, Applications, and Products in data processing.
- HANA
- SAP’s in-memory database, the platform S/4 runs on.
- ERP
- Enterprise resource planning, the system of record for operations and finance.
- Report Painter
- The classic SAP tool where statement layouts are drawn as rows and columns.
- report group
- A bundle of painter reports run together through one transaction.
- row definition
- The mapping of accounts into one named statement line.
- universal journal
- The single line-item table where S/4 finance postings land.
- management income statement
- The internal profit statement in the format leadership reads.