Introduction to NWBC

NWBC (NetWeaver Business Client), ) is a new SAP UI, presenting end users with a
seamless integration of classic SAP GUI-based transactions and newer Web Dynpro-based
applications. In the desktop variant a high–fidelity UI is offered to improve user experience. Thus the NWBC provides typical modern desktop-based user experience.

NWBC available in two flavors:

  • NWBC for HTML (Browser based)
  • NWBC for Desktop (Windows based)

NWBC for HTML is a browser-based shell (available only against ABAP systems) for
casual use scenarios. Within this environment, all SAP GUI transactions will be rendered
using the SAP GUI for HTML rendering engine.

NWBC for Desktop is a .NET based application that targets the power user. In this
scenario, the SAP GUI itself is used as rendering engine if installed. NWBC effectively
“replaces” SAP GUI as main entry point to SAP applications; however, it does use
SAP GUI to run existing applications.


› increased end user adoption
› single point of entry for the user
› content tailored to users needs
› low overall TCO

Key features
› standard client for Business Suite
› role-based (PFCG / PCD) access to SAP business applications
› browser-like navigation
› integration of different UI technologies
› allows modifications-free mash-ups via Side Panels
› supports access and navigation to other systems

Role maintenance in PFCG:

Roles will be configured  in transaction  PFCG are mapped to the menu structure of NWBC.

In transaction PFCG you can configure roles . In real life, a role corresponds to the work that a person does within a company or the position held, for example, a sales person or someone working in support. In transaction PFCG, roles are defined matching the real life roles that people play within a work situation. More specifically, a role within transaction PFCG is a set of transactions that persons within specific roles would need for their daily work. In this example, a sales person could have a role that requires transactions to add new customers, display customer details, or to enter a new lead.

Given the existence of roles within transaction PFCG that describe the typical work persona, use transaction SU01to assign these roles to specific users. A user in the system can have any number of roles assigned, which reflects the real work that the person does within the company.

Given the roles in transaction PFCG, the SAP Easy Access menus are displayed directly after logging on with SAP GUI. These are effectively the menu trees as expressed in one or more roles for each user. This allows the user to quickly start the relevant transactions for their daily work.

NWBC builds on this same PFCG infrastructure in the ABAP system. The NWBC runtime retrieves all roles assigned to a specific user and makes them available to the shell. The shell uses exactly the same role information to show the user the possible transactions that might help them with their daily work.

For this reason, the shell in NWBC is in the first instance another expression of the SAP Easy Access menu, providing roughly the same functionality.


Introduction to SAP Fiori

What is SAP Fiori?

SAP Fiori mobilizes some of the most common business functions like Workflow approvals, information lookups and self service tasks. It is collection of apps with a simple and easy to use experience for broadly and frequently used SAP software functions that works seamlessly across devices Desktops, Tablets, Smartphones and Smart Watches.

SAP Fiori is the new user experience (UX) for SAP software. It applies modern design principles for a completely re-imagined user experience across devices and deployment options. SAP Solutions, such as the SAP Business Suite (SAP S/4) applications, user SAP Fiori UX to provide a personalized and role based user experience for enterprise-wide engagement across lines of business.

While updating a single standalone SAP Fiori App is quite straight forward complexity rises with increasing number of user cases, applications, custom enhancements, etc. on productive system landscapes. This guide provides an overview of major challenges and areas of concern.

There are 500+ role-based apps, that apply the SAP Fiori UX providing enhanced user productivity and personalization for customers using SAP S/4HANA, SAP Simple Finance and SAP Business Suite on any database.

SAP Fiori UX supports a variety of roles in lines of business include HR, Finance, Manufacturing, Procurement, and Sales.

Technology behind Fiori?

Here comes my favorite web language “HTML5”


‣ HTML5 and JAVA Script UI development framework

‣ Future direction for SAP User interfaces

⇒ SAP NW Gateway

‣ Software layer for SAP ERP that exposes SAP data using OData (web) protocal

Scope of SAP Fiori?

SAP Fiori comes with three major app types,

⇒ Transnational Apps

Fact sheets

Analytical Apps

⇒ Transnational Apps

These apps let you perform transactional apps, such as creating leave request for an employee. They represent simplified views and interaction with existing business processes and solutions. They run best on an SAP HANA databases with acceptable performance.

For the transactional apps, the ABAP front-end server contains the UI layer with the product-specific UI components for the products (for example, ERP Financials (ERP-FIN), Customer Relationship Management (CRM), Supply Chain Management (SCM)) as well as the infrastructure components. The infrastructure comprises the central UI component with the SAP UI5 control library and the SAP Fiori launchpad as well as SAP Gateway with the OData enablement.

The front-end components have access through a trusted RFC connection to the ABAP back-end server containing the business logic. The underlying database can be an SAP HANA database, or any database, and is accessed from the back-end server.


 ⇒ Fact sheets

These apps display contextual information and key facts about central objects used in business operations. From an architectural perspective major differentiators to transactional apps are:

‣ Fact sheets run only on a SAP HANA database / Suite on Hana system (no support of any DB)

‣ Directly accesses search engine on the backend server via INA search protocol

‣ Requires reverse proxy (SAP Web Dispatcher) handling the request to different systems

⇒ Analytical Apps

These apps provide role-based insight into real-time operations of a business by collecting and displaying key figures directly in the browser. Analytical apps combine the data and analytical power of SAP HANA with the integration and interface components of SAP S/4. They provide real-time information on large volume data in a simplified front end for enterprise control. With analytical apps, most important key performance indicators (KPIs) can be closely monitored in real time and allow immediate reaction on changes in market conditions or operations. From an architectural perspective major differentiators to transactional apps are:

‣ They require HANA database / Suite on HANA system and XS Engine

‣ Directly accesses HANA XS Engine

‣ Requires reverse proxy (SAP Web Dispatcher) for handling the requests to the different systems.



⇒ SAP Fiori User Roles


Click here to get configuration document of “Configuring SAP Fiori Apps

SAP HANA Trail Versions

Get the Next Generation
of Solutions For Your Business

From cloud and mobile apps to big data analytics, we have the solutions you need for your industry delivered on SAP HANA, our powerful in-memory platform. Ready for a test-drive?

Here you go for HANA Trail Versions. , cloud edition and much more….!!