> 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/command-line-interface/create-an-initial-build-map-for-your-pipeline.md).

# Create an Initial Build Map for your Pipeline

A Pipeline's Initial Build Map is a snapshot of the standard and custom ABAP code components in the Pipeline's QAS system (and their related objects), based on usage data from the Pipeline's Production system.

{% 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 %}

{% hint style="info" %}
By default, SAP Basis objects (delivery units **SAP\_BASIS**, **SAP\_UI**, **SAP\_GWFND**, and **PERSONAS**) are excluded from the build map. To customize which components are excluded, use the `[componentstoignore]` section in `config.toml`. See [Configuration settings](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/configuration-settings.md#componentstoignore).
{% endhint %}

{% hint style="info" %}
This procedure reads `config.toml` and reads and writes the agent's local data under the agent's `userdata` directory (by default `%ProgramData%\Tricentis\SeaLights\ABAP Agent`). Install the agent with `slabapcli setup install` before you run `buildmap run`.
{% endhint %}

## `slabapcli buildmap run`

Creates an Initial Build Map for a pipeline. The agent schedules a one-time `INIT_BUILD_MAP` Windows Scheduled Task that runs approximately one minute after the command is issued.

{% tabs %}
{% tab title="Command Prompt" %}
{% code title="Syntax" overflow="wrap" %}

```batch
slabapcli.exe buildmap run --pipeline <pipeline-name>
```

{% endcode %}
{% endtab %}

{% tab title="PowerShell" %}
{% code title="Syntax" overflow="wrap" %}

```powershell
.\slabapcli.exe buildmap run --pipeline <pipeline-name>
```

{% endcode %}
{% endtab %}
{% endtabs %}

| Parameter          | Required | Description                                      |
| ------------------ | -------- | ------------------------------------------------ |
| `-p`, `--pipeline` | Yes      | The pipeline name (as shown in `pipeline list`). |

### Example

{% tabs %}
{% tab title="Command Prompt" %}
{% code title="Command" overflow="wrap" %}

```batch
slabapcli.exe buildmap run --pipeline "ALM_Demo-S21"
```

{% endcode %}
{% endtab %}

{% tab title="PowerShell" %}
{% code title="Command" overflow="wrap" %}

```powershell
.\slabapcli.exe buildmap run --pipeline 'ALM_Demo-S21'
```

{% endcode %}
{% endtab %}
{% endtabs %}

{% code title="Expected output (PowerShell)" overflow="wrap" lineNumbers="true" %}

```log
.\slabapcli.exe buildmap run --pipeline 'ALM_Demo-S21'
[2025-06-17 15:28:19.806+01:00] [info] Detected Windows version: Windows 11
[2025-06-17 15:28:19.807+01:00] [info] Config pathname: C:\ProgramData\Tricentis\SeaLights\ABAP Agent\config\config.toml
```

{% endcode %}

The agent creates a scheduled `INIT_BUILD_MAP` task that runs **once only** (approximately one minute from now) to create the Initial Build Map.

{% hint style="info" %}
You can also create an Initial Build Map directly by running `watcher.exe INIT_BUILD_MAP --pipeline <pipeline-name>` from the command line.
{% endhint %}

In SeaLights, select the **Filter** button to add the app for your Initial Build Map to the Coverage Dashboard.

{% hint style="warning" %}
**Before Build Modifications:** Wait until the Initial Build Map has finished successfully for this pipeline before starting Build Mods (`slabapcli buildmods run` or watcher `BUILD_MODS`). Do not start Build Mods while `INIT_BUILD_MAP` is still running — overlapping build-mode tasks exit with watcher code `11`. The same applies in reverse: if Build Mods is running for the pipeline, the Initial Build Map task exits with code `11`, so stop it first. Running `buildmap run` again for a pipeline stops an Initial Build Map that is still in progress and schedules a new one.
{% endhint %}

### Package coverage and Build Modifications

The packages in the Initial Build Map come from the production usage data of the pipeline's PRD system. Build Modifications use the same scope: they only include objects in these packages, plus objects in customer packages (packages whose names start with `Z` or `Y`). Deleted objects are not limited. Build Modifications therefore need the production usage data that this procedure creates for the PRD RFC Destination. See [Monitor your Pipeline for Build Modifications](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface/monitor-your-pipeline-for-build-modifications.md#which-objects-are-included).

### Long runs on large systems

On a large SAP system, the Initial Build Map can take many hours. The watcher waits up to 1000 hours for each step of the run, so a long run is not cut off. Watcher exit code `18` (task timeout) means that a single step exceeded that limit; see [Watcher Exit Codes](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface/monitor-your-pipeline-for-build-modifications.md#watcher-exit-codes).

<figure><img src="https://4057366433-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAjqTCMRYvHhDgsdPLUnc%2Fuploads%2FkptVzkETaCmCGPZAJIQz%2Fimage.png?alt=media&amp;token=002552bb-60c7-4577-b7b5-cce8e309014e" alt="" width="563"><figcaption></figcaption></figure>

<figure><img src="https://4057366433-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAjqTCMRYvHhDgsdPLUnc%2Fuploads%2FhtQNmrZSWHfgSlOL1Owv%2Fimage.png?alt=media&amp;token=ec792d20-05bb-43e9-9fe8-02733aba0bb9" alt=""><figcaption></figcaption></figure>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sealights.io/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface/create-an-initial-build-map-for-your-pipeline.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.