CRM PCUI Technology

CR2015 - SAP CRM PCUI Overview
India SAP CoE, Slide 1
PCUI
PrepareMe
TellMe
5
ShowMe
LetMe
HelpMe
PCUI
PrepareMe
TellMe
5
ShowMe
LetMe
HelpMe
PrepareMe
Purpose
Use
Challenges
Purpose
Providing UI to cover following user requirements
Intuitiveness
Consistency
Appealing and familiar look and feel
Easy navigation
Easy to learn and remember
Responsiveness and efficiency
Logical alignment with workflow and processes
Easy access to various systems
The right content at the right time
Personalized working environment
Provides online access to SAP CRM solution
Use
No installation needed on computers, Access via Web browser
(based on browser technology web client )
Preconfigured user roles
User-friendly interface: Intuitive and recognizable interaction
design, Easy navigation and Internet-like behavior
Easy to develop with pre defined elements
Easy to adapt and Modify
Get access to information quickly
Reduce processing time to a minimum
Preassembled content for complete business tasks
Easy adaptation of the roles for specific needs
Personalization and configuration: Users have personalization
options to adapt content to their use/liking.
User interface is flexible and configurable to embrace customerspecific business requirements.
Knowledge Management
Challenges
For every business transaction there is individual PCUI
application which makes it difficult while traversing
Different user interface in online and offline mode
Specific developments: Main effort for complex
modifications
Not full scope in CRM 4.0 (e.g. Reference doc in
complaints, customer hierarchy, ...)
Double maintenance: authorization in CRM + Roles in
Portal
Creation of several CRM roles
PCUI Technology
PrepareMe
TellMe
5
ShowMe
LetMe
HelpMe
Requirements for People-Centric

CRM (based on CRM 4.0 SP01)
Enterprise Portal 5.0 SP05, Patch 1, Hotfix
1, including the Knowledge Management
Platform (KM)
Business Package for SAP CRM 4.0, 50.1
Business Package for Communication
The Portal Plug-In (WP Plug-in) must be
installed on all backend systems.
PCUI Landscape
CRM Server
BSP Application
CRM_BSP_FRAME
Enterprise Portal
Portal Server
Web Server
MVC
Architecture
IView Server
Flow Logic
Page Builder
PCUI Technical Infrastructure

The People-Centric UI is based on a
combination of
Portal Technology
The Model-View-Controller Programming
Model
Business Server Pages

combination of
Portal Technology
Model
Enterprise Portal Technology

The People-Centric UI as a whole is seamlessly
integrated into SAP EP.
The portal is the single point of entry for every user and
offers access to the Web-based SAP applications as
well as to different content from document
management tools or Web-enabled applications.
Special features of the portal, like Single Sign-On
(SSO), personalization, and Drag&Relate, make it the
appropriate workplace for any user.
EP : Corner stone for PCUI

Provides CRM Users with easy access to multiple sources
EP provides the screens with an intuitive navigation
experience, solid session management, and offers access
to various sources of content. Knowledge management,
role-dependent access, and the integration of SAP and
non-SAP applications make the portal an integral part of
the People-Centric UI of the mySAP Business Suite.
Technical Components within EP
Sales Contract on Portal

combination of
Portal Technology
Model
Model View Controller

The MVC design methodology is
an object-oriented methodology
that efficiently relates UIs to the
underlying data models
The formal separation of these
three areas is realized by means
of the three components model,
view, and controller.
User
Display Input
View
Controller
With the help of these

components, complex Web
applications can be divided up
into simpler, logical units.
Model
MVC Architecture
PCUI is based on MVC Architecture:
VIEW : The view is the visualization layer, which is responsible for
the rendering of the graphical and textual outputs. The view
receives instructions from the user and passes these on to the
controller.
CONTROLLER : The controller monitors and interprets the users
mouse and keyboard input and causes the model or view layer to
react accordingly. Data entries are sent on to the model for
processing.
MODEL : The model delivers or receives data from the controller
and ensures that the data is processed by the corresponding
business logic. The model deals only with internal processing,
with no reference to the UI.
MVC Programming in PeopleCentric UI Framework

The UI framework is built on the MVC
programming model and implemented
in two layers of controllers. One main
controller (C0) controls several sub
controllers (C1, C2 and so on )
These controllers communicate over
the generic interface of the interaction
layer with the model. The business
objects also provide a generic
interface to the interaction layer.
These generic interfaces are the
model access layer.
Two Stage MVC
UI framework Architecture
Layered Business Transaction

Model
User Interface
PUT_METHOD
GET_METHOD
Interaction layer
PUT_DATA_API
API
GET_DATA_API
GET_DATA_API
Object
layer
User Interface
User Interface
PUT_METHOD
GET_METHOD
Interaction layer
PUT_DATA_API
API
GET_DATA_API
GET_DATA_API
Object
layer
PCUI User Interface

The People-Centric UI is built from a set of
elementary UI components that can be
combined to form higher levels of hierarchically
structured components.
The top-level pattern of the People-Centric UI
page is called a business object pattern, which
is a combination of more specialized patterns
The Object Identification Pattern (OIP)
The Object Data Pattern (ODP)
Pattern based Interface

Orientation Area
O
Search Area I
Result List P
Detail Area 1
O
D
Detail Area 2 P
Interaction Layer
User Interface
PUT_METHOD
GET_METHOD
Interaction layer
PUT_DATA_API
API
GET_DATA_API
GET_DATA_API
Object
layer
Interaction layer
The interaction layer provides controllers with one
single interface across all business objects.
The interaction layer controls the flow of any business
transaction. Based on the user inputs (field
modifications, function keys, and so on), it controls
which methods of an object are performed (Fcode
control), which objects are to be displayed or modified,
or which elements of the corresponding UI are to be
activated (dynpro or field control).

combination of
Portal Technology
The Model-View-Controller Programming Model

Business Server Pages (BSPs) are HTML
pages that contain the actual application
logic and presentation logic.
BSPs define the Web user interface and

determine the elements of user interaction
The views of the People-Centric UI are
implemented as BSP elements.
BSP Application
A Business Server Page (BSP) application
is an independent development project that
is created and edited in the SAP
development environment (transaction
SE80).
A Business Server Page (BSP) application
is a complete functional application, like a
classic SAP transaction. However, this
application is executed in a Web browser
rather than in the SAPGUI
PCUI Role Concept
User 1
Content 5
Content 4
By creating roles you can

assign different pieces of
content to different group
of users
User2
User3
Content 4
In People Centric CRM all

the content needed to
perform a job is packaged
as a ROLE
Content 2
Different Users,
Different Needs
Content 3
Content 2
Content1
Individuals Perform
different Job Functions,
business activities and
tasks
PCUI Role Concept Contd..

A role consists of
worksets for each
Business activity
Each workset provided
pages containing Iviews
and external services to
access all underlying
applications needed to
perform a task
Preconfigured Roles in mySAP

CRM
The following applications run in preconfigured Roles
Sales
Marketing
Service
Interaction channel
Channel management
Portal Administration
Additionally many industry roles are

available
PCUI Customization
To address customer-specific UI requirements, an additional
customizing layer is available for blueprint tables.
The UI framework connects the business logic to the UI with the configuration
information from blueprint tables.
Model access classes give standard interfaces to business objects which, in
conjunction with the configuration information contained in blueprint tables,
connect the UI to the business logic.
The interaction layer provides controllers with one single interface across all
business objects.
Blueprint tables are tables that contain all the configuration information
required by the new UI framework to specify the application UI (Web-based).
Blueprint applications are applications built by Customizing the blueprint
tables of the new UI framework.
Blueprint Table
The main blueprint table CRMC_BLUEPRINT drives
the whole UI when the application is requested by
the browser, the main controller first looks into the
main blueprint table, which is where the basic
parameters of the application have been set.
The entries in the main blueprint table also determine
which blueprint sub tables are relevant for the setup of
the current screen. Thus the main blueprint table is the
basic blueprint for the design of an application.
Maintaining Blueprint Table

The maintenance of
the blueprint tables is
done within separate
maintenance
transactions.
CRMC_BLUEPRINT for
SAP product
development
CRMC_BLUEPRINT_C
for customer
developments
Application Set
Blueprint tables
define application
via tables for
toolbars, tabstrips,
fieldgroups etc.
Search
Group
Toolbar
Group
Tabstrip
Group
Toolbar
Group
Steps to Develop Blueprint

Application
There are only two steps to
be performed to develop an
application with this UI:
The views of the applications
have to be customized via
the blueprint tables.
A class with special methods
has to be implemented
inside the model in order to
access the business data
Steps for Blueprint Table

maintenance
Define the application set

Define the screen setup in the main blueprint table
If you have role-dependent views, define them here
Define events
Define the layout of toolbars, tabstrips, and search groups
Create screen structure
Define field groups
Create model access class and complete application set
Maintain application log
Define object link navigation Complete F4 help, if necessary
Test the consistency of entries
Generate the layout
PCUI - Floor Plan Concept

The new Floor plan is designed for mySAP
CRM 5.0. It is a general interaction and
navigation concept for PCUI.
The main reason for designing a new Floor

plan is the intention to improve the
user Experience of mySAP CRM 5.0.
PCUI Overview
1
Prepare Me
2
Tell Me
3
Show Me
Let Me
Help Me
Show Me
Opening Applications without PORTAL
environment
Finding Technical Information for an
application
OIP and ODP Areas in an application
Views in an application
Standard Navigations through Toolbar
Basic Customizations in
CRMC_BLUEPRINT_C

environment
application
CRMC_BLUEPRINT_C
BSP Application for CRM :

CRM_BSP_FRAME
Use SELECT.HTM to
get list of BSP
Applications
Execute
SE80 select BSP

Application
CRM_BSP_FRAME
BSP Application for CRM :

CRM_BSP_FRAME Contd..
List of CRM
Applications will
be displayed
Select a application to
be opened e.g : Sales
Orders
Sales Order
application in
PCUI

environment
application
CRMC_BLUEPRINT_C
Transaction CRMC_PCUITOOLS
GOTO Support Tools for
Application Developers
->Analysis Tools ->
Determine the Correct
Model Access Class ->
Execute
Enter the application

Name (e.g.
CRMD_BUS2000112
Service Contracts)
Technical Information Displayed

for all the screen elements

environment
application
CRMC_BLUEPRINT_C
OIP
Search area
Result
List
ODP
ODP

environment
application
CRMC_BLUEPRINT_C
List View
List View Contd..
Form View

environment
application
CRMC_BLUEPRINT_C
Standard Toolbar
CRM 5.0 applications consist of a set of
portal pages and views :
the BSP application with List and Details
view
the Summary page and the Fact Sheet
page.
Standard Toolbar Contd..

Click on the Fact sheet
Detail View of Fact sheet

environment
application
CRMC_BLUEPRINT_C
CRMC_BLUEPRINT_C
To view the List if application and application
elements Layout of User Interface (People-Centric
UI)->Application/Layout->Define Layout of the
People-Centric UI (Customizing Tool)
On F8
CRMC_BLUEPRINT_C Contd..
Select the application to view
its details like associated
Application set, structure
Name etc
List of fields in a field
group
All the standard attributes (read only,

mandatory, default value) can be enabled
/disabled in the check box available.
Event associated with the Tab
page Group
Path - Layout of User Interface
(People-Centric UI) ->
Application Element ->Field
Group -> Layout Generation
PCUI Transactions
Searching a Sales Order
Create a Installed Base
Search Sales Order

Search Sales
order with
blank search
Create IB
Create
IB
Create IB Contd..
PCUI Overview
PrepareMe
TellMe
ShowMe
LetMe
5
HelpMe
Let Me
What are different technologies used in PCUI?
Explain PCUI landscape.
Explain concept of blueprint tables, floorplan,
controller, Application set.
Change text of a standard field.
Hide a standard field
PCUI Overview
PrepareMe
TellMe
ShowMe
LetMe
5
HelpMe
Important URLs
Debugging PCUI Application
https://weblogs.sdn.sap.com/pub/wlg/2280
PCUI and EEWB
https://weblogs.sdn.sap.com/pub/wlg/2040

CRM PCUI Technology

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CRM PCUI Technology

Uploaded by

Copyright:

Available Formats

CR2015 - SAP CRM PCUI Overview

India SAP CoE, Slide 1

India SAP CoE, Slide 4

India SAP CoE, Slide 5

India SAP CoE, Slide 7

Requirements for People-Centric

India SAP CoE, Slide 9

India SAP CoE, Slide 10

PCUI Technical Infrastructure

India SAP CoE, Slide 11

PCUI Technical Infrastructure

India SAP CoE, Slide 12

Enterprise Portal Technology

India SAP CoE, Slide 13

EP : Corner stone for PCUI

India SAP CoE, Slide 14

Technical Components within EP

India SAP CoE, Slide 15

Sales Contract on Portal

India SAP CoE, Slide 16

PCUI Technical Infrastructure

India SAP CoE, Slide 17

Model View Controller

With the help of these

India SAP CoE, Slide 18

India SAP CoE, Slide 19

MVC Programming in PeopleCentric UI Framework

India SAP CoE, Slide 20

Two Stage MVC

India SAP CoE, Slide 21

Layered Business Transaction

India SAP CoE, Slide 22

India SAP CoE, Slide 23

PCUI User Interface

India SAP CoE, Slide 24

Pattern based Interface

India SAP CoE, Slide 25

India SAP CoE, Slide 26

India SAP CoE, Slide 27

PCUI Technical Infrastructure

India SAP CoE, Slide 28

Business Server Pages

BSPs define the Web user interface and

India SAP CoE, Slide 29

PCUI Role Concept

India SAP CoE, Slide 31

By creating roles you can

In People Centric CRM all

PCUI Role Concept Contd..

India SAP CoE, Slide 32

Preconfigured Roles in mySAP

Additionally many industry roles are

India SAP CoE, Slide 34

India SAP CoE, Slide 35

Maintaining Blueprint Table

India SAP CoE, Slide 36

India SAP CoE, Slide 37

Steps to Develop Blueprint

India SAP CoE, Slide 38

Steps for Blueprint Table

Define the application set

India SAP CoE, Slide 39

PCUI - Floor Plan Concept

The main reason for designing a new Floor