> 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/guides/fiori-support.md). # Fiori support Use this guide after you finish [Setup and installation](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/guides/setup-and-installation.md) 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](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/concepts/sap-objects-support.md). Ensure QAS collects SCMON context data — [Configure your QAS systems to collect SCMON data](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/install-the-abap-agent/configure-your-qas-systems-to-collect-scmon-data.md). ## 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 per 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](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface/upload-flpca-data.md). {% hint style="warning" %} **Required for Fiori:** Import FLPCA **after** setup is in place and **before** you run `search_testrepo`. Upload is **per RFC** (`upload_flpca import --rfc --file `). 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 (per RFC) Export FLPCA from your landscape for each RFC destination you use, then import on the agent host. Follow [Upload FLPCA data](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface/upload-flpca-data.md). Repeat for each RFC 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`](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/guides/setup-and-installation.md). Ongoing commands: [Search Test Repositories](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface/search-test-repositories.md). {% 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](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/guides/show-the-value-with-test-cycles.md) (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](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/guides/show-the-value-with-test-cycles.md) 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 relevant RFC, and that `search_testrepo` already found tests for the Fiori terms you care about. {% endstep %} {% endstepper %} ## Troubleshooting | Problem | What to check | | --------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | No application / build in SeaLights after the initial build map | Check server and watcher logs. Verify RFC connectivity with `slabapcli rfc test --name `. | | `setup status` fails | Fix SeaLights token, RFC destinations, SAP authorizations, and SCMON before starting the server. See [Validate Your Setup](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface/validate-your-setup.md). | | `search_testrepo` finds nothing | Confirm every `testrepo set` for the pipeline is done. If you just changed config, verify it reloaded — see [Configuration Settings](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/configuration-settings.md). Check adapter logs under [Log locations](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/configuration-settings.md#log-locations). For Fiori, confirm FLPCA was imported. | | No coverage / Test Gaps do not move after a test | Confirm Footprints is running (`footprints run`). For Tosca, set **SeaLightsLabId** to the auto-derived pipeline lab ID — leave `--labid` unset on `pipeline set`. Wait for SeaLights to process Footprints. | | Test Cycles look wrong or empty | Overriding `--labid` casually breaks Test Cycles. Leave it unset so the lab ID matches the QAS branch name (`" "`). Use `pipeline list` to confirm. | | TIA does not skip / optimize tests (Tosca Cloud) | Confirm a Build Modification exists for the transport, Footprints are collecting, and SeaLights optimization is enabled on the playlist. See [Run a test in Tosca Cloud](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/test-tool-integrations/tosca-cloud/run-a-test-in-tosca-cloud.md). | For deeper diagnosis, see [Troubleshooting the ABAP Agent](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/troubleshooting-the-abap-agent.md). ## Related reading * [SAP objects support](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/concepts/sap-objects-support.md) * [Upload FLPCA data](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface/upload-flpca-data.md) * [Setup and installation](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/guides/setup-and-installation.md) * [Show the value with Test Cycles](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/guides/show-the-value-with-test-cycles.md) * [Search Test Repositories](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface/search-test-repositories.md) * [Test Tool Integrations](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/test-tool-integrations.md) --- # 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/guides/fiori-support.md?ask=&goal= ``` `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.