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 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. Ensure QAS collects SCMON context data — Configure your QAS systems to collect SCMON data.
How Fiori names appear in SeaLights
SeaLights does not use one label style for every Fiori-related context:
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.
Required for Fiori: Import FLPCA after setup is in place and before you run search_testrepo. Upload is per RFC (upload_flpca import --rfc <rfc> --file <path>). 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.
Fiori validation path
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. Repeat for each RFC that needs launchpad enrichment.
Confirm import with upload_flpca status for that RFC before continuing.
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. Ongoing commands: Search Test Repositories.
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 (process specific transports). Confirm SeaLights shows the expected modifications before opening a cycle.
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 and the linked product docs there (recommendations, gaps, Multi App Coverage Report).
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.
Troubleshooting
No application / build in SeaLights after the initial build map
Check server and watcher logs. Verify RFC connectivity with slabapcli rfc test --name <rfc>.
setup status fails
Fix SeaLights token, RFC destinations, SAP authorizations, and SCMON before starting the server. See Validate Your Setup.
search_testrepo finds nothing
Confirm every testrepo set for the pipeline is done. If you just changed config, verify it reloaded — see Configuration Settings. Check adapter logs under 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 ("<SID> <ashost>"). 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.
For deeper diagnosis, see Troubleshooting the ABAP Agent.
Related reading
Last updated
Was this helpful?