Lesson 4 of 5
Reports
10 min
Listen to this lesson
Report continuity is where controllers feel the conversion. The numbers may be right, but if the monthly contribution margin report, the cost center variance report and the plant absorption report look different, people stop trusting them. Planning report redesign early, with the people who use the reports, is the best way to avoid a go-live that is technically sound and practically rejected.
Building the report inventory
Start with an inventory of every controlling report in use: standard reports, Report Painter and Report Writer reports, costing-based CO-PA drilldown reports, custom ABAP programs, spreadsheets fed by extracts, and data warehouse reports that read controlling data. For each, record the owner, the users, the frequency, the decisions it supports and the data it reads. Usage statistics from the ECC system help separate reports that are run every month from reports nobody has opened in a year.
| Report type | What happens after conversion | Typical action |
|---|---|---|
| Standard CO reports (cost center line items, plan/actual) | Keep working through compatibility views | Test; consider the Fiori equivalent |
| Report Painter / Report Writer reports on cost centers | Generally keep working | Test totals; check accounts that changed type |
| Costing-based CO-PA drilldown reports | Work only while costing-based CO-PA stays active | Rebuild on margin analysis before retirement |
| Custom ABAP reading or writing old CO tables | Reads may work via compatibility views; writes need rework | Custom code analysis; fix or replace |
| Extracts to a data warehouse | Extractors and data models may change | Check with the analytics team; re-map history |
What happens to each kind of controlling report in a conversion.
Prefer embedded analytics
Margin analysis and the Universal Journal are designed for reporting with CDS-based queries: one data source, real-time, reconciled with the P&L. SAP Fiori analytical apps cover many standard controlling needs, and custom queries can fill the gaps without copying data. A good rule: rebuild a report on embedded analytics if it reads S/4HANA data and serves operational or monthly decisions; keep it in an external analytics layer if it needs data from several systems or long history from before the conversion.
- InventoryAll CO reports with owners, users, frequency and decisions supported
- TriageKeep as is / rebuild on embedded analytics / retire
- Design with usersMock-ups agreed with the people who read the report
- Build and reconcileNew report built; totals tied to the trial balance
- CompareOld and new report on the same period; differences explained
Design with the readers
Redesign is a chance to improve reports, but the first goal is trust. Agree a mock-up with the people who read each priority report before anything is built. Keep the familiar structure where it still makes sense: the same rows, the same totals, the same order of lines. Where the new data model changes a number, for example because COGS is now split into components or secondary costs now sit on visible accounts, show the change explicitly in the first months, with a note or a reconciliation line, rather than hoping nobody notices. A report that looks familiar and explains its differences gets adopted; a report that looks better but cannot be tied to last month gets rebuilt in a spreadsheet by the users, and then you have two problems.
Watch the reports that feed other systems as much as the ones people read. Extracts to planning tools, bonus calculations, transfer pricing files and bank covenant reporting often read controlling data and are rarely on anyone's report list. Ask the interface owners and finance operations directly; these are the reports whose differences cost real money.
What would you do?
The monthly contribution margin report in ECC is a costing-based CO-PA drilldown. Contoso keeps costing-based CO-PA for the fiscal year. The report owner wants to "leave it alone until December." What is the risk, and what do you recommend?
- Inventory every controlling report with owner, users, frequency and the decisions it supports.
- Standard and Report Painter reports mostly keep working; costing-based drilldowns and custom table writers need action.
- Prefer embedded analytics on the Universal Journal; keep cross-system and long history in external analytics.
- Rebuild during the parallel period and compare old and new on the same data.
Check your understanding · not graded
Lesson check
1. Which report needs a rebuild before costing-based CO-PA is retired?
2. Where should a monthly margin report on S/4HANA data usually be rebuilt?
3. What helps separate active reports from unused ones in the inventory?
4. Which reports are most often missing from a report inventory and cost real money when they change?