SAP UI5 Interview Questions and Answers with Explanations

SAP UI5 FAQ's

Ques 1.What is SAPUI5?

Ans.-SAPUI5 is also one client-side rendering library just like any other HTML5. 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.

Ques 2. Why SAPUI5 instead of HTML5?

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

Ques 3. What is the main difference between HTML5 and SAP UI5?

Ans.- HTML5 is a markup language and it doesn’t have programming capabilities but SAP UI5 is a framework which is based on MVC approach to build 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.

Ques 4. 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 form of object, View defines the UI and Controller contains all the logic to drive as well connects view with model.

Ans.- SAPUI5 uses two mechanism for navigation in applications those are EventBus and Routing where latter supersedes since SAPUI5 1.16. sap.ui.core.routing is the class used for the routing.

We define routing in components metadata in “routing” key. It is composed of route object and hash changer object. Route object defines the navigation paths and hash changer will be used at runtime to change the hash which leads to navigation.

Ques 9. What is Responsive Web Design?

Ans.- A web application which gives the same look and feel to the user in desktops and mobile devices.

Ques 10. What is Component in SAP UI5?

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

Ques 11. What are the types of Components?

Ans.-

There are two types of components:

Faceless components: Mainly without UIs, Used for business logic and helper methods e.g. Formatters.

UI Component: typically component.js file which is made by extending sap.ui.core.UIComponent class.

Ques 12. When and How to use formatter 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:

1. JSON Model – Client-side model, supports two way binding.2. XML Model – Client-side model and intended for small data sets this is very rarely used model.3. Resource Model – This is also client side model used to maintain resource bundles, specially texts.4. ODATA Model – This is most important model of the four provided. This is server side model, supports two way binding ODATA model currently supports ODATA version 2.0.

Ques 14. What all types of views are available in SAPUI5?

Ans.-

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

1. JSON view2. XML View3. JavaScript View(JS View)4. HTML View

Ques 15. What are the Lifecycle/hook methods of SAPUI5 views controller?

Ans.- There 4 four Lifecycle methods available in every SAPUI5 views controller. These are onInit(), onExit(), onAfterRendering(), onBeforeRendering(). 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; onAfterRendering when the view has been rendered and, therefore, its HTML is part of the document; onBeforeRendering is called before the controller view is re-rendered and not before the first rendering.

Ques 16. Can we add our own controls to UI5?

Ans.- Yes, we can add custom controls by creating definition of it from scratch. To define a custom control we use sap.ui.control.extend and to enhance a standard SAP UI5 control we use sap.ui.commons.controlname.extend.

Ques 17. 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.

Ques 18. What are SAPUI5 Fragments?

Ans.- Fragments are very light weight UI controls and part of another UI. Fragments are not completely like views but they act like a view. Fragments are defined similar like views and are names like “myFragment.fragment.xml“.

Ques 19. Does Fragment have its own controller?

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

Ques 20. 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.

Ques 21. What is SAPUI5 Bootstrapping?

Ans.- SAPUI5 Bootstrapping is loading and initializing SAPUI5 in any HTML page. The very 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.

Ques 22. What is Metadata Annotations?

Ans.- The service metadata document explains 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.

Ques 23. What are the 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:NavigationProperty

-edm:AssociationSet

Ques 24. What is SAP Fiori?

Ans.- SAPUI5 is client side HTML5 rendering framework or library and SAP FIORI is collection of and released as waves of applications which are completely based on SAPUI5 framework. It means we can create applications using SAPUI5 framework and SAP FIORI is final product i.e. application.

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

Ques 27. What is FIORI Launchpad and Explain it?

Ans.- As we know there are more than 500 FIORI applications, SAP has provided a Shell or single point place from where we can access the all the applications. This serves as a home page for all the FIORI applications provided to. This shows tile based UI where every UI redirects to assigned FIORI application. This Launchpad is fully customizable according to your needs like theming and all.

Ques 28. How to know that device is Touch Screen or not?

Ans.- SAPUI5 library provides a special API “sap.ui.Device“ which can be used to for device and its feature detection. This API has a flag “sap.ui.Device.touch” which returns true if device is a touch screen otherwise false.

Ques 29. How to know the web browser of the client on which SAP Fiori application is running using SAP UI5?

Ans.- SAP UI5 library provides a special API “sap.ui.Device“ which can be used to for 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.