> 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-1.5/command-line-reference/build-maps.md).

# Build Maps

To analyze transport changes you make to a QAS system, the ABAP Agent needs an initial snapshot of the system. A Build Map is a snapshot of the standard and custom code objects (and their related objects) in a Pipeline's QAS system, based on usage data from the Pipeline's Production system.

The ABAP Agent automatically excludes SAP Basis objects (delivery units `SAP_BASIS` and `SAP_UI`) from a Build Map. To customize which components are excluded, use the `[componentstoignore]` section in `config.toml`. See [Configuration settings](https://github.com/Sealights/gitbook.setupandconfiguration/blob/master/sealights-agents-and-plugins/abap-agent-1.5/configuration-settings.md).

{% hint style="info" %}
**TODO (from v1.5 draft):** Confirm the link target for "Configuration settings" once that page exists in the v1.5 section.
{% endhint %}

## Create an Initial Build Map

The `buildmap run` command lets you create an Initial Build Map for your Pipeline. It uses a scheduled task named `INIT_BUILD_MAP`. The task runs once only, after a delay of two minutes, to create the Initial Build Map.

{% 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                                      |
| ------------ | -------- | ------------------------------------------------ |
| `--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 "HH_SLABAPCLI_170625"
```

{% endcode %}
{% endtab %}

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

```powershell
.\slabapcli.exe buildmap run --pipeline 'HH_SLABAPCLI_170625'
```

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

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

```log
.\slabapcli.exe buildmap run --pipeline 'HH_SLABAPCLI_170625'
[2025-06-17 15:28:19.807+01:00] [info] Current ANSI Code Page: 65001 (UTF-8) (65001)
[2025-06-17 15:28:19.807+01:00] [info] Config pathname: ../config/config.toml
```

{% endcode %}

{% hint style="info" %}
You can bypass the Task Scheduler and create an Initial Build Map directly from the command line. Run `watcher.exe INIT_BUILD_MAP --pipeline <pipeline-name>` from the ABAP Agent's `bin` directory.
{% endhint %}


---

# 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-1.5/command-line-reference/build-maps.md?ask=<question>&goal=<endgoal>
```

`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.