C_FIORD_2502 Sample Questions Answers

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

Thesap.m.FacetFiltercontrol fires:

confirm: when filters are applied.

reset: when the user clears filters.

SAPUI5 API Reference - FacetFilter:“Events include 'confirm', 'reset', triggered by user interactions.”

listFilter/oninit are not defined FacetFilter events.

Groupsare optional in SAP Fiori 3 and newer versions:

Used tovisually organize tiles.

Tiles/apps can still be accessed via theApp Finderif the catalog is assigned.

SAP Fiori Launchpad Admin Guide:

“Groups are optional. Users can use App Finder to launch apps directly from catalogs.”

Other steps like creating catalogs and target mappings are essential for app accessibility.

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.

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.

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

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.

Flexible Column Layout is a feature that supports responsive design. Configuration can be done via:

manifest.jsonunder the sap.ui5/routing/config section.

Analytical List Page (ALP)includes:

Visual filters(compact KPI tiles with charts).

Interactive charts.

Visual tablesfor detailed drill-down.

SAP ALP Template Guide:

“ALP combines chart-based filtering with data tables and visual filters for analytic display.”

Standard form sections are not typical components in ALP.

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.

ODataModelis the only model that:

Supportsdeep inserts, i.e., inserting parent and child entities in one request.

Utilizesnavigation propertiesand the $expand functionality.

SAP Gateway Developer Guide:

“A deep insert involves a POST request with a nested payload… supported only by the OData model.”

XML/JSON/Resource models are static and client-only, without support for backend communication or nested entity posting.

SAP Fiori elements provide:

Design compliancewith SAP Fiori UX guidelines.

Reduced costby minimizing custom code.

Hook methodsare custom logic injection points:

Add conditionals (if (this.extHookFunction) this.extHookFunction();)

Identify extension points in the controller

Provide a placeholder for custom logic, typically in a utility/helper file.

SAP Extension Practices:

“To use hook methods, define optional logic spots and allow override in custom layer.”

Modifying bootstrap is unrelated. Function names do not need special reservations—convention suffices.

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.

Thei18n.propertiesfile holds thetranslation keys and valuesfor different languages. Demonstrating localization involves:

Showing these files with translations like i18n_fr.properties or i18n_de.properties.

SAPUI5 dynamically picks the language based on browser settings.

SAPUI5 Localization Guide:

“Translation values are maintained in i18n.properties files. The framework selects the appropriate version based on the user’s language preference.”

The other choices (e.g., preview frame or project.json) don’t expose actual translation content.