UI Framework Architecture

Detailed View

SAP Enhancement Package 1 for SAP CRM 7.0

1
 UI Framework Architecture – SAP EHP1 for
SAP CRM 7.0

Continued Focus on Usability:

The SAP CRM Web Client UI

„ Drive rapid user adoption and

productivity via one web-based,
easy-to-use and easy-to-configure
UI for all SAP CRM on-line users

„ Appealing Web application style

„ Easy and flexible UI configuration

„ Usability towards joy-of-use

© SAP 2009 / Page 2

With SAP EHP1 for SAP CRM 7.0 continued its focus on usability and quick user adoption.
Based on clear feedback by SAP customers SAP decided to further enhance the new SAP
CRM user interface that follows the requirements of the market while unifying the user
experience across all SAP CRM users

If it comes to usability: whatever is done – one will love the other one won’t, so the key to
make our customers successful is not only to provide a complete new navigation and
interaction design, but at the same time provide all the tools required on project base to
adapt the user interface to the concrete needs of the business user

In parallel the new User Interface makes the big next step into the area of state-of-the-art
web design which is used across SAP’s CRM on-demand and on-premise solution

This big step towards joy-of-use has been achieved by changing only the user interface
oriented software layers, leaving the general architecture on the CRM server untouched.
I.e. the business process customizing stays the same as in previous releases.

2
 Content

1. General Overview and Concepts

2. Presentation Layer
3. Business Object & Generic Interaction Layer
4. Tools
5. Customer Enhancements
6. UI Check Tools

© SAP 2009 / Page 3

3
 UI Framework Architecture – SAP EHP1 for
SAP CRM 7.0 Key Benefits

„ Simple tasks achievable without

Simplicity
training

„ Support different application variants

Flexibility (Tiled Layout, Task Based UI)

„ Multi-browser support

Performance „ Easy configuration even for power

users

„ Use of Ajax, Load on Request

© SAP 2009 / Page 4

In general the new CRM UI Framework contains the BOL/Genil Layer as well as leverages
the BSP technology via a newly created tag library, supported by a new toolset for
customers, partners, consultants and application programmers.

Application Variants: Based on the one holistic Framework there exists the need to provide
the flexibility and freedom to server different navigation and interaction paradigms (e.g.
within an Interaction Centre application a minimum of scrolling is allowed, a CRM on
Demand solution has limited and easy to use customizing and configuration possibilities).

Basic HTML: A Cross browser support can be achieved as few browser specific HTML gets
rendered

Componentized application: One of the central concepts of the new CRM UI Framework is
the componentization. The different applications are logically bundled within components,
which follow the “black box” principle. Every component can run stand-alone and does not
make any assumptions about the surrounding environment.

Load on request: In contrast to the formed concept used within the Interaction Centre
WebClient, the different components get only loaded (instantiated) when they are
called/used.

4
 Overview: Layers of CRM Applications

Web Browser* CRM WebClient

Presentation
Layer (BSP)
CRM
WebClient:
Specific
Layers – New
UI Framework Business
Layer
(BOL/GENIL)

Layers of CRM Business

Underlying Engine
Business
Application
© SAP 2009 / Page 5 * New in EHP1

The SAP CRM EHP1 for SAP CRM System includes on a high level 3 different layers:
„ The Business Application Layer: this is the CRM Server as a it existed in SAP CRM
4.0 and SAP CRM 5.0, which got enhance with additional functionality and new features
but remained technically unchanged with the new CRM 2006s UI Framework; e.g.
Customizing, Interfaces, Tables, Middleware, BAPI’s etc. are untouched by the UI
Framework.
„ The CRM WebClient specific Layer: On top of the Business application Layer this layer
was build containing the CRM UI Framework, which is based on the technology used in
SAP CRM 4.0 and SAP CRM 5.0 in the Interaction Center WebClient. This layer got
significantly enhanced with new concepts (e.g. Component/Window concept,
THTMLB/CHTMLB Tags, Tools)
„ The Web Browser: The CRM UI runs within standard Web Browsers. Currently IE 8.0
and Firefox 3.0 are the latest browsers supported with SAP CRM EHP1 for SAP CRM
7.0.

The next slide provides you a more detailed view on the content and the technology within
new CRM WebClient specific layer. As the Business application layer remains unchanged
by the new CRM UI Framework it will not be covered within this presentation in more detail.

5
 Overview: Layers of CRM Applications

Web Browser CRM WebClient

Presentation Controller
Layer Business Server
CRM Model
Pages (BSPs)
WebClient View
Specific
Layers – New
UI Framework Business Business Object Layer
Layer (BOL)
Generic Interaction Layer
(GenIL)

Layers of Business
Appl. Progr. Interfaces
Underlying Engine
(APIs)
Business (SAP CRM)
Application Tables

© SAP 2009 / Page 6

The Business Server Pages (BSPs) are the presentation layer of the CRM WebClient.
They are used to generate the HTML page of the CRM WebClient running in the user’s
browser. The business logic of CRM business objects and processes is not controlled by
the BSPs: presentations and data models are handled separately. Due to this clear
separation a great degree of flexibility in the UI Design is provided without changing the
underlying business logic and –business objects.

Business objects of an CRM WebClient session like business partners, product,

transactions, etc. are held in the Business Object Layer (BOL), within a therefore designed
caching mechanism in order to achieve high performances access to the objects from the
UI.

The Generic Interaction Layer (GENIL) handles the data transfer between CRM database
tables and the BOL. (for more details please refer to section: Business Object and Generic
Interaction Layer)

We will first focus on the CRM WebClient UI – the BSPs - and after that, we will take
a look at the data model of the business objects in the BOL.

6
 New UI: Browser Only and Portal Optional

Web Browser Portal

Web Browsers Enterprise Portal

Unified Unified
CRM UI CRM UI

Portal

SOAP/XML
Internet Communication
Manager
RFC

HTTP(S)
J2EE
ABAP (Not required by
(BSP) new UI Framework) SMTP

SAP Web Application Server 6.40

© SAP 2009 / Page 7

SAP Web Application Server 6.40 (and higher) contains two runtime environments: ABAP
and J2EE (Java 2 Enterprise Edition). However the CRM WebClient is based on the ABAP
stack and not making use of Java technology. The user interface (UI) is a so called
Business Server Page (BSP). Via the Internet Communication Manager (ICM), which is
also part of the SAP Web Application Server, the BSP is transferred as a Web page to the
front end client.
„ In general BSPs are a combination of ABAP Classes and methods and HTML. This
technology was already used within SAP CRM 3.1, 4.0 and 5.0 whereby the underlying
usage and concepts from CRM PC-UI and CRM WebClient differ significantly.

Note: A portal can be used but is not necessary to run the CRM WebClient

7
 CRM WebClient UI Integration Into
SAP Enterprise Portal

Screenshot:
Portal Integration
Half-Screen plus explaination
The CRM WebClient UI optionally runs
embedded in the SAP Enterprise Portal
environment, making use of the Portal
navigation as well as other Portal
functionality.

„ CRM work area runs full screen in place in

Enterprise Portal work area
„ Navigation and central functionality is
provided using enterprise portal functionality
„ Tool based migration of CRM WebClient
roles to Enterprise Portal roles
„ Flexibly map the CRM navigation into the
available portal navigation areas

© SAP 2009 / Page 8

8
 CRM WebClient Enterprise Portal Integration

Central
Search

CRM History
CRM navigation bar embedded in
transferred to Portal Portal History
navigation bars,
various options Saved
possible Search

Direct Link
Groups (e.g.
Quick Create)
in own iView
CRM work area
in place in
Portal work area

© SAP 2009 / Page 9

9
 Content

1. General Overview and Concepts

2. Presentation Layer
3. Business Object & Generic Interaction Layer
4. Tools
5. Customer Enhancements
6. UI Check Tools

© SAP 2009 / Page 10

10
 Layers of CRM Applications

Web Browser CRM WebClient

Presentation Controller
Layer Business Server
Model
Pages (BSPs)
CRM View
WebClient
Specific
Layers Business Business Object Layer
Layer (BOL)
Generic Interaction Layer
(GenIL)

Layers of Business
Appl. Progr. Interfaces
(APIs)
underlying Engine
Business (e.g. SAP CRM)
Application Tables
© SAP 2009 / Page 11

Business objects of an CRM WebClient session like business partners, product,

transactions, etc. are held in the Business Object Layer (BOL), within a therefore designed
caching mechanism in order to achieve high performances access to the objects from the
UI.

The Generic Interaction Layer (GENIL) handles the data transfer between CRM database
tables and the BOL.

11
 CRM WebClient:
Model-View-Controller Concept

S
Elements grouping as follows
„ Handle Events
Views (BSP) „ Update application
data „ Defines
„ Views
„ Define control flow application
„ View Sets Request data
Controller „ Usually
connected to
set business
Controllers (BSP)
functionality
„ Application Controller
Model
„ Component Controller
Response
„ Window Controller View get
„ View Controller
„ Custom Controller „ Visualization of the
application data

Model
„ Contexts Data flow
„ Context nodes Control flow

© SAP 2009 / Page 12

The basic elements of the presentation layer are Views, Controllers and the Model.

In the right picture the design pattern for decoupling presentation and logic of an
application is shown.

12
 Components, Windows & View(-Sets)

L-Shape with Work Center Component

Window: Service Order Search

View Set

ViewArea with
one view

Window 2 (Service Order Overview containing views)

© SAP 2009 / Page 13

13
 CRM Web Client: View Details

The CRM Web Client views can be based on a minimal amount of coding

Each configurable view is based on:

„ A page type related configuration tag
Specific implementations possible via:
„ Additional usage of base tags

© SAP 2009 / Page 14

14
 Content

1. General Overview and Concepts

2. Presentation Layer
3. Business Object & Generic Interaction Layer
4. Tools
5. Customer Enhancements
6. UI Check Tools

© SAP 2009 / Page 15

15
 Layers of CRM Applications

Web Browser CRM WebClient

Presentation Controller
Layer Business Server
Model
Pages (BSPs)
CRM View
WebClient
Specific
Layers Business Business Object Layer
Layer (BOL)
Generic Interaction Layer
(GenIL)

Layers of Business
Appl. Progr. Interfaces
(APIs)
underlying Engine
Business (e.g. SAP CRM)
Application Tables
© SAP 2009 / Page 16

Business objects of an CRM WebClient session like business partners, product,

transactions, etc. are held in the Business Object Layer (BOL), within a therefore designed
caching mechanism in order to achieve high performances access to the objects from the
UI.

The Generic Interaction Layer (GENIL) handles the data transfer between CRM database
tables and the BOL.

16
 Business Object Layer Versus
Generic Interaction Layer
Business
Object Query
Entities Core Cache
Layer Services

Generic
Interaction Application Interface
Layer

Generic Interaction Layer

R R R R

Component IF Component IF Component IF Component IF

genIL genIL genIL genIL

Component 1 Component 2 Component ... Component n

R R R R

API 1 API 2 API ... API n

Database(s)

© SAP 2009 / Page 17

The UI only deals with Business Object Layer entities and does frequent calls on a fine
granular basis.

On the level of BOL, there is a cache in memory to avoid unnecessary requests to the
lower levels

Whenever BOL cannot serve a request from the UI-Layer from its cache, it fires a request
to the Generic Interaction Layer

The Generic Interaction Layer itself just dispatches the request to the appropriate Generic
Interaction Layer Component(s) and bundles the results before it returns the request.

The Generic Interaction Layer Components are adapters that map the heterogenous APIs
to the unique component interface and are build by the application development of the
respective objects.

Remark:

The concept of the generic interaction layer components addresses a distinct area from the
concept of UI components that was discussed in the previous section.

17
 Content

1. General Overview and Concepts

2. Presentation Layer
3. Business Object & Generic Interaction Layer
4. Tools
5. Customer Enhancements
6. UI Check Tools

© SAP 2009 / Page 18

18
 The Component Workbench as Central Modeling
Tool for the CRM UI Framework

The workbench is the central access point to...

„ Components, Windows, Views

„ Runtime repositories
„ Component related BOL model

© SAP 2009 / Page 19

You can access the workbench via:

„ SAP Easy Access Menue -> Architecture and Technology -> Configuration -> Access
BSP WD Workbench.

19
 Components and Component Usage

Component A Comp. Controller Component B Comp. Controller

Context Context
Window A Window B

View 1 View 4

View 2 View 5

View 3

Runtime Repository
Component Usages
Component B
Window B

Public Elements of Component B

© SAP 2009 / Page 20

It is possible to reuse components within other components (e.g. Text Assignment

component is used in the component for the Sales and the Service order).

Based on the reuse concept generic, reusable application parts (so called embedded
components) are developed once and could be reused within different components (so
called embedding compoentes).

In the slide the embedding component (A) just has to access the public elements of the
embedded component (B) via the component usage which can be defined within the CRM
UI Workbench.

The embedding component handles the navigation into and out of the embedded
component and therefore can influce the navigation behavior directly.

20
 From UI Requirement to Technology

Requirement Tool Software Layer

Layout change Graphical UI
e.g. move field Design Tool Presentation
Layer (BSP)

Add new field to UI Layer Layers of

Business new UI
Layer (BOL) Framework

Add new field to

Interaction
Data Model CRM Easy Layer (GenIL)
Enhancement
Workbench
(EEWB) Layers of
Business underlying
Engine API
(e.g. SAP CRM)
Business
Application
Tables
© SAP 2009 / Page 21

21
 BOL and GenIL: Tools

Model Browser:
Presentation Visualizing BOL Model
Layer (BSP)

Layers of New Business

UI Framework Layer (BOL)

Interaction BOL Browser:

Testing Data retrieval from DB to BOL
Layer (GenIL)

Layers of Business
Underlying Engine API
Business (e.g. SAP CRM)
Application
Tables

© SAP 2009 / Page 22

There are some tools that help you to investigate the model of BOL and GENIL.
„ The Model Browser helps you to visualizing the BOL Model of the underlying business
objects
„ You can also see there the available attribute structure indicated the available fields
within the model itself, where the UI Configuration Tool works on

„ The BOL Browser gives you the ability to test the BOL-Objects and the underlying
Business Objects without UI in order to verify that the data is routed correctly though this
layer.

22
 Search Page Floorplan

A Wizard guided procedure the facilitates the creation of Search Pages

„ The Wizard supports

application development to
create Search Pages in a
more efficient and
productive manner by
reusing existing code
through base classes.
„ The wizard generates a
common BSP page layout
for the viewset, search and
result views so that
framework can centrally
maintain changes and
application development do
not need to adapt for their
pages.

© SAP 2009 / Page 23 * New in EHP1

Reduce amount of work by the application developer for creating search pages.
→ This has led to the design and implementation of base classes encapsulating common
search page functionality.

Use a common BSP page layout for the view set, search and result views.
→ This implies that Framework changes are made centrally once, thus freeing the
application developer from having to adapt their pages.

Reduce redundancy of generated classes by the wizard.

→ So far it has been possible to use the view creation wizard for creating search and result
views. The events SEARCH and CLEAR were always generated for every search view
leading to a large amount of redundancy. The search page wizard no longer generates the
event handlers as they are common to all search pages and are therefore part of the base
classes. This is just one example of several illustrating code reuse.

23
 Content

1. General Overview and Concepts

2. Presentation Layer
3. Business Object & Generic Interaction Layer
4. Tools
5. Customer Enhancements
6. UI Check Tools

© SAP 2009 / Page 24

24
 Customer Enhancements

There are several ways of achieving Customer Enhancements

View Layout Configuration:

„ Could be achieved via the UI Configuration Tool
„ Used for customer-specific layout and label changes (including custom fields and
views/tables)
„ Customer and SAP configurations are stored separately
Component Enhancements:
„ Enhance the functionality of components, views and controllers provided by SAP
„ Modification free via inheritance and using references
„ Uses replacement concept for components at runtime
„ On top of this it is possible to create completely new components
Application Enhancements:
„ Structural enhancements (fields and tables) via Application Enhancement Tool
„ Embed external content via Rapid Application Tool*

© SAP 2009 / Page 25 * New in EHP1

25
 View Layout Configuration

SAP Comp. Controller

Component
Context
Window Main Configure
Views
View 1

View 2

View 3
Enhance
Runtime Repository Component
Component Usages (wizard supported)
View Set Composition
Navigation

© SAP 2009 / Page 26

The SAP-delivered components can be adjusted by either UI Configuration Tool (e.g. for
view specific Layout changes) or by the Component Enhancement Concept for functional
enhancements (e.g. new events)

The Component Enhancement Concept is explained in more detail in the next slides

26
 Component Enhancement

SAP Comp. Controller Customer Comp. Controller

Component Component
Context Context
Window Main Window Main
View 1 View 1

View 2 View 2

View 3 View 3

Runtime Repository Runtime Repository

Component Usages Component Usages
View Set Composition View Set Composition
Navigation Navigation

Element Referenced Element Copied automatically

© SAP 2009 / Page 27

The Component Enhancement Concepts bases on and leverages the fully object
oriented programming model of the UI Framework

The build in Wizards work on inheritance concepts, which derive SAP Standard Classes to
Customer Namespace classes in case of redefinitions are required.

In the first step, using the Component Enhancement Concept the system automatically
creates:
„ a BSP application for the enhancement elements (runtime repository, derived controllers
etc.)
„ copies the runtime repository
„ stores component replacement information (which customer component replaces the
SAP Standard component at runtime).

After a customer component has been created using the Component Enhancement
Concept, all SAP Standard views and controllers are still used and remain
unchanged, as those are referenced within the new component. Therefore these are
displayed in the CRM UI Workbench within the new component in gray color. Only the
runtime repository is copied from the SAP Standard component, which should be enhanced
(see slide)

27
 Component Enhancement

SAP Comp. Controller Customer Comp. Controller

Component Component
Context Context
Window Main Window Main
View 1 View 1

View 2 View 2

View 3 View 3

Runtime Repository Runtime Repository

Component Usages Component Usages
View Set Composition View Set Composition
Navigation Navigation

Element Referenced Element Copied automatically Element Inherited if required

© SAP 2009 / Page 28

In a second step views and/or controllers can be enhanced/changed via the build in
Wizard in the CRM UI Workbench.

In case a view or controller is required to be adjusted/changed, the wizards automatically

take care about the needed inheritance logic to stay modification free (in a customer
system)

The wizards support:

„ create controller and view
„ derive controller and context classes
„ maintain controller replacement information

When a view and/or controller is adjusted/changed using the build in Wizards, e.g
redefining a method, this will not be overwritten with changes done by SAP for exactly
this redefined method. All other changes by SAP to exactly this view and/or controller will
automatically be inherited to the customer own view/controller.

All other changes of the referenced SAP Standard Component to existing views or
controllers, which have not been changed/enhanced will automatically be part of the
customer component.

Via this concept the system is upgrade secure.

28
 Application Enhancement Tool – SAP EHP1 for
SAP CRM7.0 Custom Fields and Tables*

Supported Features

„ Create custom fields and tables* that

complement existing applications and
match best your specific business
needs
„ Modify and regenerate newly created
fields and tables*
„ Provide translations in the system
supported languages
„ Extend the supported external
interfaces - for example Mobile, R/3,
BW and OLTP Reporting
„ Easily reuse custom fields and tables*
in applications that share common
extension places
„ Generate a form or table view based on
the table’s cardinality with respect to the
extended object (1:1 or 1:N)*

© SAP 2009 / Page 29 * New in EHP1

29
 Rapid Applications – SAP EHP1 for SAP CRM7.0
Screenshot: Create an Application From a DB Table

Supported Features

„ Create Rapid Applications from

DB Tables
„ Create Rapid Applications from
Web Services
„ Embed Rapid Applications into
existing Applications
„ Define mapping between Rapid
Applications and exiting
applications
„ Define default values for use in
Rapid Applications (e.g. to pass
license keys to a web service)
„ Display embedded Rapid
Application as a form or table
based assignment block

© SAP 2009 / Page 30 New in EHP1

30
 Content

1. General Overview and Concepts

2. Presentation Layer
3. Business Object & Generic Interaction Layer
4. Tools
5. Customer Enhancements
6. UI Check Tools

© SAP 2009 / Page 31

31
 UI Framework Check Tools – SAP EHP1 for
SAP CRM7.0 Objectives of the Presentation

Why do UI Framework Check Tools

matter for CRM customers?

„ Ensure consistency of customer

enhancements during development and
after upgrades

„ Facilitate maintenance of customizing

and configuration related to UI

„ Understand and resolve differences due

to updates between SAP standard and
customer enhancements

„ Safeguard quality of custom-tailored

solutions across patches, service packs
and releases
© SAP 2009 / Page 32

32
 UI Framework Check Tools – SAP EHP1 for
SAP CRM7.0 Key Features
General Functions
„ Fine-granular or high-level
definition of what to check
„ Check results are
persisted as application log
„ Check results can be
displayed grouped or as
list
„ Navigation from check
result to location of issue
„ Check tool can be run
scheduled in batch-mode
© SAP 2009 / Page 33
Safeguards
„ Consistency of views
enhanced by customers
„ Consistency of design layer
definitions
„ Consistency of UI
configurations
„ Consistency of
personalization data
„ Automatic adjustments of
personalization data
„ Consistency of runtime
repositories
33
Integration
„ Direct access to checks and
runtime repository
comparison within UI
component workbench
„ Transfer issue-location
parameters with navigation
„ Execution checks and
runtime repository
comparison via IMG after
upgrades and/or corrections
„ Export of check results to
Excel
* New in EHP1
 UI Framework Check Tools – SAP EHP1 for
SAP CRM7.0 Key Benefits

„ Enhance Applications in CRM

Component Workbench
Flexibility „ Apply SAP Corrections, Support
Packages and Upgrades

„ Analyze & Reestablish Consistency with

Safeguarding UI Framework Check Tools

„ Increase Productivity by Detecting &

Resolving actual Issues, as well as,
Stability potential Issues in your Custom Solution

„ Gain Stability from Technical Consistency

© SAP 2009 / Page 34

34
 Check Tools – SAP EHP1 for SAP CRM7.0
Access via IMG or Component Workbench

*
*

© SAP 2009 / Page 35 * New in EHP1

35
 Check Tools – SAP EHP1 for SAP CRM7.0
Parameters Describing What to Check

© SAP 2009 / Page 36 New in EHP1

36
 Check Tools – SAP EHP1 for SAP CRM7.0
Check Result Grouped by Type, Component, View

© SAP 2009 / Page 37 New in EHP1

37
 Check Tools – SAP EHP1 for SAP CRM7.0
Check Result List

© SAP 2009 / Page 38 New in EHP1

38
 Check Tools – SAP EHP1 for SAP CRM7.0
Runtime Repository Comparison

© SAP 2009 / Page 39 * New in EHP1

39
 Further Information

„ SAP CRM - Roll-Out Map

https://portal.wdf.sap.corp/go/crm-rollout-map

„ SAP CRM - Ramp-Up Knowledge Transfer (RKT)

http://service.sap.com/rkt-crm

„ SAP CRM – Demo Portal

http://crmportal.wdf.sap.corp:1080

„ SAP CRM – WiKi

https://wiki.wdf.sap.corp/display/SAPCRMHub/Home

„ SAP CRM - Help Portal

http://help.sap.com/crm

„ SAP Public Web

http://www.sap.com/crm

© SAP 2009 / Page 40

40
 Copyright 2009 SAP AG
All Rights Reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein
may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries,
eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+,
POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex,
MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other
countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos
are trademarks or registered trademarks of SAP AG in Germany and other countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and
services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries.
Business Objects is an SAP company.
All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only.
National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only,
without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group
products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed
as constituting an additional warrant.

© SAP 2009 / Page 41

41
Title of the Presentation
This is the Subtitle

Department, Board Area or Team

Date

42
 Agenda
e
p ict ur
ra e
p l e fo der slid
sam e divi
in th

1. Divider headline
1.1. Subdivider headline
1.2. Subdivider headline
2. Divider headline
2.1. Subdivider headline
2.2. Subdivider headline
3. Divider headline
3.1. Subdivider headline
3.2. Subdivider headline
4. Divider headline
4.1. Subdivider headline
4.2. Subdivider headline

© SAP 2009 / Page 43

43
 Agenda

1. Divider headline
1.1. Subdivider headline
1.2. Subdivider headline
2. Divider headline
2.1. Subdivider headline
2.2. Subdivider headline
3. Divider headline
3.1. Subdivider headline
3.2. Subdivider headline
4. Divider headline
4.1. Subdivider headline
4.2. Subdivider headline

© SAP 2009 / Page 44

44
 Title

First level
„ Second level
„ Third level
– Fourth level
– Fifth level

© SAP 2009 / Page 45

45
 Thank you!

© SAP 2009 / Page 46

46
 Grid

© SAP 2009 / Page 47

47
 Definition and Halftone Values of Colors

SAP Blue SAP Gold SAP Light Gray SAP Gray SAP Dark Gray
Primary color palette
RGB 4/53/123 RGB 240/171/0 RGB 204/204/204 RGB 153/153/153 RGB 102/102/102
100%

Dove Petrol Warm Green Warm Red Violet/Mauve

RGB 68/105/125 RGB 21/101/112 RGB 85/118/48 RGB 119/74/57 RGB 100/68/89 Secondary color palette
100%

RGB 96/127/143 RGB 98/146/147 RGB 110/138/79 RGB 140/101/87 RGB 123/96/114 85%

RGB 125/150/164 RGB 127/166/167 RGB 136/160/111 RGB 161/129/118 RGB 147/125/139 70%

RGB 152/173/183 RGB 154/185/185 RGB 162/180/141 RGB 181/156/147 RGB 170/152/164 55%

RGB 180/195/203 RGB 181/204/204 RGB 187/200/172 RGB 201/183/176 RGB 193/180/189 40%

Cool Green Ocher Cool Red Warning Red

RGB 73/108/96 RGB 129/110/44 RGB 132/76/84 Tertiary color palette RGB 158/48/57
100%

RGB 101/129/120 RGB 148/132/75 RGB 150/103/110 85%

RGB 129/152/144 RGB 167/154/108 RGB 169/130/136 70%

RGB 156/174/168 RGB 186/176/139 RGB 188/157/162 55%

RGB 183/196/191 RGB 205/197/171 RGB 206/183/187 40%

© SAP 2009 / Page 48

48
 Copyright 2009 SAP AG
All Rights Reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein
may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries,
eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+,
POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex,
MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other
countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos
are trademarks or registered trademarks of SAP AG in Germany and other countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and
services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries.
Business Objects is an SAP company.
All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only.
National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only,
without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group
products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed
as constituting an additional warrant.

© SAP 2009 / Page 49

49