SAP UI5 Interview Questions

Are you planning to attend an interview for the SAP UI Developer role but are confused about how to crack that interview also what would be the most probable SAP UI5 Interview Questions that the interviewer may ask? Well, you have reached the right place. Tekslate has collected the most frequently asked SAP UI5 Interview Questions which are often asked in multiple interviews.

In this article, we will cover the following:

• SAP UI5 Interview Questions
• SAP UI5 FIORI Interview Questions

SAP UI5 Interview Questions

Q1) What is SAPUI5?

Ans: Just like any other HTML5 client-side rendering library, SAPUI5 is also one. SAPUI5 strictly follows RIA (Rich Internet Application) standards. It is based on JavaScript which provides a lightweight programming model for desktop as well as mobile applications.

Q2) Why SAPUI5?

Ans: As the HTML5 world is the new age front technology across all aspects of internet applications SAP was kind of trailing in this age because SAP was using age-old Web Dynpro for building SAP Web Applications which lacks rich and user-friendly UI. SAP identified this and came up with its own custom HTML5 library i.e. SAPUI5.

Q3) Explain the Navigation concept in SAPUI5?

Ans: SAPUI5 uses two mechanisms for navigation in applications that are EventBus and Routing where the latter supersedes since SAPUI5 1.16.sap.ui.core.routing is the class used for the routing. We define routing in components metadata in the “routing” key.

Q4) What is a Component?

Ans: Component or Component.js is the first point of our application or we can say that it serves as an index that encapsulates all our application details i.e. view names, routing details, main view, applications type(Fullscreen or SplitApp), application service configuration, etc.

Q5) What is the difference between HTML5 and SAPUI5?

Ans: HTML5 is a markup language, It doesn’t have programming capabilities but SAPUI5 is a framework that is based on the MVC approach to building web applications. HTML5 is mainly for the purpose of creating a simple webpage without formatting and logic but UI5 provides standard style and components to build rich UIs.

Q6) What is MVC?

Ans: MVC stands for model view controller; it’s an architecture to design UI based applications to achieve maximum reusability and extensibility of the application for future changes. Model is the representation of data in the form of the object, View defines the UI and the Controller contains all the logic to drive as well connects view with model.

Q7) When and How to use formatting in SAPUI5?

Ans: We need to use formatter when we need to perform some changes on the back end property data on the front end. we can use formatter while data binding to a property like as follows: oControl = new sap.ui.commons.TextField({ value : {path : “/path”, formatter : function(oEvent){ return “Value:”+oEvent; }}});

Q8) What all design patterns are recommended/available in SAPUI5?

Ans: SAP recommends following application design patterns keeping in mind the design consistency of the applications:

• Master-Detail
• Master-Master-Detail
• Fullscreen
• Fullscreen-Fullscreen-Master Detail (Multi Flow)

Q9) What types of views are available in SAPUI5?

Ans: There are following predefined three types of view available in SAPUI5:

• JSON view
• JavaScript View(JS View)
• HTML View

Q10) What is formatted in SAPUI5 and how to use it?

Ans: We need to use formatter when we need to perform some changes on the back-end property data on the front end. we can use formatter while data  binding to a property like as follows: oControl = new sap.ui.commons.TextField({ value : {path : “/path”, formatter : function(oEvent){ return “Value:”+oEvent; }}});

Q11) What all types of data models available in SAPUI5?

Ans: As SAPUI5 follows MVC(Model-View-Controller) there model plays a crucial role in the framework. SAPUI5 has the following predefined four data models available:

• JSON Model: Client-side model, supports two-way binding.
• XML Model: Client-side model intended for small data sets this is a very rarely used, model.
• Resource Model: This is also a client-side model used to maintain resource bundles, especially texts.
• OData Model: This is the most important model of the four provided. This is the server-side model, that supports two-way binding ODATA model currently supports OData version 2.0.

Q12) What are the Lifecycle methods of the SAPUI5 views controller?

Ans: There are four Lifecycle methods available in every SAPUI5 view controller.

These are

• onInit()
• onExit()
• on after rendering()
• on before rendering()
• onInit is called when a view is instantiated and its controls (if available) have already been created;
• onExit is called when the view is destroyed, used to free resources and finalize activities;
• on after rendering when the view has been rendered and therefore its HTML is part of the document;
• on before rendering is called before the controller view is re-rendered and not before the first rendering.

Q13) What is the main difference between OData Model and JSON Model?

Ans: The JSON model is a client-side model and, therefore, intended for small datasets, which are completely available on the client. The OData model is a server-side model: the dataset is only available on the server and the client only knows the currently visible rows and fields.

SAP UI5 FIORI Interview Questions

Q14) What are the SAPUI5 Fragments?

Ans: Fragments are very lightweight UI controls and part of another UI. Fragments are not completely like views but they act as a view. Fragments are defined similar to views and are names like “myFragment.fragment.xml“.

Q15) Does Fragment have its own controller?

Ans: Fragments are created without controllers, they don’t have their own controllers they share the controller of the view which is invoking it.

Q16) In how many ways you can bind data to your controls?

Ans: We can bind data to any controls using three methods, Property, Element, and Aggregation binding.

Q17) What is SAPUI5 Bootstrapping?

Ans: SAPUI5 Bootstrapping means loading and initializing SAPUI5 on any HTML page. The most important library or resource loaded in SAPUI5 bootstrap is “sap-UI-core.js”. Apart from this theme for the application, SAPUI5 libraries, etc are declared in the bootstrapping.

Q18) What are the Metadata Annotations?

Ans: The service metadata document describes the structure of all resources in the service. This structural metadata makes it easy to understand a service. We can explore service metadata at the address “$metadata” relative to the service root.

Q19) What are common Metadata Annotations?

Ans: Following are some of the service metadata annotations which are common and a front-end developer must know these in order to understand the service and integrate it:

EDM: EntityContainer

EDM: EntitySet

EDM: EntityType

EDM: Property

EDM: Nav Navigation Property

EDM: AssociationSet

Q20) What is the difference between SAP Fiori and SAPUI5?

Ans: SAP FIORI is a collection of standard applications based on the SAPUI5 library provided by SAP. SAP FIORI applications share some standard design guidelines and the way in which these applications are developed.

Q21) How many types of Fiori applications are there?

Ans: There are 3 types of Fiori applications:

• Transactional
• Analytical
• Fact Sheets

Q22) What is the difference between SAP Fiori and SAPUI5?

Ans: SAP FIORI is a collection of standard applications based on the SAPUI5 library provided by SAP. SAP FIORI applications share some standard design guidelines and the way in which these applications are developed.

Q23) What is FIORI Launchpad and Explain it?

Ans: It is a home page for all the FIORI applications provided. There is more than five hundred custom app provided by SAP. This shows a tile-based UI where every UI redirects to the assigned FIORI application. This Launchpad is fully customizable according to your needs like theming and all.

Q24) How can you get the web browser of the client on which the SAP Fiori application is running?

Ans: SAPUI5 library provides a special API “sap.ui.Device“which can be used for the device and its feature detection. This API provides flags like “chrome”, “firefox”, “Mozilla”, “edge” etc. in “sap. ui.Device.browser” API which returns boolean values. 

Q25) What are Fiori Design Principles?

Ans: There are 5 design principles we need to keep in mind while designing SAP Fiori applications.

• Role-Based
• Delightful
• Simple
• Responsive
• Coherent

Q26) What is SAP Fiori?

Ans: SAPUI5 is a client-side HTML5 rendering framework or library and SAP FIORI is a collection of and released as waves of applications that are completely based on the SAPUI5 framework. It means we can create applications using the SAPUI5 framework and SAP FIORI is the final product i.e. application. In SAPUI5 we have to code from scratch, but in Fiori Application the custom application is already built and enhancements can be done on those custom apps.