Launchpad is navigation and authorisation, not a theme
Tile → intent → target mapping → UI5. Catalog on the PFCG role; spaces only arrange.
Read →Istanbul · independent delivery
SAP Blog
Most searches are ‘Fiori is missing’, ‘failed to load catalogs’, ‘empty My Inbox’, ‘CAP or RAP’. One intent per page. Product names stay in English.
Launchpad
Spaces replace groups; the catalog remains the authorisation source
/UI2/FLPCM_CUST for content, PFCG for the role. Space assignment without catalog is empty App Finder.
Read →Failed to load catalogs is a service and cache chain
PAGE_BUILDER_PERS, S_SERVICE, /UI2/DELETE_CACHE_AFTER_IMP, reverse-proxy %2F, post-copy alias.
Read →Could not open app is five checks, not one dump
ICF node, OData activation, target mapping, semantic object, role. Istanbul AMS runbook.
Read →Horizon is a theme, not a new Launchpad
Belize/Quartz delta, brand CSS, accessibility. Theme last, catalog first.
Read →No tile on the home page is not ‘no app’
Catalog right vs space layout. Train users on Finder before opening tickets.
Read →Keep tiles in FLPCM_CUST, not in Excel
Catalog, space, page, derived content. /UI2/FLC is the check, not the editor.
Read →Embedded frontend is the same box; hub is another SID
System alias, RFC, post-copy break. Write the topology in discovery.
Read →Fiori ID, OData, catalog and ICF are the fit-gap row
Standard app selection before Z. Istanbul consulting starts in the library.
Read →The tile knows the target from the mapping, not from hope
Semantic object, action, SAPUI5 component. Catalog break shows as Could not open app.
Read →Row-to-object navigation is an intent contract
Parameters, mapping, Could not open app. Write the semantic object in the process design.
Read →Authorisations
The catalog is the right to run; group and space only layout
PFCG assignment, /UI2/FLPCM_CUST, App Finder. Group-only assignment is the usual go-live defect.
Read →A business catalog on the role is the Fiori right
Space assignment, S_SERVICE, test user. SoD note in the Istanbul role workshop.
Read →A green tile with a dead service is a lie
ICF, system alias, S_SERVICE. Activate before the first user test.
Read →SU53 is the wrong first trace for Fiori
S_SERVICE, catalog, backend object. STAUTHTRACE is the Fiori auth proof.
Read →Elements
Elements is metadata UI, not a Z-UI5 copy
List Report, Object Page, annotation, RAP/CDS. Freestyle only when the floorplan fails.
Read →The queue screen comes from annotation, not XML views
SelectionFields, LineItem, variant, export. RAP actions and authorisation cuts.
Read →The object page is the work screen of one record
Header, facet, draft, RAP action. In-app limits stay in discovery.
Read →OVP is empty when the analytical CDS is empty
Cards, KPI, navigation to List Report. Not a wallpaper of unused tiles.
Read →Choose Elements when the floorplan is enough
Upgrade cost, RAP, Studio vs freestyle kit. Record the decision in discovery.
Read →Adapt the standard app; do not copy it
In-app vs Adaptation Project, clean-core, Git. Copy is technical debt.
Read →Custom field and UI Adaptation before RAP
Key-user limit, released objects. First door on clean-core.
Read →Process UX
Do not open the tile before the inbox stack is up
/IWPGW/TASKPROCESSING v2, /IWPGW/BWF, PGW alias must not be _RFC, task filter.
Read →SBWP full and Inbox empty is a PGW/filter/auth chain
TASKPROCESSING v2, /IWPGW/BWF, alias not _RFC, task filter. Istanbul AMS runbook.
Read →Putting ME21N on a tile is not Fiori procurement
Reference Library fit-gap, role, space, My Inbox. Istanbul rollout.
Read →Hanging FB60 on a tile does not change the ledger
Vendor invoice, open items, Overview Page. Auth and Inbox in the same design.
Read →Support
Slow Fiori is UI5, OData, CDS or the network — pick one
First paint, trace, /IWFND/ERROR_LOG. Istanbul AMS splits the layer before Basis guesswork.
Read →Which cache to clear after a transport
UI2, browser, SMICM, Gateway. Old tiles after import are cache until proven otherwise.
Read →HTTPS is easy; %2F silently breaks catalogs
Termination, routing, catalog vs OData paths. Do not split the two.
Read →If the parent ICF node is down, a green child is worthless
UI2, UI5, OData. Could not open app 404 starts in SICF.
Read →Green service, wrong SID
LOCAL vs RFC, My Inbox PGW, _RFC trap. Post-copy checklist.
Read →The red screen’s real text is in ERROR_LOG
OData 500/403, alias, CDS, business rule. Match the browser request to the log.
Read →Incognito before Basis
Current Chrome/Edge, no IE. Addon and PWA ‘works on my machine’ split.
Read →After go-live the tile breaks; without a queue the investment dies
P1–P4, Launchpad, OData, Inbox. Independent team; no licences, no partner claim.
Read →RAP
RAP is the ABAP model for Fiori on S/4
CDS, behavior, draft, OData V4. Clean-core extension on released APIs.
Read →Managed is the default; unmanaged wraps released BAPIs
Additional save, Object Page. Record the choice in discovery.
Read →Draft is the unsaved Object Page, not a Z-table habit
Draft table, exclusive lock, when to enable. Istanbul RAP delivery.
Read →BDEF is the behaviour contract
Action, determination, validation, implementation. Same language as the Fiori screen.
Read →UI annotation builds the screen; XML views do not
Metadata extension, List Report, Object Page, value help.
Read →Publish V4 from RAP; do not mix V2 by accident
Service definition, binding, Elements V4 vs V2. Istanbul service note.
Read →An empty Fiori list is often DCL, not a CDS bug
PFCG, S_SERVICE, instance auth. HAR before rewriting the query.
Read →New Fiori work is RAP; do not open Z-BOPF
Stock BOPF move is a programme, not a weekend. Istanbul guide.
Read →Restricted ABAP, released API, RAP
On-stack S/4 vs BTP ABAP environment. Lock the language version in the project.
Read →Clean Core
Unreleased tables are not clean-core RAP
C1 contract, ATC. Istanbul consulting proves the API before the BDEF.
Read →Keep S/4 upgradeable
In-app, RAP developer extensibility, BTP side-by-side. Modification last.
Read →The process sits next to the core, not in a Z-include
CAP, destination, Cloud Connector. First slice is one tile.
Read →Key user, RAP, or BTP — pick in discovery
Try in-app first. RAP on released API. Side-by-side when the process leaves S/4.
Read →CAP
CAP is side-by-side Fiori, not RAP on S/4
CDS model, Node.js, XSUAA, destination. Write placement first.
Read →Do not confuse CAP CDS with ABAP CDS
Domain, projection, association, aspect. BTP data contract.
Read →Node.js is the default; Java needs a reason
Handlers, TypeScript, S/4 destination. One runtime per landscape.
Read →mta.yaml is where CAP lives on BTP
srv, approuter, XSUAA, destination, HDI. Read deploy logs before rewriting CDS.
Read →Mock auth is not production
Role collection, IAS trust, JWT chain. Istanbul CAP security note.
Read →Annotations in CAP CDS, tile on Work Zone
List Report, Object Page. Same floorplan discipline as RAP.
Read →CAP does not always need HANA Cloud
HDI vs SQLite vs S/4 remote. Do not copy the S/4 document into HANA.
Read →BTP
The destination is the name CAP and Fiori use toward S/4
Connectivity, Cloud Connector, OAuth, principal propagation.
Read →Without Cloud Connector, BTP does not reach on-prem S/4
Virtual host, Location ID, mapping. Tunnel troubleshooting.
Read →The subaccount is the box the landscape lives in
Directory, CF space, quota. Dev/test/prod as three boxes by default.
Read →Content federation vs S/4 Launchpad as primary shell
Tiles, identity, where the user starts the day. Istanbul choice note.
Read →iFlow, API Management and Event Mesh are not one box
Cloud Integration vs PI/PO. BTP integration map.
Read →The iFlow is the message path on BTP
Adapter, mapping, Groovy, exception subprocess. MPL is a separate queue.
Read →Async events are not synchronous Fiori OData
Enterprise event, queue, CAP messaging vs iFlow. Consume idempotently.
Read →A trial CAP is not a production landscape
Quota, IdP, Cloud Connector. We do not sell licences.
Read →Do not put the Fiori UI service on the internet
OData/REST proxy vs CPI iFlow. UI binding stays inside.
Read →Where Fiori and BTP identities are proved
Corporate IdP, IPS, principal propagation. User map in discovery.
Read →S/4
No tile means the activation chain, not the theme
OData, ICF, catalog, Spaces and Pages, role. Prove with a business user.
Read →Insight next to the document, not a BW project
Analytical CDS, KPI tile, OVP, ALP. Narrow filters.
Read →WebGUI is not a Fiori delivery
Apps library, custom T-code, RAP/CAP. Istanbul roadmap.
Read →Standard first, then contracted extension, then AMS
Wave gates are go/no-go. Istanbul consulting programme.
Read →