SAP Coverage Analysis now displays every executable and object impacted by an SAP change by default, giving release owners evidence of the full tested scope before they approve deployment.
Full impact scope replaces the gap-only default
Previously, the Coverage Analysis table emphasized what remained untested. Fully covered objects, executables, and even entire application areas could disappear from the detailed view. Although teams could see an aggregate coverage percentage, they could not inspect the complete set of changed items that produced it.
September 2026 makes the complete impact view the standard experience. Release stakeholders can now review:
- Every executable affected by a change
- Every impacted object within those executables
- Covered and uncovered items in the same review context
- Application areas that have complete coverage
This matters when a release decision requires more than a percentage. A quality leader can confirm that critical changes were exercised, while a release manager can identify residual gaps without moving between separate reports.
Per-object status makes coverage evidence reviewable
Each object row now includes a clear Covered or Uncovered indicator in the Change Coverage column. That gives QA, SAP functional teams, and control owners a direct way to inspect test evidence at the object level.
For enterprise governance, this reduces ambiguity in common questions:
- Which changed objects were exercised by testing?
- Which executables are fully covered?
- Are there uncovered changes in a business-critical application area?
- Does the release record show the scope that was considered at approval time?
The visibility is especially useful where SAP changes span multiple teams and ownership boundaries. Coverage discussions can be based on identified objects rather than a high-level score alone.
Keep gap-focused triage when it is the right workflow
The new default does not remove the operational value of a concentrated gap list. Teams can activate Uncovered Objects Only to filter the table to objects that still need attention.
With the filter enabled, Sealights hides:
- Executables with no uncovered objects remaining
- Application areas with no executables remaining in the filtered result
This supports two distinct review modes. The full view supports release assurance and evidence review. The uncovered-only view supports daily test planning, defect follow-up, and risk-based remediation. Teams can switch between them without losing the broader context, which is useful when deadlines are tight.
Improve auditability of SAP release decisions
The selected table view can be shared or archived as shown, including the active filter context. That creates a more defensible record for change advisory reviews, regulated delivery controls, and internal audit requests.
Organizations should define how this evidence fits into their release process. A practical policy may require:
- Full-scope review for production approval of material SAP changes
- Uncovered-only review to document accepted residual risk
- Archived evidence linked to the change or release record
- Named accountability for exceptions and compensating controls
The update does not replace risk assessment. It does make the testing evidence behind that assessment much easier to inspect. Teams will need to agree what coverage level and what types of uncovered objects require escalation.
Workflow impact for QA, DevOps, and SAP delivery leaders
QA leaders gain a clearer basis for confirming test completion. DevOps and release managers gain a view that better aligns with deployment governance. SAP engineering teams can distinguish genuinely complete coverage from a table that simply omitted fully covered work.
For senior leaders, the main value is control quality. The change helps connect release approval to an observable inventory of impacted objects and their coverage state. It also makes reporting more consistent across teams that formerly used different interpretations of a gap-only screen.
How Merito helps
Merito helps enterprises incorporate Sealights coverage evidence into practical SAP release governance. We can assess current approval workflows, define coverage and exception policies, map evidence to audit requirements, and help teams standardize dashboards and operating procedures across QA, DevOps, and SAP delivery functions.
The aim is not more reporting. It is a repeatable decision process where release owners can see the full change scope, identify remaining gaps, and record why a release was approved.
Merito is an authorized Tricentis reseller and services partner, listed as a Certified Solution Partner in the Tricentis partner directory. Our Tricentis Sealights team can scope licensing, sizing, and rollout for September 2026, and our enterprise upgrade services help you plan and validate the upgrade with minimal disruption to release schedules.
