> 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/guides/fiori-support.md).

# Fiori support

Fiori and OData with ABAP Agent 2.0 — how names appear in SeaLights, mandatory FLPCA import before search\_testrepo, and the path from search to Test Cycle recommendations.

Use this guide after you finish [Setup and installation](broken://pages/jvmOWRjO10SvuLg7G51U) through RFC, pipeline, test repositories, `setup status`, and the initial build map. It focuses on **Fiori-specific** steps: FLPCA import, repository search, transports, and Test Cycles.

For how `WAPA`, `IWSV`, and other object types relate to SCMON coverage and business context, start with [SAP objects support](broken://pages/W91lfYHxi5z8fYg7EK6F). Ensure QAS collects SCMON context data — [Configure your QAS systems to collect SCMON data](broken://pages/V9DzcqIlJYSD11AE8G20).

## How Fiori names appear in SeaLights

SeaLights does not use one label style for every Fiori-related context:

| Fiori style                                      | How it appears in SeaLights                                                                                            |
| ------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------- |
| **Classic Fiori** (transaction-backed apps)      | Under the **executable / business context** — for example the GUI transaction code (`VA01`), not the FLPCA tile title. |
| **WAPA / IWSV** (UI5 apps and OData V2 services) | Under the **technical Fiori app name** — the `WAPA` or `IWSV` identity from SCMON context data.                        |

FLPCA does not replace those UI identities. It enriches what the agent can match when it searches your test repositories (see below).

## FLPCA and Fiori test recommendations

**FLPCA** is the Fiori Launchpad Content Administrator export (`/UI2/FLPCA`). After you import it for a pipeline's PRD RFC, the agent stores launchpad **titles and keywords** alongside that RFC’s data.

When `search_testrepo` runs, the agent uses that catalog to expand search terms for Fiori-driven processes — especially where classic transactions map to launchpad apps. Better matches in the test repository feed **Test Recommendations** later: transports that touch Fiori-backed code are linked to tests whose names or metadata align with those expanded terms.

Command reference: [Upload FLPCA data](broken://pages/OVyJn64Uei6IIYc502CN).

{% hint style="warning" %}
**Required for Fiori:** Import FLPCA **after** setup is in place and **before** you run `search_testrepo`. Upload an Excel export (`.xlsx`) for each pipeline's **PRD RFC** (`upload_flpca import --rfc <prd-rfc> --file <path>`); search does not read FLPCA data imported for QAS or other RFCs. The import command waits for the import to finish and exits with a non-zero code if it fails; confirm each import with `upload_flpca status` before scheduling or running search. Without FLPCA, Fiori-related repository search often finds few or no useful tests.
{% endhint %}

## Fiori validation path

{% stepper %}
{% step %}

### Upload FLPCA data (PRD RFC)

Export `/UI2/FLPCA` to an Excel workbook (`.xlsx`) from your production system, then import it on the agent host against the pipeline's PRD RFC.

Follow [Upload FLPCA data](broken://pages/OVyJn64Uei6IIYc502CN). Repeat for the PRD RFC of each pipeline that needs launchpad enrichment.

Confirm import with `upload_flpca status` for that RFC before continuing.
{% endstep %}

{% step %}

### Search test repositories

Run the Part 1 smoke check for `search_testrepo` — schedule search, wait for a run, and confirm matches for Fiori-related terms you expect (including FLPCA-expanded titles where classic transactions map to launchpad apps).

Steps and pass criteria: [Setup and installation — Smoke-test `search_testrepo`](broken://pages/jvmOWRjO10SvuLg7G51U). Ongoing commands: [Search Test Repositories](broken://pages/3dzoIdoAGQw91N8Jpn6t).
{% endstep %}

{% step %}

### Import transports that impact Fiori

Process transports that change Fiori/OData-backed code or related contexts so the agent records **build modifications**.

Use the watcher flow in [Show the value with Test Cycles](broken://pages/EXMBmOkLCBbhPiWjM2ki) (process specific transports). Confirm SeaLights shows the expected modifications before opening a cycle.
{% endstep %}

{% step %}

### Generate a Test Cycle for your test stage

In SeaLights, create a Test Cycle for your application, environment, stage, and transport scope — same hub as Part 2: **Test Optimization → Test Recommendations**.

Wizard and outputs: [Show the value with Test Cycles](broken://pages/EXMBmOkLCBbhPiWjM2ki) and the linked product docs there (recommendations, gaps, Multi App Coverage Report).
{% endstep %}

{% step %}

### Confirm Fiori-related tests in recommendations

Review **Test Recommendations** for the cycle. You should see tests tied to Fiori-driven impact: classic contexts under their transaction-style executable (for example `VA01`), and `WAPA` / `IWSV` contexts under their technical app names.

If recommendations look thin, verify SCMON context data, FLPCA import for the pipeline's PRD RFC, and that `search_testrepo` already found tests for the Fiori terms you care about.
{% endstep %}
{% endstepper %}

## Troubleshooting

## Related reading

* [SAP objects support](broken://pages/W91lfYHxi5z8fYg7EK6F)
* [Upload FLPCA data](broken://pages/OVyJn64Uei6IIYc502CN)
* [Setup and installation](broken://pages/jvmOWRjO10SvuLg7G51U)
* [Show the value with Test Cycles](broken://pages/EXMBmOkLCBbhPiWjM2ki)
* [Search Test Repositories](broken://pages/3dzoIdoAGQw91N8Jpn6t)
* [Test Tool Integrations](broken://pages/X3jEQR7gju1fIaT7v4vC)