> For the complete documentation index, see [llms.txt](https://sealights-docs.tricentis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sealights-docs.tricentis.com/setup-and-configuration/abap-agent-2.0.md).

# ABAP Agent

## Introduction

The SeaLights ABAP Agent continuously monitors changes made to an SAP application, and identifies whether tests you've run in your connected test tools 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).

### Where to start

New to the ABAP Agent? Follow this path:

1. **Understand the concepts** — [Concepts](broken://pages/oMfktNYbgWdVRfiH7HPM) explains the architecture and how SAP objects map to coverage data.
2. **Install and configure the agent** — [Install the ABAP Agent](broken://pages/RVJ0Dzu84lPtG9vQelRG) walks through the SAP add-on, authorizations, and agent binaries.
3. **Follow the onboarding guide** — [Guides](broken://pages/nEgrwph59EDjWWrTfFhb) is a step-by-step path from a finished install to your first Test Cycle recommendations.

## What's new in 2.1

ABAP Agent **2.1** (current release build **2.1.2.175**) extends the 2.0 architecture with:

* **Incremental Build Mods processing:** After transport discovery, Build Mods cache entries and cross-reference links refresh only for added, changed, or deleted objects — not the entire landscape on every run.
* **Most-at-Risk data:** The Initial Build Map and Build Modifications provide the data SeaLights uses to identify and rank the executables most at risk from your changes. See [Most at Risk Executables](https://docs.sealights.io/knowledgebase/test-optimization/test-optimization-for-sap/test-recommendations-for-manual-testing/how-sealights-builds-test-recommendations-for-sap/most-at-risk-executables) and [Most-At-Risk Ranking](https://docs.sealights.io/knowledgebase/knowledge-base/sealights-for-abap/how-it-works/day-zero-structural-analysis-no-execution-history-required/most-at-risk-ranking).
* **OpenText Octane and SAP Cloud ALM adapters:** New test-repository integrations alongside the existing adapter portfolio.
* **Windows service lifecycle:** `slabapcli setup install` registers the **SeaLights ABAP Server** service; most lab settings hot-reload while `sealights.token` requires a service restart.
* **Reliable in-place upgrades:** Setup force-replaces packaged `bin` files so stale binaries do not survive equal-version upgrades.

See the [ABAP Agent release notes](https://docs.sealights.io/knowledgebase/agent-release-notes/abap-technologies/abap-agent) for the full 2.1 change list.

### 2.1.2

Release build **2.1.2.175** adds the following:

* **Critical list upload:** `slabapcli upload critical_list` uploads a critical list (a CSV file of business-critical SAP objects) to the pipeline's SeaLights app. See [Upload a Critical List](broken://pages/RyMh0JbwIMIXBvLuyPT5).
* **Build modifications bug fixes:** General fixes and improvements to build modification monitoring. See [Monitor your Pipeline for Build Modifications](broken://pages/JZVVGs3ieGcAwmbZ8qqj).
* **Tosca Cloud adapter bug fixes:** General fixes to the Tosca Cloud test repository adapter. See [Connect Tosca Cloud to SeaLights](broken://pages/KWz17kExfX3vexGN20xZ).

## Architecture (introduced 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, Build Modifications, and test-repository search via `SLABAPServer.exe` (CAPI / AdapterHost), and runs Footprints locally. See [Create an Initial Build Map for your Pipeline](broken://pages/6f4WDLP7ZxZdqhvqwcMb) and the [Command-line interface](broken://pages/PpeeqpK0FATYS7huqS2l).
* **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), OpenText ALM, OpenText Octane, and SAP Cloud 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** — import the Excel export for each pipeline's PRD RFC 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 add-on](broken://pages/KA26qNyaJ9N3X9bfhQmb) for details.

Details for each change are covered on the relevant pages in this section.

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](broken://pages/NH2qyXJr7ew3TzIxA4aj) for the full list of system, SAP, and permission requirements.

## Software components

We deliver the SeaLights ABAP Agent in a ZIP file that includes an installer and the following components:

* **ABAP add-on:** A new SAP add-on 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 local background service that coordinates agent operations and launches the adapter host. Required for `testrepo test`, `search_testrepo`, and `upload_flpca import` operations. `slabapcli setup install` registers the **SeaLights ABAP Server** Windows service; after you set the SeaLights token, start it with `slabapcli server start` (it also starts automatically when the machine restarts).
* **SLABAPAdapterHost.exe:** A host process for test-repository adapters (Azure DevOps, Tosca Commander, Tosca Cloud, Excel, Xray, qTest, Certify, SAP Solution Manager (SSM), OpenText ALM, OpenText Octane, SAP Cloud ALM, and others).