Explore topic-wise InterviewSolutions in .

• By creating MULTIPLE filters and concatenating them either with AND or OR
• By creating a single sap.ui.model.Filter object and specifying a PATH, an OPERATOR, and up to TWO values

• POSITIVE
• NEGATIVE
• CRITICAL

They are REPRESENTATIONS of STATES such as SUCCESS, WARNING, and ERROR.

They are representations of states such as success, warning, and error.

• $SKIP
• $COUNT
• $EXPAND

Paging can be ACCOMPLISHED by USING $skip in COMBINATION with $top. The PARAMETERS’ VALUES describe the interval of the data that is requested.

Paging can be accomplished by using $skip in combination with $top. The parameters’ values describe the interval of the data that is requested.

Aggregation BINDING is used for list-like structures, WHEREAS element binding can be used to SET the binding context of any PARENT CONTROL.

Aggregation binding is used for list-like structures, whereas element binding can be used to set the binding context of any parent control.

When you WANT bindings of child controls to resolve their PATHS relative to the BINDING of the PARENT

When you want bindings of child controls to resolve their paths relative to the binding of the parent

Set the “visible” PROPERTY of the control to “true” or “FALSE”.

Set the “visible” property of the control to “true” or “false”.

As MANY as NEEDED

As many as needed

• Run your APP from SAP Web IDE and COPY its URL into a new browser TAB.
• In your app's manifest.json file, go to “services”, copy the URI, and use it to replace the file path in the URL from Step 1.
• Append “/$metadata” and press enter.

GROUP: TRUE

group: true

• sap.ui.model.type.Float
• sap.ui.model.type.DateTime
• sap.ui.model.type.Currency

• SET handleValidation to TRUE in the manifest.json FILE.
• REGISTER to the validationError EVENT on sap.ui.getCore().

• An ARRAY with the data in the JSONModel that you want to bind to the LIST
• A template list ITEM to be CLONED
• A bound list control

To BIND a SET of DATA ENTITIES to a list-like STRUCTURE

To bind a set of data entities to a list-like structure

'TINY', 'Small', 'Medium' or 'Large'

'Tiny', 'Small', 'Medium' or 'Large'

<BUTTON text="SAVE DRAFT" icon="sap-icon://save" />

<Button text="Save Draft" icon="sap-icon://save" />

Two-way

Two-way

JAVA SCRIPT OBJECT NOTATION

Java Script Object Notation

Manifest.json

Manifest.json

• sap.ui5
• sap.app
• sap.ui

• ROOT VIEW
• Supported device TYPES
• Supported themes

• ONINIT – an EVENT that is called when the VIEW and the controller are INSTANTIATED
• onExit – an event that is called when the view and the controller are destroyed

• To SEPARATE the UI and the processing logic
• To control the APPLICATION flow by HANDLING user events or UPDATING the view

• JAVASCRIPT VIEWS
• JSON views
• XML views

• ASSOCIATIONS
• PROPERTIES
• AGGREGATIONS

• D3.js for visualization
• ARIA for accessibility STANDARDS and KEYBOARD handling
• jQuery for managing DOM elements and ABSTRACTING browser differences

There are 5 DESIGN principles we need to keep in MIND while designing SAP Fiori applications.

1. ROLE Based
2. DELIGHTFUL
3. Simple
4. RESPONSIVE
5. Coherent

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

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

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

It is a home page for all the FIORI applications PROVIDED to. There are more than FIVE hundred custom app provided by SAP. 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.

It is a home page for all the FIORI applications provided to. There are more than five hundred custom app provided by SAP. 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.

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.

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.

There are 3 types of FIORI APPLICATIONS:

• TRANSACTIONAL
• Analytical
• FACT SHEETS

There are 3 types of fiori applications:

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

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

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

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:

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.

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.

FRAGMENTS are CREATED without controllers, they don’t have their own controllers they SHARE CONTROLLER of the view which is invoking it.

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

Fragments are very light weight UI controls. Fragments are not completely LIKE views but they act like a VIEW. Fragments are defined SIMILAR like views and are names like “Fragment.fragment.xml“.

Fragments are very light weight UI controls. Fragments are not completely like views but they act like a view. Fragments are defined similar like views and are names like “Fragment.fragment.xml“.

We can BIND DATA to any CONTROLS using three METHODS, Property, Element and Aggregation binding.

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

SAPUI5 Bootstrapping means loading and INITIALIZING SAPUI5 in any HTML page. THEMES and LIBRARIES are defined in this.

SAPUI5 Bootstrapping means loading and initializing SAPUI5 in any HTML page. Themes and Libraries are defined in this.

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.

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.

There are 4 lifecycle available in SAPUI5’s views controller, they are:

1. onInit() – it is called when a view is INSTANTIATED and its controls have already been created.
2. onExit() – it is called when the view is destroyed, used to FREE resources and finalize activities.
3. onAfterRendering() - when the view has been rendered and, THEREFORE, its HTML is part of the document.
4. onBeforeRendering() -It is called before the controller view is re-rendered and not before the first RENDERING. 

There are 4 lifecycle available in SAPUI5’s views controller, they are:

SAPUI5 has following predefined four DATA models available:

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.

SAPUI5 has following predefined four data models available:

There are 4 TYPES of VIEWS available:

1. JS view
2. JSON view
3. XML view
4. HTML view

There are 4 types of views available:

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;
}}});

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;
}}});

VAR obj_name = NEW sap.m.ControlName(“id of control”,{ PROPERTIES, events, aggregations });

var obj_name = new sap.m.ControlName(“id of control”,{ properties, events, aggregations });

A web application which GIVES same LOOK and FEEL to the user in DESKTOPS and mobile DEVICES.

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

Sap uses TWO mechanisms, routing and EventBus. Routing Is specifically USED for bookmarking the URL. We define routing in component.js within the metadata. It also defines the navigation path and HASH changer which is used at the runtime to CHANGE the url of the particular screen.

Sap uses two mechanisms, routing and EventBus. Routing Is specifically used for bookmarking the URL. We define routing in component.js within the metadata. It also defines the navigation path and hash changer which is used at the runtime to change the url of the particular screen.

sap.ui.commons, sap.ui.table and sap.suite.ui LIBRARIES for DESKTOP application development and sap.m LIBRARY ALONG with sap.ui.layout for Fiori application development.

sap.ui.commons, sap.ui.table and sap.suite.ui libraries for desktop application development and sap.m library along with sap.ui.layout for Fiori application development.