C_FIORD_2502 SAP Certified Associate - SAP Fiori Application Developer Questions and Answers

TheOverview Page (OVP)template uses cards to visualize key metrics, charts, and actionable insights. It's designed to aggregate and highlight information from multiple sources.

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.

ResponsiveFlowLayoutallows content towrap and flowaccording to screen size and available space:

Preferred for building responsive UI layoutswithout tables.

Supports multiple rows and automatic adjustment of elements.

SAPUI5 Layout Control Reference:

“ResponsiveFlowLayout arranges controls in rows, wrapping them depending on the available width.”

Grid layout is rigid, and Vertical/Horizontal layouts are not responsive.

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.”

Thecriticalityproperty in @UI.lineItem enablescolored status indicators:

Values are interpreted using SAP-defined criticality semantics:

1 = Negative (Red)

2 = Critical (Yellow)

3 = Positive (Green)

SAP Annotations Guide:

“Use criticality in lineItem annotations to enable status coloring for numeric codes representing status.”

Color is not a valid annotation. @UI.selectionField is unrelated to table columns.

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.

SAP Business Application Studio (BAS)provides:

Extensibility Pane: lists available extension points from the standard app.

Wizards: generate required files (e.g., controller extensions, views) automatically.

SAP BAS Guide:

“The Extensibility Pane visualizes available hooks… wizards create necessary files for view/controller/fragment replacement.”

Descriptor editor is used for manifest edits but doesn’t directly choose extension elements.

TheAnalytical List Page (ALP)is ideal for applications requiring:

Charts

Visual filters

The manifest.json supports variousextensibility namespaces:

sap.ui.viewModifications: replaces/changes view content.

sap.ui.controllerExtensions: injects custom logic.

SAP Fiori Extension Documentation:

“The manifest.json file defines UI and logic extensibility using namespaces like viewModifications and controllerExtensions.”

Options B/C are not valid manifest namespaces.

SAPUI5 supports differentbinding types:

Property binding: binds individual attributes (e.g., text="{/name}").

Aggregation binding: binds lists or tables (e.g., items="{/products}").

Element binding: binds a control and its children to a specific path (bindElement("/product")).

SAPUI5 Developer Guide:

“Supported binding types include Property, Aggregation, and Element binding.”

Structure/Combination are not valid SAPUI5 binding categories.

Text strings for localization reside in thei18n.propertiesfile:

Key-value format used across multiple languages.

SAPUI5 Documentation:“Translation texts are managed via i18n.properties and localized versions like i18n_de.properties.”

Other files do not hold textual content directly.

OData V4 offers:

Advanced analytical capabilities: including grouping and aggregation.

Improved data types: such as more precise decimal handling.

SAPUI5 supportslocalization via resource bundles:

.properties files (often mistakenly called .props) are used for language-specific translations.

One default file (i18n.properties) and additional ones like i18n_fr.properties.

These files containkey-valuepairs for translation.

SAPUI5 SDK:

“Internationalization is supported using resource bundles. Each bundle is a .properties file with keys and translations. You must provide separate files per language.”

Creating separate views/controllers per language is incorrect; views are static. HTML character encoding is optional and not specific to language support.

Responsive tables(sap.m.Table) in SAPUI5 use demandPopin, popinDisplay, and screen width qualifiers to optimize mobile display. Correct settings include:

maxScreenWidth="mobile"ensures pop-in on small devices.

demandPopin="true"triggers field reformatting into pop-ins.

popinDisplay="Inline"keeps visual alignment.

SAPUI5 SDK – Responsive Table Control:

“Use demandPopin with maxScreenWidth and popinDisplay to handle narrow screen layouts.”

Options with minScreenWidth do not apply to mobile-focused pop-in logic.

SAP offersmultiple extension mechanisms:

Adaptation Project: customizes standard apps without copying code.

View Extensions: via manifest.json to inject custom UI at extension points.

Controller Hooks and Property Overridesfor fine-grained control.

SAP Fiori Extensibility Guide:

“Adaptation projects allow for UI and logic customization using SAP Business Application Studio.”

Changing runtime libraries or merging data at runtime are neither recommended nor supported directly.