SAP CRM User Interface Road Map:

Since the time SAP has emerged there has been a constant effort to improve the User Interface to gain
customer satisfaction and customer base. The result of these improvements gave us several UIs, out of
which the most popular UI which has got a great feedback from the customers is the IC WebClient UI
(CRM 5.0). The CRM WebClient is an extension of the IC WebClient where all the CRM applications are
developed and made compatible to the WebClient framework.

Kalyan trainerkalyan@gmail.com
Architecture of CRM WebClient:

WebClient is based on a multi-layer architecture on the server side:

1. Presentation layer: The Business Server Pages (BSPs) are the presentation layer of the IC
WebClient. They are the basis for the HTML page of the IC WebClient running in the IC
agent’s Web browser.
2. Business object layer: Data of business objects of an IC WebClient session, such as business
partners, products, and transactions are handled by the business layer of the IC WebClient.
3. CRM database

Architectural Flow of WebClient UI:

Kalyan trainerkalyan@gmail.com
Overview of WebClient User Interface:
The purpose of CRM WebClient user interface is to support an employee in fulfilling all of the important
day to day tasks that his role entails in an organization.

Eg: Employees from Marketing department involve in segmenting target groups, create marketing
campaigns etc.

Eg: Sales employees involve in creating sales orders etc

Structure of the WebClient UI:

Kalyan trainerkalyan@gmail.com
The User interface is divided into three large and self contained areas:
1. Navigation bar: to navigate between different CRM Applications
2. Header area: Contains global functions like saved search,
3. Work area: displays all page types

Page Types:
1. Home page: The home page is the starting point for every user in his or her daily work. It
contains the most important personal information and provides access to the most frequently
used tools. In addition to links, entire reports may also be included directly on this page.

2. Work Center page: Every top-level menu item has an individual work center page. This work
center page contains a set of shortcuts and provides access to all CRM components related to
the work center. In addition to links, entire reports may also be included directly on this page.

3. Overview Page: The overview page is a user-friendly interface for viewing and editing object-
related information. This is the most important element in the CRM WebClient UI. Overview
pages consist of a main assignment block (Details) that allows object identification based on
header data, and a set of assignment blocks that show related information.

4. Edit pages allow users to create or maintain CRM content. They are linked to an assignment
block on the overview page. Edit pages are designed as form views.
5. Edit list pages provide users with a special way to perform list maintenance, in the order entry
process
6. Search Help Dialog Box: This dialog box allows users to select objects they want to assign to the
object currently being edited, for example, account search help. Filters can be applied here.

Kalyan trainerkalyan@gmail.com
 7. Assignment Blocks: The overview page contains assignment blocks that you can use to display
the most important data for a business object. From here you can navigate to edit page or edit
list
8. Calendar: The calendar can be accessed from the first level of navigation and displays all or the
user’s appointments and dates
9. E-Mail Inbox: The email inbox gives you access to groupware solution to ensure that emails from
the CRM application can be sent and received

User Interface Personalization:

CRM WebClient offers the user to design the user interface according to his requirements and choice.
The settings done in personalization will not affect the application or settings of other users.

Business Role Concept:

Business roles are collections of activities that enable a user to participate in one or more business
scenarios within an organization.

EG: Marketing Prof, Sales Prof, Service Prof

Business Role consists of:

1. Navigation bar Profile: structure of the navigation bar displayed on the user interface

2. Role config key: defines a configuration that is based on the business role

3. Technical Profile: The call for the internet page loaded after you log off from the WebClient

4. Layout Profile: defines the navigation frame of the WebClient like header area, footer area,
work area and navigation bar

5. PFCG Role: is a technical container for authorizations required to perform the business functions
that comprise the business role eg: executing sap transactions. We can assign only one PFCG
role to one business role

Business Role Assignment:

1. Organizational model assignment

2. Test user assignment (SU3)

Component Workbench:

UI Component Overview:

1. It represents a self-contained, reusable unit

Kalyan trainerkalyan@gmail.com
 2. It encapsulates reusable elements such as windows, controller, context, context nodes and their
attributes
3. It is assigned to a BSP Application
4. It exposes visual interface to the outside world
5. It is created and processed with the component workbench

The component workbench is the development environment for UI components of the WebClient UI
framework. Transaction code is BSP_WD_CMPWB.

The Component workbench is divided into three areas:

1. Tool bar area

2. Component structure area
3. Detail area

View:
View is a smallest unit of the WebUI screen. A combination of several views will make up the complete
screen. Views cannot be displayed independently, it can only exist within a UI component and assigned
either directly to a window or a view set.

View controller: every view has exactly one view controller and is responsible for processing the entries
made, actions performed by the user and managing data related to the view.

View context: manages the data relating to the view. It is a linking layer between presentation and
database.

Event handler: are used to handle user actions on the user interface. If you create an event handler for
example ‘CLICK’, a method will be created in the view controller as ‘EH_ONCLICK’ and is called from the
DO_HANDLE_EVENT method.

Window: a window is a layer on a UI component and is used for arranging navigating views or view sets.
To be able to display a view or view set they have to be assigned to a window.

Component controller: there is exactly one component controller per UI component. It is a central data
store for UI component and can be accessed by all the objects within the Component. It is used for cross
component navigation and data transfer.

Custom controller: custom controller like Component controller is an additional data store within the UI
Component and can be used for sharing data across views within the component. There can be several
custom controllers.

Runtime repository: is the tool for visualizing and processing the repository.xml file. The tasks that can
be performed by using this editor are:
1. Connecting UI components to component set.
2. Assigning views and view-sets
3. Creating navigational links

Kalyan trainerkalyan@gmail.com
 4. Defining the component interface

Business Layer of WebClient framework:

The Generic interaction layer and Business Object layer belong to the Business Layer.

Business Object Layer (BOL): stores the data related to the business objects together with a defined set
of attributes and relationships during the runtime.

Genil Objects:
1. Root objects: can be addressed via its unique key. Each root object is an access object but not
vice versa
2. Search object: is a defined object search and provides root objects or access objects as result set
3. Dynamic search object delivers more features than a simple search eg: it provides search
operators
4. Dependant objects: are directly or indirectly depends on root objects and can be addressed only
via the root objects
5. Search result object: it is a root object and is the result of the search object
6. Access object: can be accessed directly via its unique key.

The transaction code to access GENIL browser is GENIL_MODEL_BROWSER.

The transaction code to access the BOL is GENIL_BOL_BROWSER.

Kalyan trainerkalyan@gmail.com
Kalyan trainerkalyan@gmail.com