> For the complete documentation index, see [llms.txt](https://docs.sealights.io/knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealights.io/knowledgebase/knowledge-base/sealights-for-abap/intro-to-sealights/what-is-sealights.md). # What is SeaLights for ABAP SeaLights for ABAP is a change impact analysis and test optimization platform purpose-built for SAP environments. It automatically connects every SAP transport (a package of code or configuration changes) to the tests that actually cover it — so teams always know which changes landed, which ones have been verified, and which ones carry undetected risk. *** ### Business Value & Key Use Cases **Who benefits:** QA Leads, Release Managers, SAP Basis Teams, Test Architects, Compliance/Audit stakeholders. #### Real-World Scenarios This Solves * **Targeted regression testing after a transport import** — Instead of running 9,000 tests to be safe, SeaLights identifies the exact subset (e.g., 167 tests) that covers every changed object, delivering up to 96% test savings per cycle. * **Proving coverage for audits and sign-offs** — Release owners receive an automatically generated, business-readable coverage report organized by App Area → Executable → Object, retained per cycle for audit replay with no manual reconstruction required. * **Finding blind spots before go-live** — The Test Gaps tab surfaces every changed object with zero test coverage, so teams can consciously decide to test, write a new test, or formally accept the risk — nothing goes unnoticed by default. * **Accelerating ECC-to-S/4HANA migrations and upgrades** — SeaLights supports S/4HANA upgrades, support packs, feature packs, custom releases, and third-party add-on upgrades, providing immediate impact analysis from the first transport import. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.sealights.io/knowledgebase/knowledge-base/sealights-for-abap/intro-to-sealights/what-is-sealights.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.