Created by: Suryamani Kumar, SAP CRM, December 2010 SAP CRM Fundamentals: Refer notes
Web UI Architecture
Web UI Architecture
Contents :
UI components Generic interaction Layer and Business Object Layer.
Purpose
Explain the technical concepts and Architecture used by the CRM web client UI ,Such as Business Server Pages (BSPs) and the underlying Business object layer. Describe the different layers of the web client UI software architecture.
Use
One Web-based, easy-to-use, and easy-to-configure UI for all SAP CRM Online users. Easy to configure web client with minimal amount of coding. Appealing web application style visual design consistent across on-demand and on-premise.
Challenges
New UI Architecture & Concepts. Understanding MVC Architecture, Modification and building new MVC BSP page and integration of new flow logic BSP Screens. Generic Interaction Layer (GeIL) and Business Layer (BOL).
Architecture
UI components - Role of UI components in the Framework
Some of the views of the web client are persistent others views are selected and changed dynamically thought web client session.
8
To find out the name of the UI Component and view place your cursor in an editable field and Press F2.
9
Component Workbench
A UI Component is the bundle of views ,view sets etc. that logically belong to each other. A UI Components can be edited in the component workbench. T-Code :BSP_WD_CMPWB
10
The model of the CRM web client BSPs consists of context and context nodes that link the fields of a view to underlying.
11
The controller is the first element that is insatiated when the system navigates to a particular view.
12
Transaction BSP_WD_CMPWB Displays all development objects of the CRM web client applications. 13
Context Nodes
Context nodes are link between the input fields on the view and the data model in the BOL. 14
View Details
The layout of CRM web client views can be implemented in two different ways that both rely on HTMLB tags. 15
View sets are views as well, they have a Controller class and a context class but no context nodes. 16
Event Handler, Inbound and outbound plugs are methods of the controller class.
17
UI Components Summary
Describe the role of the UI components in the framework. Get a basic understanding of the model view controller concept.
18
Architecture
19
20
Business Layer
- BOL works with the data at run time. - Data that are changed in the user interface are first changed in the BOL and then transferred to the Generic interaction layer.
21
GenIL Components
- A GeniL Component is a Class that acts as a link between the existing CRM Business Logic and the UI framework. - GeniL Component does the mapping between the data model that is defined and the actual data interface.
22
Component Sets
Business Object: Smallest unit of an object Model. Each BO is Assigned a unique name. The data model of a component set can be visualized in the BOL Browser. 24
The Business object layer works with the data at runtime and communicate with the generic interaction layer.
25
BOL Browser
BOL browser is the tool used by developers to test the framework independent from the user interface.
27
To access the data of the single business object you need to navigate Through the data hierarchy starting with the root object.
28
Describe the functionality of the Generic Interaction Layer. Explain the classification of the Business Objects. State the role of the Business Object Layer in the Framework.
29
Customization
UI Configuration Tool
30
31
32
LetMe
BSP_WD_CMPWB
Transactions
Component Workbench
33
Describe the role of the UI Components in the framework. Get a basic understanding of the model view controller view concept. Explain the technical architecture of the SAP CRM User interface. State the basics of the Model view controller concept. Work with the system tools: BOL Browser and GenIL Model Browser.
34
Web UI Architecture
35
Definition
The Interaction Center Web Client, as part of SAP Customer Relationship Management (SAP CRM), provides tools to ensure efficient and consistent customer service by collaboration and communicating with customers over various channels. It supports agents and managers who are involved with the interaction center.
IC Agent Agent can handle inbound or outbound service, sales, or marketing transactions using the phone, e-mail, fax, or the Web. They can process business transactions such as quotations, sales tickets and service tickets, and enhance their productivity by using alerts, scripting, and a solution search. All relevant account information is available to them in once location, such as account data, order status and product-related information.
36
Use
The Interaction Center supports all CRM strategies, such as; Sales: processing of sales transactions, opportunities, product proposals Service: e-mail processing and workflow, solution database, service transitions Marketing: campaigns, call lists, product proposals. In addition, the Interaction Center supports multi-channel communication: Telephone: incoming and outgoing calls, call lists, CTI (computer telephony integration) connation E-mail, fax, SMS Internet: inclusion of Internet and intranet pages, co-browsing, callme-back, Web chat, Web telephony.
37
Challenges
Customizing Process of IC Web Client Business Role New Functionalities Available In Account I identification: Accounts Employee details Install Base Objects Customizing Process of Account Identification Functions using Account Identification profiles New Transactions types added in IC Web Client Business Transactions ERP Quotation in ERP Sales Order ERP Sales Contract
38
39
Create the new profile by copying an existing profile that more or less matches your requirements. Account Identification Profile Agent Inbox Profile Business Transactions Profile The business transaction profile controls which CRM business transaction type is liked to the navigation bar buttons.
Assing Functional Profiles to Business Role
43
IMG Path: Customer Relationship Management > Business Roles > Define Organizational Assignment Transaction: PPOMA_CRM Assign infotyp: Goto > Detailed Object
Users / Business Partners are assigned within the Organizational Model to a Position User / Business Partners can be assigned to multiple Positions
Each Position can have exactly one Business Role assigned to (Infotype 1163)
54
55
56
57
58
59
62
65
67
69
Let Me
Transactions
CRMC_UI_PROFILE Define Business Roles
CRMC_UI_NBLINKS
PPOMA_CRM
71
Let Me
Task: 1.Define Business Role E.g. ZIC_AGENT 2.Assign to Organizational Unit Org Unit 3.Define Account Identification Profile E.g. ZDEFAULT 4.Assign to Navigation Bar Profile (Work Center) 5.Assign Function profiles to Business Role 6.Define Business Transaction profiles E.g. ZDEFAULT 7.Assign to Function profiles to Business Role E.g. IC_BT 8.Define Inbox Profiles (Agent Inbox Profile) E.g. DEFAULT 1 9.Assign to Function profile E.g. IC_INBOX
72
74
Unit Summary
Explain the process of customizing IC Web Client functions
Use Wizards supporting the Configuration Create a new Account Identification profile Create a new Business Transaction profile
76