Upload FLPCA data

Import Fiori Launchpad (FLPCA) catalog data per RFC. Required for Fiori before search_testrepo; optional enrichment for non-Fiori landscapes.

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

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.

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

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.

Command Prompt

Syntax

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

PowerShell

Syntax

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

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

Command Prompt

Command

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

PowerShell

Command

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

Expected output (PowerShell)

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

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.

---

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.

Command Prompt

Syntax

slabapcli.exe upload_flpca status --rfc <rfc>

PowerShell

Syntax

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

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

Example

Command Prompt

Command

slabapcli.exe upload_flpca status --rfc "S21"

PowerShell

Command

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

Expected output (PowerShell) — successful import

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

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.