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

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.

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.

QUnitfollows theAAApattern:

Arrange: Prepare test data/setup.

Act: Perform the operation.

Assert: Validate the result.

SAP Testing Guidelines:

“The Arrange-Act-Assert (AAA) pattern is fundamental to unit testing logic with QUnit.”

B is the pattern for OPA5 (behavioral testing), not QUnit.

OPA5 (One Page Acceptance)testing framework is used for:

End-to-end integration testingof SAPUI5 apps.

Verifyingnavigation, routing, and view transitionsusing test cases written in Given-When-Then format.

SAPUI5 Testing Guide:

“OPA tests simulate full user interactions, including navigation, and validate that applications behave as expected.”

QUnit is for unit tests. Sinon is a mocking library. Mock server simulates backend but doesn’t test navigation logic.

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.

Fragmentsare XML/JS/HTML code snippets:

They arelightweight and reusable(dialogs, table columns, etc.).

Areloaded via module loader(sap.ui.require) and inserted into views.

SAPUI5 Fragments Documentation:

“Fragments are not self-contained views and do not have controllers. They are loaded by name using module loading.”

A/B are incorrect because fragments lack controller context and cannot act standalone.

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.

View Replacementis the most invasive extensibility technique used when extension points aren’t sufficient. It includes:

Building a completely newXML viewand mapping it via sap.ui.viewReplacements in the manifest.

Assessmentthat the available extension hooks (like controller or fragment replacements) don’t fulfill the requirement.

SAP Extensibility Guide:

“Use view replacement only if the application cannot be extended via extension points or controller hooks.”

Replacing individual controls (C, D) aligns more withcontrol replacement, not full view substitution.

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.

InPFCG, to authorize access to Fiori apps:

Assign thecatalogto theMenu tabof a role.

The user must be assigned the role.

SAP Authorization Guide:

“Fiori Catalogs must be added in the PFCG Menu tab to include corresponding apps in user authorization.”

Authorization tabs are used for backend authorizations, not app tiles.

SAP Fiori elements support rendering of:

Micro Chartsusing @UI.chart inside table columns.

Imageswith appropriate annotations or formatter logic.

Text, the default for most line item entries.Charts and nested tables are not rendered inside cells.

SAP Fiori Elements Developer Extensibility Guide:“Micro charts can be embedded in cells… Images and formatted text are supported.”

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.

TheODataModelsupports data binding to back-end OData services and includes fullserver-side capabilities:

Sorting,filtering,paging, andbatchingare natively processed by the server via query options ($orderby, $filter).

This offloads processing from the client and ensures efficient data handling.

SAPUI5 SDK - ODataModel (v2andv4):

“The ODataModel provides advanced features like server-side sorting and filtering using standard OData query options.”

In contrast, JSONModel, ResourceModel, and XMLModel are client-only and lack these features.

@UI.lineItem specifiestable columnsin a List Report.

position determines theorderof columns: ProductName, Status, Price.

CDS UI LineItem Documentation:

“The lineItem annotation defines columns for tabular display. position is used to sort fields in the UI.”

These are not form fields; they’re tabular entries.

SAPUI5 SDKprovides:

ExtensiveUI controls(charts, tables, lists, dialogs, etc.)

Internationalization (i18n)support for multi-language development.

SAPUI5 SDK Features Overview:

“SAPUI5 offers a responsive design across all devices and full translation support via resource bundles.”

Web Dynpro is unrelated; responsiveness is not limited to non-mobile devices.