ABAP add-on
What the browser cannot see, the ABAP system knows: which PFCG roles a user has, which catalog would bring a tile and which start authorization is missing. The optional add-on /CDNA/FIORITAILOR answers exactly that – read only, with the user’s session.
- Edition
- from Enterprise
- Package
/CDNA/FIORITAILOR(abapGit)- Service
- OData V4, RAP, read only
- Systems
- S/4HANA on-premise and Private Cloud
- Status
- not yet tested on a real system
What the add-on is for
Without the add-on FrontTailor works as usual. With it you also get:
- the Roles tab: roles, catalogs, groups, spaces and reachable intents of your own user or – with authorization – another user (Roles and authorizations);
- the complete check chain “Why don’t I see this tile?” with the stages role and start authorization, field by field as in SU53;
- the actual ICF timeout of the session in health instead of an estimate (Health and morning check).
The service only reads; it creates and changes nothing. That is why it is allowed on PROD systems too.
Install
- Pull the package
/CDNA/FIORITAILORwith abapGit from thebackend/abap/folder of the FrontTailor repository. - Publish the service group
/CDNA/FIORITAILOR_O4in/IWFND/V4_ADMIN. Default path:/sap/opu/odata4/cdna/fioritailor_o4/srvd/cdna/fioritailor/0001/. - Assign the roles (see below).
- In FrontTailor, switch on Use backend service for this SAP host in the Roles tab. The state should change to Available.
The detailed guide with transport and SICF is in backend/abap/README.md. If an object fails on import (especially the service binding, the authorization object or the application log object), you can create it by hand in ADT, SU21 or SLG0.
Roles and log
| Role | Content | For whom |
|---|---|---|
/CDNA/FT_USER | Start authorization S_START for R3TR G4BA /CDNA/FIORITAILOR_O4 | all users of the “Roles” tab |
/CDNA/FT_SIM | Authorization object /CDNA/SIM, ACTVT 03 | everyone allowed to check other users |
Every check of another user is written to the application log SLG1 (object /CDNA/FT, subobject SIMULATION) before the check – with caller, action and checked user. If the log cannot be saved, the check is refused. The panel warns before sending and shows the log number afterwards.
What goes over the wire
- FrontTailor calls the service only after you have switched on Use backend service for the host. Before that, not a single request goes to the service.
- The call always goes to the host of the launchpad tab, with your existing browser session. A different path can be entered, a different host cannot.
- Only the switch (and a different path) is stored, locally in the browser – no answers, users, tokens or cookies. The CSRF token lives in memory only.
- With the policy
modules.backend: falsethe tab disappears, and the check chain and health no longer ask the backend (Enterprise deployment).
States in the “Roles” tab
| State | Meaning |
|---|---|
| Off | The switch is off; FrontTailor works without the backend. |
| Available | The backend service answers. |
| Not installed | HTTP 404: the add-on is not installed, or its SICF node is inactive. |
| Not logged on | No SAP session in this browser – log on in the tab and check again. |
| No authorization | The user lacks the role /CDNA/FT_USER. |
| No host access | The site is not granted in FrontTailor (grant). |
| Incompatible | Unknown contract version – update the add-on or the extension. |
| Error | The service failed; details in /IWFND/ERROR_LOG. |
See also
- Help from people ABAP backend add-on for FrontTailor Enterprise
- Docs Roles and authorizations
- Docs Health and morning check
- Docs Enterprise deployment
- Sources ADR-0321