Video Briefing
This video explains why SAP regression cycles take weeks. Because nobody can produce a list of what a transport changed, its dependencies, and what production actually uses, testing everything becomes the only defensible option. Chris Carpenter of Merito walks through checks any team can run this week, covers SAP data showing 40 to 60% of custom ABAP never executes in production, and explains how change impact analysis (LiveCompare, SAP CIA, or bundled with Tricentis Tosca) shrinks regression scope based on risk.
Key Takeaways
SAP regression takes weeks because nobody can prove what a transport touched, so teams rationally test everything.
SAP's own guidance says 40 to 60% of custom ABAP code never executes in production, which inflates test scope with dead code.
Change impact analysis works in 3 steps. It resolves every object a transport touches including standard SAP code, weights the graph with production usage, and matches scope against existing tests.
Percentage of test cases executed measures team activity, not test coverage. The better metric is the share of changed and used objects validated before the release gate.
Fiori sits on OData services and CDS views that ABAP tooling cannot see, so a CDS change can silently break apps.
LiveCompare is sold standalone, as SAP Change Impact Analysis, or bundled with Tricentis Tosca as SAP Enterprise Continuous Testing, and buying the wrong packaging is a common avoidable mistake.
Consultation request
Use this form to talk through the workflow, platform fit, and delivery priorities behind this video with a Merito specialist.
Discovery
Use the conversation to translate what you saw here into a practical next step for your team.
Alignment
We route the request to the team best suited for platform strategy, implementation, quality, or AppSec delivery work.
Get Started
The request is protected by reCAPTCHA Enterprise and processed through Merito's standard consultation flow.