C_FIORD_2502 Questions and Answers

Deployment Targetsfor SAPUI5 apps from BAS include:

SAP BTP(via HTML5 App Repository or MTA).

SAPUI5 ABAP Repositoryon an on-premise or S/4HANA backend system.

SAP Deployment Guide:

“Deployment to ABAP repository or HTML5 App Repository on SAP BTP is supported. SAPUI5 Java repo is deprecated.”

Fiori Launchpad is not a deployment target but a UI layer.

Tile visibility in Fiori Launchpad depends on:

Target Mappingsbeing defined.

The tile being part of aGroupassigned to the user.

OData service authorizationsbeing present (no access = no launch).

SAP Fiori Launchpad Troubleshooting Guide:

“Missing target mapping, group, or backend authorization will prevent tile visibility even if the catalog is assigned.”

PFCG and catalog issues alone won't prevent the App Finder from showing all apps.

On theObject Page Header:

title.valuedisplays actual value of field Sales order Number.

description.valueshowsSales Order Ownertext.

SAP CDS Annotations Guide:

“In object pages, headerInfo.title.value and description.value are displayed prominently in the page header.”

TypeName/Plural are used for page titles and breadcrumbs.

Dynamic Tiles:

UseOData servicesto fetch real-time values (e.g., counts, statuses).

Properties liketitle, info, icon, and numbercan be dynamically set.

SAP Fiori Admin Guide:

“Dynamic tiles fetch content using OData or Web Services.”

Static tiles have fixed text. Semi-dynamic tiles are not part of standard Fiori design.

SAPUI5 supports three maindata binding modes:

One-way: Data flows from model to view.

Two-way: Data syncs both directions (used in forms).

One-time: Data is injected once and not updated.

SAPUI5 Developer Guide:

“Binding modes define how data is synchronized between the model and the view. The supported modes are: OneWay, TwoWay, OneTime.”

Three-way and resource-model binding are invalid or unrelated to binding modes.

Generic actionsin SAP Fiori elements include:

Create: enabled by entity-level metadata (CreateAllowed).

Navigation: defined via semantic object and annotation metadata.

SAP Fiori Elements Functional Scope:

“Out-of-the-box actions include Create, Delete, and Navigation depending on metadata. Approve is domain-specific.”

Approve is custom logic and must be implemented manually.

Given the hierarchical structure, where regions is an array, and companies is a sub-array under region[0], correct access is:

/regions/0/companies: path to company list in first region (Americas).

name and city are properties of each company.

SAPUI5 Model Binding Guide:

“To bind list data in nested arrays, use full path access like /parent/0/child.”

Extension points allow app developers to inject custom UI or logic into standard apps:

Custom column: Add additional columns to tables.

Custom section: Extend the Object Page with new sections.

Tiles are linked viaTarget Mappings, which define:

Semantic object + Actioncombination.

This routing determines what app or view is launched.

SAP Fiori Launchpad Configuration Guide:

“Target mappings define navigation logic using semantic object/action. Tiles use these to determine routing targets.”

Semantic object alone is not actionable.

To add afilter field, use:

UI.SelectionFieldannotation in the CDS view.

Fact Sheet appsare designed to be launched viaEnterprise Searchin the Fiori Launchpad:

Tied to asemantic objectand accessed from search results.

Show detailed object data in a drill-down format.

SAP Fiori App Types Guide:

“Fact Sheet apps are integrated into the Enterprise Search and typically launched from search results, not from tiles.”

Transactional and analytical apps are primarily accessed via tiles or navigation.

In OData:

POSTis used tocreatenew entities.

PUTandPATCHare used to update existing entities.

CHANGE and UPDATE are invalid HTTP methods.

SAP OData V2/V4 Protocol Guide:

“To create a new entity, a POST request is issued to the entity set URL with the new entity’s payload.”

In ahub deployment:

UI5 app code (HTML/CSS/JS) is deployed onSAP Front-End Server (FES).

Business logic (OData services) remains onBack-End Server (BES).

SAP Fiori Deployment Guide:

“FES hosts the UI components and handles UI5 resource loading. BES contains the application data logic.”

Web Dispatcher only routes traffic. XS Engine is for HANA-native apps.