Lesson 5 of 5
Testing report continuity
8 min
Listen to this lesson
Report continuity testing answers one question for the business: after the conversion, do our key reports show the same numbers for the same data, and where they differ, do we know why? It is a comparison test, and like every comparison test it needs the same input on both sides, a defined list of what to compare, and an explanation for every difference.
Same data, two systems
In a system conversion the cleanest comparison is the mock itself. Before a mock conversion, run the key reports in the ECC copy for one or two closed periods and save the results. After the mock conversion, run the equivalent reports in the converted system for the same periods. Because the data is the same, any difference comes from the conversion, from a changed report, or from a changed data model, and each kind of difference has a different owner.
- FreezeChoose closed periods (for example March and April) in the ECC copy used for the mock
- Capture beforeRun the key reports in ECC; save outputs with selection parameters
- ConvertMock conversion of the same copy into CMQ
- Capture afterRun the equivalent S/4HANA reports with matching selections
- Compare and explainLine by line; every difference classified, owned and accepted or fixed
| Report | Before (ECC) | After (S/4HANA) | Expected |
|---|---|---|---|
| Cost center actual/plan, Detroit Assembly, April | Cost center report | Same report via compatibility views and the Fiori equivalent | Identical totals by account |
| Trial balance, company code 1710, April | ECC balance report | S/4HANA trial balance | Identical; secondary accounts now visible if in the FS version |
| Contribution margin, April | Costing-based drilldown | Costing-based drilldown and margin analysis query | Costing-based identical; margin analysis bridged |
| Stock value by plant | ECC stock value list | Material ledger stock values | Identical totals per plant |
Contoso's report continuity test list (extract).
Classifying differences
| Class | Example | Owner | Typical outcome |
|---|---|---|---|
| Conversion defect | A cost center total differs by $1,840 after the mock | Conversion team | Fix and re-verify in the next mock |
| Report change | New report groups accounts differently | Report owner | Adjust report or accept with explanation |
| Data model change | Secondary costs now on the trial balance | Finance process owner | Accept; update the financial statement version if needed |
| Approach change | Margin analysis COGS differs from costing-based value field | Finance process owner | Explain in the bridge; accept |
The evidence is a comparison workbook per report: selection parameters on both sides, the figures, the differences, and for each difference a class, an explanation, an owner and a decision. The test passes when every difference is explained and accepted by the report owner, not when the figures match. Some differences are the point of the conversion; a secondary cost now visible on the trial balance is a feature. What matters is that nobody is surprised by it in the first real close.
Making comparisons repeatable
Comparisons are only useful if they can be repeated quickly on every mock. Save the selection parameters for each report as variants on both sides, so the same report runs the same way each time. Keep the comparison workbook template stable, with columns for figure, before, after, difference, class, explanation, owner and decision. Where possible, compare at the level the business reads (account, cost center, product, customer) and add a total line that ties to the trial balance, so a difference can be located quickly. Store workbooks with the test cases in SAP Cloud ALM; mock 2 should start from the mock 1 workbook with every accepted difference already explained, so the team only investigates what is new.
Repeat the comparison on each mock and on the dress rehearsal. Differences fixed in mock 1 should not reappear in mock 2, and the dress rehearsal comparison is the one Dan signs against. After go-live, the first two closes in CMP are compared with the last close in EP1 in the same way, which turns report continuity from a test into a habit.
What would you do?
In mock conversion 2, the Detroit Assembly cost center report for April shows $1,840 more in S/4HANA than in ECC. In mock 1 the totals matched. What should Priya's team do?
- Compare key reports before and after each mock conversion on the same closed periods.
- Classify every difference: conversion defect, report change, data model change or approach change.
- The test passes when every difference is explained and accepted, not only when figures match.
- Repeat on every mock, the dress rehearsal and the first closes after go-live.
Check your understanding · not graded
Lesson check
1. What is the cleanest data source for a before-and-after report comparison?
2. When does a report continuity test pass?
3. A difference appears in mock 2 that was not in mock 1. What is it?