> 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/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0.md). # ABAP Agent {% hint style="danger" %} **ABAP Agent is not compatible with ABAP Agent 1.3.0.70 and earlier.** You cannot continue using your existing 1.3 installation, SAP add-on, local agent data, or SeaLights application history with the current release. See [Upgrading ABAP Agent version](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/upgrading-abap-agent-version.md#compatibility-with-earlier-abap-agent-versions) for the full requirements and required actions. Documentation for the legacy product line (1.3 and earlier) is under [ABAP Agent 1.x](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/abap-agent.md) in this section. {% endhint %} ## What's new in 2.0 ABAP Agent 2.0 re-architects the agent into a coordinated local stack and adds test-impact capabilities that connect ABAP code changes to the business processes they touch — and to the tests that exercise them. The main additions: * **New modular agent design:** The CLI registers Windows Task Scheduler jobs that run `watcher.exe`; the watcher orchestrates Initial Build Map and test-repository search via `SLABAPServer.exe` (CAPI / AdapterHost), and runs Build Modifications and Footprints locally. See [Create an Initial Build Map for your Pipeline](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface/create-an-initial-build-map-for-your-pipeline.md) and the [Command-line interface](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface.md). * **Scan Test Repositories and map tests to business contexts:** Connect the agent to your test management tools — such as Azure DevOps, Tosca Commander, Tosca Cloud, Excel, Xray, qTest, Certify, SAP Solution Manager (SSM), and OpenText ALM — through adapters (`testrepo`). A scheduled scan (`search_testrepo`) searches those repositories for tests covering the business contexts impacted by recent changes and reports the matches to SeaLights. That turns "what changed in SAP" into "which existing tests validate it," so teams know what to run instead of re-running everything. * **Code-to-business-context mapping:** 2.0 maps each changed ABAP object to the business context it belongs to — the transaction, Fiori app, or Web Dynpro application a business user actually runs — and groups impact and coverage by that context. Instead of a flat list of technical objects, stakeholders see impact and test coverage in business terms. * **Fiori Launchpad enrichment (`upload_flpca`):** Import your Fiori Launchpad catalog (`/UI2/FLPCA`) so transaction-based business contexts are enriched with Fiori app titles and keywords. **Required for Fiori** — complete per-RFC import before `search_testrepo`. Optional enrichment for landscapes without Fiori-driven processes. * **New SAP add-on:** A new ABAP add-on specific to 2.0 must be installed in your SAP system. This add-on is **not backwards compatible** — it does not support earlier ABAP Agent versions (1.x). See [Install the ABAP addon](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/install-the-abap-agent/install-the-abap-addon.md) for details. Details for each change are covered on the relevant pages in this section. ## Introduction The SeaLights ABAP Agent continuously monitors changes made to an SAP application, and identifies whether tests you've run in Tosca exercise these changes. This allows you to see the test coverage for new or changed ABAP components in SeaLights, and identify ABAP components that don't yet have any tests. The agent has a command-line interface which allows you to do the following: * Install the agent and connect it to SeaLights. * Create RFC Destinations to connect to your QAS and Production systems. * Create Pipelines to identify QAS and Production systems in your SAP landscape. For version history, see the [ABAP Agent release notes](https://docs.sealights.io/knowledgebase/agent-release-notes/abap-technologies/abap-agent). The SeaLights ABAP Agent lets you create the following: ### Initial Build Map The agent uses a watcher program which you run once for each Pipeline to create an Initial Build Map. The agent creates an Initial Build Map as follows: * It retrieves usage data for standard and custom objects from the Pipeline's Production System and finds the Development Class or Package associated with each used object. By default, the agent retrieves the last 13 months of usage data. * It accesses the Pipeline's QAS system to retrieve all the objects that belong to each Development Class or Package. * It sends the objects to SeaLights. The agent stores the Initial Build Map in a SeaLights app named after the Pipeline. You can add each app to the SeaLights Coverage Dashboard. The agent stores the following code objects in the Initial Build Map: * Programs * Functions * Function Groups * Classes * Methods * Enhancement Objects ### Build Modifications The agent uses a watcher program which runs every five minutes and checks for code changes made to a Pipeline by transports imported into its QAS system. The agent stores the changes in Build Modifications, and adds these to the Pipeline's app that you can add to the SeaLights Coverage Dashboard. ### Footprints If you have connected Tosca to SeaLights, you can configure the watcher program to check for test executions in Tosca and report these to SeaLights. When you run a test in Tosca, the agent matches the ABAP components that you ran in the test against objects in the latest Build Modification. It then sends this data to SeaLights as a Footprint. SeaLights processes the Footprint data and updates the test coverage for the ABAP objects in the latest Build Modification. You can see the test coverage in your SeaLights app's Coverage Report. ## System requirements The ABAP Agent relies on **SCMON** for data collection, which is available from **SAP NetWeaver 7.4 SP08** onward. The SAP system must therefore be **version 7.4.8 or higher**. Supported systems include SAP S/4HANA Cloud (Private Edition), SAP S/4HANA Enterprise Management, and SAP ECC. The watcher program runs under Windows. See [Prerequisites & Limitations](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/install-the-abap-agent/prerequisites-and-limitations.md) for the full list of system, SAP, and permission requirements. ## Software components We deliver the SeaLights ABAP Agent 2.0 in a ZIP file that includes an installer and the following components: * **ABAP addon:** A new SAP addon for ABAP Agent 2.0 that includes the agent's SAP components. This add-on must be installed in your SAP system and is **not backwards compatible** with earlier ABAP Agent versions (1.x). * **Installer:** A Windows setup program (`SeaLights_ABAP_Agent_Setup.exe`) that installs the agent binaries, configures directories and permissions, and handles upgrades automatically. * **WATCHER**: A program that watches for ABAP changes and reports them to SeaLights. * **SLABAPCLI:** A command-line interface program that lets you configure the ABAP Agent and connect it to SeaLights. * **SLABAPServer.exe:** A .NET localhost HTTP server that coordinates agent operations and launches the adapter host. Required for `testrepo test`, `search_testrepo`, and `upload_flpca import` operations. Can run interactively or as a Windows service. * **SLABAPAdapterHost.exe:** A .NET host process for test-repository adapters (Azure DevOps, Tosca Commander, Tosca Cloud, Excel, Xray, qTest, Certify, SAP Solution Manager (SSM), OpenText ALM, and others). --- # 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/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0.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.