> 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/upload-flpca-data.md).

# Upload FLPCA data

FLPCA is the Fiori Launchpad Content Administrator export (`/UI2/FLPCA`). Importing FLPCA data enriches test-repository matching by adding launchpad **titles and keywords** to business contexts.

The import is dispatched as a server task and the results are stored in a per-RFC SQLite database under `%ProgramData%`.

{% hint style="warning" %}
**When to run it:** Import FLPCA data **after** RFC, pipeline, and test-repository configuration is in place.

**Fiori (required):** For Fiori applications, FLPCA import is **mandatory**. Complete per-RFC import (`upload_flpca import` → confirm with `upload_flpca status`) **before** you run `search_testrepo`. See [Fiori support](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/guides/fiori-support.md).

**Non-Fiori (optional):** If you do not rely on Fiori-driven processes, FLPCA import is optional enrichment for test-repository matching.
{% endhint %}

## Import FLPCA data

### `slabapcli upload_flpca import`

Imports a FLPCA data file for an RFC Destination. The import runs as a server task. Use `upload_flpca status` to monitor the result after the command returns.

The imported data is written to:

```
%ProgramData%\Tricentis\SeaLights\ABAP Agent\private\flpca\{rfc-name-lowercase}.db
```

For example, for RFC Destination `S21`, the database is written to `private\flpca\s21.db`.

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

```batch
slabapcli.exe upload_flpca import --rfc <rfc> --file <path>
```

{% endcode %}
{% endtab %}

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

```powershell
.\slabapcli.exe upload_flpca import --rfc <rfc> --file <path>
```

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

| Parameter | Short flag | Required | Description                                                                                |
| --------- | ---------- | -------- | ------------------------------------------------------------------------------------------ |
| `--rfc`   | —          | Yes      | The RFC Destination name (must match a `[[rfc]].name` value in `config.toml`, e.g. `S21`). |
| `--file`  | —          | Yes      | Full path to the FLPCA data file on the agent host. The file must exist.                   |

#### Example

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

```batch
slabapcli.exe upload_flpca import --rfc "S21" --file "C:\data\flpca_s21_export.bin"
```

{% endcode %}
{% endtab %}

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

```powershell
.\slabapcli.exe upload_flpca import --rfc 'S21' --file 'C:\data\flpca_s21_export.bin'
```

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

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

```log
.\slabapcli.exe upload_flpca import --rfc 'S21' --file 'C:\data\flpca_s21_export.bin'
[2026-03-08 11:10:00.123+02:00] [info] Config pathname: C:\ProgramData\Tricentis\SeaLights\ABAP Agent\config\config.toml
```

{% endcode %}

{% hint style="info" %}
The command returns quickly after submitting the import task. The actual import runs asynchronously on the server. Use `upload_flpca status --rfc S21` to check the outcome.
{% endhint %}

***

## Check import status

### `slabapcli upload_flpca status`

Shows the result of the last `upload_flpca import` run for an RFC Destination. Reports the process state, upload state, and any server error messages.

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

```batch
slabapcli.exe upload_flpca status --rfc <rfc>
```

{% endcode %}
{% endtab %}

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

```powershell
.\slabapcli.exe upload_flpca status --rfc <rfc>
```

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

| Parameter | Short flag | Required | Description                                                          |
| --------- | ---------- | -------- | -------------------------------------------------------------------- |
| `--rfc`   | —          | Yes      | The RFC Destination name whose last import result you want to check. |

#### Example

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

```batch
slabapcli.exe upload_flpca status --rfc "S21"
```

{% endcode %}
{% endtab %}

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

```powershell
.\slabapcli.exe upload_flpca status --rfc 'S21'
```

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

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

```log
.\slabapcli.exe upload_flpca status --rfc 'S21'
[2026-03-08 11:12:00.456+02:00] [info] Config pathname: C:\ProgramData\Tricentis\SeaLights\ABAP Agent\config\config.toml
Process 'proc-def456' status: Done, upload status: Done
```

{% endcode %}

The status output reports:

| Field          | Values                     | Meaning                                                        |
| -------------- | -------------------------- | -------------------------------------------------------------- |
| Process status | `Running`, `Done`, `Error` | Current state of the server-side import task.                  |
| Upload status  | `Pending`, `Done`, `Error` | Whether the FLPCA data was uploaded to the SeaLights platform. |

If no import has been run yet, the command prints: `No import has been run for RFC 'S21' - run 'upload_flpca import' first.`


---

# 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/command-line-interface/upload-flpca-data.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.