SAP Customer Relationship Management (CRM) 7.

0 Boot camp
Copyright Copyright 2007 Accenture 20"0 Accenture All Rights All rights Reserved. reserved. Accenture, Accenture, its logo, its logo, and and High High Performance Performance elivered elivered are trademar!s are trademar!s of Accenture. of Accenture.

Agenda
# Course $pening # %AP CR& $vervie'
( %AP CR& )eneral *nformation and Highlights ( %AP CR& 7.0 +ey Capa,ilities ( %AP CR& 7.0 -nhancements ( %AP CR& 7.0 .asic %creen -lements

Getting to Kno

!ach "ther

# /et0s ma!e an introduction round and give the follo'ing information to the other participants1
( 2our name ( 2our assignment 'ithin the Accenture organi3ation ( 2our level ( 2our office ( A short overvie' of the topics and pro4ects you have 'or!ed on ( 5hy you are here in the course

#our !$pectation
# Please 'rite do'n your e7pectation of the course and put the results on the ,oard.

"%erall Course "&'ecti%es

# At the end of the course, participants 'ill ,e a,le to1 ( -7plain the historic development of %AP CR& and the future perspective. ( *dentify the scope of %AP CR& and ,usiness functions it supports. ( escri,e %AP CR& Architecture. ( *mplement %AP CR&.

Agenda
# Course $pening # %AP CR& $vervie'
( %AP CR& )eneral *nformation and Highlights ( %AP CR& 7.0 +ey Capa,ilities ( %AP CR& 7.0 -nhancements ( %AP CR& 7.0 .asic %creen -lements

(e)initions
(e)inition SAP CRM
SAP Customer Relationship (SAP CRM) is an application hich pro%ides &est*in*class )unctionalit+ )or mar,eting- sales- and ser%ice. .y supporting customer;facing ,usiness processes across multiple interaction channels, %AP CR& ena&les organi.ations to )ocus on strategies )or customer*dri%en gro th and to di))erentiate themsel%es in the mar,et ,y providing a superior customer e7perience.< %ource1 %AP %ervice mar!etplace, 200=

SAP CRM General /n)ormation and 0ighlights * Bene)its and Ad%antages

# %AP CR& .enefits for $rgani3ations
( Competitive Advantages ( *ncreased Revenue ( Potential to /o'er Costs

# %AP CR& .enefits for Customers

( .etter and Personali3ed %ervice ( Consistent interactions across all channels and touch points

# $ther Advantages
( ?irst;class functions for mar!eting, sales, and service ( -7tensive analysis as a ,asis for decision ma!ing ( %eamless integration 'ith %AP .usiness %uite solutions and other applications
>

0istor+ o) SAP CRM

@he first version of %AP CR& 'as launched in 1222. # 3004 SAP CRM (3004) 4.0, targets such !ey cross;industry ,usiness capa,ilities as service management, mar!eting resource management and mo,ile sales for handhelds. Po'ered ,y the %AP Aet5eaver platform, the ne' system features dash,oard;li!e em,edded analytics. # SAP CRM (3007) 5.0, the B* is much improved compared to CR& 200:s and uses 5e, 2.0 principles 'here users can drag sections of the screen around to personali3e them for themselves. # 3006 SAP CRM 7.0, increased Personali3ation and improved B* @ools. Ae' functions li!e /oyalty &anagement and improved @P&.

SAP Business Suite

# @he SAP Business Suite is a &undle o) &usiness applications that provides integration of information and processes, colla,oration, industry;specific functionality, and scala,ility. %AP .usiness %uite is ,ased on %APCs technology platform called Aet5eaver. # SAP Business Suite 7 so)t are delivers a synchroni3ed release schedule for all applications and components across the entire suite.
%AP

"0

SAP Business Suite (cont.)

# @he %AP .usiness %uite 7 contains the ne'est releases of1
( ( ( ( ( %AP -RP SAP Customer Relationship Management %AP Product /ifecycle &anagement %AP %upplier Relationship &anagement %AP %upply Chain &anagement

%AP

""

!nhancement %s. 7pgrade

8SAP enhancement pac,ages deli%er product )le$i&ilit+ and technolog+ ad%ancement at the same time. Customers no longer ha%e to ait 39 or :5 months )or critical )unctionalit+.;
# %AP enhancement pac!ages are optional pac!ages that deliver ne' or improved ,usiness functions that you can deploy selectively, 'hile the core applications remain sta,le. uring an upgrade all soft'are components are updated. # %AP delivers minimally disruptive innovation 'ith enhancement pac!ages. # ?or all the core applications of %AP .usiness %uite 7 soft'are %AP enhancement pac!age " is planned for the second Duarter of 20"0.
"2

SAP CRM (7.0) A%aila&ilit+

# %AP CR& E7.0F Availa,ility and &aintenance

2ou can find this information of Product Availi,ility &atri7 on the %AP %upport Portal1 https1GG'e,smp"0=.sap;ag.deGpam.
"6

Agenda
# Course $pening # %AP CR& $vervie'
( %AP CR& )eneral *nformation and Highlights ( %AP CR& 7.0 +ey Capa,ilities ( %AP CR& 7.0 -nhancements ( %AP CR& 7.0 .asic %creen -lements

"8

SAP CRM "%er%ie < Ke+ =unctionalities

# *n daily ,usiness various departments li!e &ar!eting, %ales and %ervice interact directly and regularly 'ith customers. # ?rom a soft'are point of vie' these employees need to have support to fulfill their daily tas!s in an efficient and customer; oriented 'ay.

%AP

"9 "9

SAP CRM Solution Map

/in! to the %AP %olution Composer

%AP

":

Ke+ Processes and Bene)its in Mar,eting

Ke+ processes
#&ar!eting Resource &anagement #Customer %egmentation and /ist &anagement #Campaign &anagement #Real;@ime $ffer &anagement #/ead &anagement #/oyalty &anagement #&ar!eting Planning and analytics

Ma'or &ene)its
#%elect target groups #&onitor mar!eting costs #Bse mar!eting analytics as a ,asis for ma!ing decisions #$,serve mar!ets and competitors #*dentify customer preferences

%AP

"7

SAP CRM Ke+ Mar,eting Capa&ilities < Business >alue

# &anage and coordinate mar!eting activities glo,ally, regionally, and locally # &ulti;channel support to ensure one face to the customer # @ight integration 'ith financials, accounting, and supply chain # /everage .usiness *ntelligence and CR& analytical capa,ilities for improved visi,ility and insight into mar!eting operations # .road functional spectrum # &odular, scenario;,ased implementation to ensure fast return on investment
">

Ke+ Processes and Bene)its in Sales

Ke+ processes
#Customer order management, Duotations and contracts #Account and contact management #$pportunity management and pipeline analysis #Activity management #Commissions and incentives #%ales planning and analytics

Ma'or &ene)its
#Control %ales Processes resulting in an increase in revenue #*ncrease up;selling and cross;selling opportunities #Recogni3e profita,ility of each and every customer #Reduce sales costs #Create accurate, real time forecasts

%AP

"=

SAP CRM Ke+ Sales Capa&ilities * Business >alue

# # # # # # # # Closed;loop processes ?aster response time ?ocused sales force through Dualified leads .etter service through real;time response on product availa,ility *ncreased time for selling %ales force concentrated on profita,le customers $ptimi3ed mi7 of channels @eam;selling
20

SAP CRM Ke+ Sales Capa&ilities * Sales C+cle (Closed*?oop CRM)

Customer retention Lead generation and qualification

Customer service

Sales Cycle

Billing

1. Agreement Logistics execution

%AP

2"

Ke+ Processes and Bene)its in Ser%ice

Ke+ processes
#%ervice reDuest, service order, and contract administration #*nstalled ,ase management #Customer %ervice and %upport EComplaint and Case &anagementF #Returns and epot Repair #5arranty and Claims &anagement #%ervice planning #Analytics

Ma'or &ene)its
#Achieve higher customer satisfaction through prompt and efficient service #Reduce service costs #Provide relia,le service around the cloc! #Achieve transparency of ,oth service resources and service costs

%AP

22

SAP CRM Ke+ Ser%ice Capa&ilities < Business >alue

# Accessi,ility, Hisi,ility, and *ntegration1
( Convenient multi;channel access ,oth for customers and service employees ( Complete visi,ility of relevant customer and product history supports service employees and ena,les a real time response ( *ntegration 'ith ,ac!;office systems such as %AP RG6 Customers, %AP RG6 Controlling, and %AP RG6 Human Resources
26

Ke+ Processes and Bene)its in @e& Channel

Ke+ processes
#-;&ar!eting #-;Commerce #-;%ervice #5e, Channel Analytics

Ma'or &ene)its
#Personali3e each customer0s ,uying e7perience #Provide convenient, easy;to;use, interactive selling and self;service #-na,le end;to;end, order;to;cash processes #*ncorporate partners into your e; commerce strategy #%ignificantly reduce cost of sales

%AP

28

SAP CRM Ke+ !*Commerce Capa&ilities < !$ample )or Building Bloc,s

Bro ser

Portal

@e& Catalog Guided Selling ?i%e Customer Support

Search !ngine Product Con)iguration Complaints and Returns

Personalisation "rder A Buote Management Kno ledge Management

Shopping Bas,et "nline Billing and Pa+ment iBase Management

Pricing !ngine @e& Auctions !* Anal+tics

Catalog Management
%AP

Mar,eting Management

Business Partner

"rder Management

Contract Management

Ser%ice Management
29

Ke+ Processes and Bene)its in /nteraction Center

Ke+ processes
#&ar!eting #%ales #Customer %ervice #%hared %ervice Center #*nteraction Center &anagement

Ma'or &ene)its
#-asy;to;use agent productivity tools #Portal;,ased access for interaction centre administration, management, and reporting #*ntegrate 'ith interaction centre infrastructure e.g. systems, computer telephony, e;mail, and 5e, servers #Achieve a higher R$*

%AP

2:

SAP CRM Ke+ /nteraction Center Capa&ilities * Business >alue

# *nteraction Centre uniDuely allo's to ma!e every interaction a successful and valua,le one for the customer.
# =or companies # =or the Customer ( *ncrease company e7posure ( *ncrease customer and accessi,ility convenience through additional interaction channels ( /o'er the cost of customer ( *mprove interaction consistency treatment and ease of doing ,usiness ( Provide consistent information ( *mprove service levels and across all touch points ma7imi3e customer e7perience ( *ncrease revenue 'ith cross; ( -fficiently identify and address and up;selling customer needs ( -na,le valua,le and lasting customer relationships
27

Ke+ Processes and Bene)its in Partner Channel Management

Ke+ processes
#Partner &anagement #Channel &ar!eting #Channel %ales #Partner $rder &anagement #Channel %ervice #Partner and Channel Analytics

Ma'or &ene)its
#.oost Revenues #Reduce Costs #*ncrease Profits #*ncrease Customer %atisfaction #-mpo'er Partners

%AP

2>

SAP CRM Ke+ Partner Channel Management Capa&ilities * "%er%ie

# %AP CR& provides companies 'ith a platform to manage channel partner relationships and ena,le partners to sell more effectively ( resulting in a more profita,le indirect channel.

Channel Manager

Channel Partner

Customer

2=

Ke+ Processes and Bene)its in Business Communication Management

Ke+ processes
#?ully integrated multi;channel call center communication #&onitoring and management of communications in real time through online analytics #*nteractive voice response E*HRF option

Ma'or &ene)its
#Centrali3e geographically spread communications for #*n,ound and $ut,ound contacts #$ut,ound &ar!eting Campaigns #&anage Communications across the company

%AP

60

SAP CRM Ke+ Mo&ile Capa&ilities * ?aptops

6"

Ke+ Processes and Bene)its o) CRM Anal+tics

Ke+ processes
#*ntegrated suite of analytical and planning solutions

Ma'or &ene)its
#&easurement, prediction, planning and optimi3ation of customer relationships

62

Ke+ Processes and Bene)its o) CRM /ndustr+*speci)ic Solutions

Ke+ processes
#*ncludes all general CR& functionalities, .B@ #%upports especially several industry; specific CR& processes

Ma'or &ene)its
#Addresses uniDue needs and complete, end;to;end reDuirements of all ma4or industries

!$amplesC

66

Agenda
# Course $pening # %AP CR& $vervie'
( %AP CR& )eneral *nformation and Highlights ( %AP CR& 7.0 +ey Capa,ilities ( %AP CR& 7.0 -nhancements ( %AP CR& 7.0 .asic %creen -lements

68

Changes Since SAP CRM 4.0

A real ,rea!through in CR& 200:s release1 a completely 'e,;,ased user interface, 'hich replaces the %AP )B* in all system management functions. @his technology gives strong competitive potential to %AP CR& as it1 # *mproves usa,ility compared to previous %AP CR& versions # Provides an interface 'ith %$A Eintegration 'ith %AP ( e.g. 5e, %ervices ( and non %AP applicationF

69

0ighlights o) SAP CRM 7.0 < De @e& 7/

6:

De =eatures o) SAP CRM 7.0

%AP

67

Main Strengths o) De SAP CRM 7.0

Release

# 7sa&ilit+C &ainly considering learn a,ility and understanda,ility # !))icienc+C Reduced num,er of clic!s needed to access relevant functions impact the timel+ &eha%ior # Maintaina&ilit+C &ainly focusing on Changea&ilit+ of the application related to ne' 5e, B* customi3ing # Porta&ilit+C *n terms of Adapta&ilit+ typical of 'e, ,ased user interfaces

6>

0ighlights o) SAP CRM 7.0 * Eechnical

/ntegrated !nterprise Search # %imple search B* # Cross;o,4ects and cross;system searches # *mproved performance (ash&oards and /nteracti%e Reporting # %upport visual B* and interactive analysis

6=

Agenda
# Course $pening # %AP CR& $vervie'
( %AP CR& )eneral *nformation and Highlights ( %AP CR& 7.0 +ey Capa,ilities ( %AP CR& 7.0 -nhancements ( %AP CR& 7.0 .asic %creen -lements

80

0ome Page
@he 0ome Page is the starting point for all user in daily ,usiness. *t contains the most important personal in)ormation and access to the most )reFuentl+ used tools.
The Homepage

@he Homepage provides1 # A Duic! $vervie' of the Current ay # Hyperlin!s to more det. information # Predefined content for1 ( &y Appointments today ( &y @as!s today ( 5or!flo' @as!s ( Reports and Applications ( Alerts @he Homepage *s configured per role1 # Availa,le content can ,e personali3ed ,y the user # Content can ,e adapted
8"

SAP CRM @e& 7/ Screen Structure

@he Ae' 5e, Client screen is structured into 6 different areas1 the 0eader Area EAFI the Da%igation Area E.F and the @or, Area ECF.
The Screen structure Header Area (A)

# Position of header and navigation area E/;%hapeF are fi7ed, even if Aavigation .ar can ,e hidden # /;shape Contains1 ( %ystem /in!s ( %aved %earches ( 5or! area title ( History ,ac! and for'ard ( Aavigation .ar # 5or! Area contents are dynamic depending on selected contents on navigation area
82

Nav. Bar Area (B)

L-Shape

Work Area (c)

0eader Area
.esides displaying the 'or! title area and the Header Area of the 5e, B* provides system lin!s and search functionalities.

aF ,F cF dF
Header Area

aF ,F cF dF

%ystem /in!s %aved %earches ?or'ard J .ac! Aavigation &essages J @ools

86

Da%igation Bar
@he Aavigation .ar is divided into t'o areas1 Aavigation *tems and Kuic! lin!s aF
Navigation Bar

aF

Aavigation items the items you can select and navigate to Ecalendar, email in,o7,LF.

,F

,F Create Kuic! lin!s you can determine freDuently used items as MDuic! lin!s.< cF Recent *tems lists the last vie'ed ,usiness o,4ects

cF
88

@or, Center
-very first level menu EAccounts, $rders, ActivitiesL.F item has an individual 'or! center page. *t contains a set of shortcuts and access to all 'or! center;related components.
The Work Center page

# *s opened &+ choosing the )irst* le%el na%igation entry directly, 'ithout selecting a second;level entry # *ncludes important content regarding the current area1 ( %earch /in!s ( Create /in!s ( Reports # Content of the page could ,e customi.ed ithout de%elopment acti%ities

89

@or, Area
@he 5or! Area can contains different page types Eentry pages, content pages, support pagesF.

Work Area

# # #

-ntry pages Content pages %upport pages

8:

@or, ?ist
@he 'or! list provides a complete overvie' of information pushed to the user. *t is divided in to alerts and 'or!flo' tas!s.
The Work List page

# Contains information a,out alerts and 'or!flo' tas!s pushed to the users # %everal predefined alerts and 'or!flo' are delivered 'ith %AP CR& ECampaign, approval 'or!flo', accept lead 'or!flo', lost opportunity alert, and so onF # 5ithin a role, smaller content areas for alerts and 'or!flo's can ,e em,edded directly in the home page

87

"%er%ie

Page
The Overview page

@he "%er%ie Page provides a summary of all important information regarding a single o,4ect Ne.g. Account, Contact, Activity, %ales $rder, %ervice $rderL.O in displa+ mode. # Consist of a header ,loc! 'ith the core information and a set of su,ordinate assignment ,loc!s containing related information # @he information in assignment ,loc!s can ,e displayed 'ith1 ( ?orm Hie's ( @a,les ( Hierarchy trees # Contains the hyperlin!s to navigate to other related o,4ects

8>

Ad%anced Search
@he advanced search provide the user 'ith comprehensi%e, )le$i&le and eas+ to understand search capa&ilities individually )or e%er+ &usiness o&'ect
The Search page

# Allo's for )le$i&le creation of search model ,y choosing a 'ide range of search criteria # !as+*to*understand operator;,ased search logic # Provide a search result list for getting a Duic! overvie' and easy navigation to detailed information of single o,4ects # $ffer options to create- delete, or perform a mass update EoptionallyF of information directly from the search result list # %aving Search models # $ffers !$port to MS !$cel
8=

Agenda
# %AP CR& 5e, B*
( Architecture ( B* Concept and B* Component Concept ( Aavigation .ar and .usiness Roles ( B* Configuration ( Personali3ation ( Additional ?eatures ( BOL & GenIL ( Knowledge Check

# KJA and ay " 5rap;up

90

BSP ArchitectureC Basics

# @he CR& 5e,Client is ,uilt to run 'ithin a 5e, .ro'ser # @herefore, on the client side it is only necessary to install a 5e, .ro'ser. An %AP )raphical Bser *nterface E%AP )B*F is not necessary # All data displayed in the 5e, ,ro'ser is sent ,y hyperte7t @ransfer Protocol EH@@PF from the %AP 5e, Application %erver to the client Ethe 5e, .ro'serF # @he user interface EB*F is ,ased on .usiness %erver Page E.%PF technology, 'hich is a ,lend of A.AP code and .%P e7tensions

%AP

9"

CRM @e&7/ and SAP @e& Application Ser%er

# @he %AP 5e, Application %erver contains t'o run time environments1 A.AP EAdvanced .usiness Application ProgrammingF and P2-- EPava 2 -nterprise -ditionF # @he user interface EB*F is ,ased on .usiness %erver Page E.%PF technology # .%Ps are a ,lend of A.AP code and .%P e7tensions # .%P e7tensions provide hyperte7t &ar!up /anguage .usiness EH@&/.F tags for ,uilding a consistent page layout throughout all applications # H@&/. tags include comple7 and e7tensi,le capa,ilities 'hich are much more po'erful than standard H@&/ tags
%AP

92

@e&Application Ser%erC /ntegration Potential

# @he H@@P services of the *nternet Communication &anager E*C&F communicate ,et'een the 5e, .ro'ser and the .%P runtime # *t is responsi,le for caching and 'or!s 'ith a great variety of protocols, such as %imple $,4ect Access Protocol E%$APF, H@@PE%F, and %imple &ail @ransfer Protocol E%&@PF # A set of %AP 5e, %ervices has to ,e ena,led in order to allo' communication ,et'een 5e,Application %erver and .%P

%AP

96

CRM @e&Client Architecture (1 o) :)

@he CR& 5e,Client is ,ased on a multi;layer architecture on the server side1 #Presentation ?a+er @he presentation layer of the CR& 5e,Client is ,ased on .usiness %erver Pages E.%PsF, 'hich are sho'n as dynamic H@&/ pages in the 5e, ,ro'ser.

98

CRM @e&Client Architecture (3 o) :)

# Business ?a+er (B"? and Gen/?) Holds the data structure of ,usiness o,4ects during a CR& 5e,Client session, such as ,usiness partners or products and handles transactions. *t consists of t'o layers1
Business o&'ect la+er (B"?)C @he ,usiness o,4ect layer saves the ,usiness o,4ect data, e.g. sales orders, at runtime of the %AP CR& session. @his layer guarantees the separation of the CR& 5e,Client B* and the underlying ,usiness logic. Generic interaction la+er (gen/?)C @he generic interaction layer handles the data transfer from the ,usiness o,4ect layer to the application programming interfaces EAP*sF of the underlying ,usiness engine. *t is the connection ,et'een the ,usiness o,4ect layer and the underlying ,usiness engine.
99

CRM @e&Client Architecture (: o) :)

# Business !ngine @he layers are strictly separated in order to allo' connections ,et'een the B* layer and any .usiness Application Ee.g. -RP o,4ects such as -mployees or %ales $rdersF

9:

CRM Architecture Representation

@he graphic ,elo' e7plains ho' the technical components of the CR& 5e,Client 'or! together in the architecture concept.

Corresponding system tools:

BSP_ !_C"P B Component Workbench #$%&L_"'!$L_B(' ( to explore the GenIL model

S$

#$%&L_B'L_B(' S$( to explore Business Objects and relations S$11) S$1* explore data objects and databases
%AP

97

7/ ConceptC Model >ie Controller

@he CR& 5e,Client .%P is ,ased on the &odel Hie' Controller E&HCF paradigm 'hich is a 'idely accepted design pattern for developing o,4ect oriented user interfaces EB*F. *t provides an effective 'ay of relating B* layouts to an underlying data model.
Presentation ?a+er Controller
ReFuest Bser input
(ri%es /nteraction ?ogic

CRM @e&Client

Model
set
?in,s to underl+ing Structure

>ie
Response ata output
0andles >isual "utput

get

ata flo' Control flo'

Business ?a+ers Business !ngine

(B"? and Gen/?)

((ata&ase ta&les) 9>

7/ ConceptC Model >ie Controller (cont.)

Presentation ?a+er
ReFuest

Controller
(ri%es /nteraction ?ogic set

Model
?in,s to underl+ing Structure get

>ie
Response 0andles >isual "utput

9=

7ser /nteraction
@he figure ,elo' sho's ho' the vie', controller, and model ma!e up the B* layer of the CR& 5e,Client.
CR& 5e,Client
Create Ser%ice Eic,et user input data output

1
ReFuest

Presentation /ayer E.%PF

Controller >ie

". Bser inserts a reDuest Ee.g. Create %ervice @ic!etF 2. Hie' Controller is initiali3ed and reDuest is passed 6. Controller calls underlying data model E.usiness $,4ectsF 8. ata in model is provided ,y .usiness -ngine Edata,aseF and structured in .usiness /ayer 9. Correct data is availa,le in the vie'I 'e, page structure is ,uilt

Model

Ser%ice Eic,et created

Response

.usiness /ayer

B"?C Business "&'ect ?a+er

data structures o) the B"? holding &usiness o&'ects )or the /C @e&Client session

Gen/?C Generic /nteraction ?a+er

Gen/? Model and /mplementation Classes connecting B"? to AP/s

9
CRM AP/ AP/ AP/ /S*7

.usiness -ngine
(m+ SAP CRM- m+SAP !RP- /S*7- etc.)

:. Response is sent to Bser *nterface

:0

General ConceptsC Comparison M>C Architecture G CRM S+stem

@he previous slides e7plained a,stractly ho' the technical components of the CR& 5e,Client 'or! together in the architecture concept. .ut1 ho' are this concepts technically implemented in the CR& applicationQ @he &HC model is implemented ,y means of B* Components. A component is an A.AP $,4ect $riented class 'hich implements the component interface. M>C Architecture CRM S#SE!M

%AP

:"

M>C Architecture in CRM S+stem

@he components and their corresponding controllers, vie's and conte7ts can ,e accessed via the Component @or,&ench. @his transaction represents the &HC architecture and allo's access to the classes and methods of its elements.

ControllerC Class ER*&P/F ModelC Conte7t and Conte7t Aodes ERC@S@F ControllerC &ethods for -vent Handling and Aavigation >ie C /ayout efinition ERhtmF
:2

Component @or,&enchC Component Structure Bro ser

!$ampleC >ie Structure o) the %ie Account (etails. @he model of CR& 5e,Client .%Ps consists of conte7ts and conte7t nodes that lin! the fields of a .%P vie' to the underlying .$/. .oth conte7t and conte7t nodes are implemented as A.AP classes.
# Conte$tC @he Conte7t class 'ith the suffi7 C@S@ # Conte$t DodeC @he Conte7t Aode 'ith suffi7 CA77. Conte7t nodes represent data in the structure of .usiness $,4ects. # Attri&utesC -ach field displayed at the vie' is lin!ed to an attri,ute of a conte7t node.
:6

Accessing the Component @or,&ench

@o 'or! on B* Components %AP provides the so called BSP Component @or,&ench. @he .%P Component 5or!,ench is the central frame'or! modeling tool, and provides access to a variety of functions. *t can ,e accessed via /MG or 'ith transaction code BSPH@(HCMP@B *t offers the follo'ing main access points1 #@he Component Structure Bro ser provides access to the o,4ects of a B* Component #@he B"? Model Bro ser sho's the ,usiness o,4ect layer E.$/F model of a B* component. #@he Runtime Repositor+ !ditor sho's the runtime repository of a B* component. *n the runtime repository, you can see and edit the vie' set composition E'hich vie's are assigned to a vie' area and 'hich vie' areas ,elong to a vie' setF.

:8

S+stem (emo 1C Component @or,&ench

:9

Component @or,&enchC Structure o) 7/ Component

A component is an A.AP $,4ect $riented class, 'hich implements the component interface. 5ith the ne' CR& B* ?rame'or! a ne' concept is introduced as valid for all Applications 'hich are ,ased on this ?rame'or!.
ComponentC
# .undle of 'indo's, vie' sets, vie's and custom controllers # %elf;contained reusa,le unit Eo'n runtime repository, interfaces to outsideF # Can have multiple instances at runtime # @echnically mapped to .%P application
/P

Structur e
Component Controller Custom Controller

5indo'

/P

>ie >ie

"P

>ie

>ie Sets

>ie Sets Sets >ie

"P

Component ::

Component @or,&enchC Component Structure Bro ser

# *nventory of Components # Creation of Component Controller, 5indo's, Custom Controllers, and Hie's is supported ,y 'i3ards # -ach component consists of several runtime o,4ects # &ost important ones are 5indo's, Custom Controllers and Hie's @indo sC Contains all Hie's that should ,e displayed. Custom ControllersC $rgani3es cross;vie' data transfer. Reduces retrieval of data from the .$/. >ie sC &ain programming and B* Configuration o,4ects.
:7

Component @or,&enchC B"? Model Bro ser

@he .$/ &odel .ro'ser sho's the ,usiness o,4ect layer E.$/F model of a B* component. @his .$/ model is assigned to the B* component via the runtime repository. @he .$/ &odel .ro'ser is availa,le only if this assignment e7ists.

# # # # # # #

Root $,4ects Access $,4ects ependent $,4ects %earch $,4ects %earch Result $,4ects Hie' $,4ects ynamic %earch $,4ects

Business "&'ect )roup of unstructured attri,utes, 'hich characteri3e a .usiness o,4ect Ee.g. Accounts, -mployees, $rdersI ActivitiesLF. .$ can ,e hierarchically aggregated in order to create an $,4ect &odel.
:>

Component @or,&enchC Runtime Repositor+

@he runtime repository editor of the component 'or!,ench is the tool 'hich displays and maintains the Runtime Repository for a Component. -ach Component consists of several design o,4ects consolidated in the Runtime Repository. ModelsC Assignment of the component set @indo sC Assignment of Hie's to 5indo's >ie SetsC Com,ination of Hie's to one %creen

Da%igational ?in,sC escription of Aavigation Component /nter)aceC *nterface of Component -lements to the $utside Component 7sagesC Bsages of EotherF Components
:=

Component @or,&enchC Runtime Repositor+ (cont.)

# -ach component has its o'n runtime repository file E'hich it means that any component can ,e autonomously e7ecutedF # *t acts li!e a catalogue containing vie's, vie'sets and the composition of vie's 'ithin vie'sets, navigational lin!s E'ith target and source vie'F and in,ound and out,ound plugs definitions # @echnically stored as .7ml file

70

Agenda
# %AP CR& 5e, B*
( Architecture ( B* Concept and B* Component Concept ( Aavigation .ar and .usiness Roles ( B* Configuration ( Personali3ation ( Additional ?eatures ( BOL & GenIL ( Knowledge Check

# KJA and ay " 5rap;up

7"

Da%igation Bar
Navigation Bar

# Allo's direct navigation to all entry pages # Provides t'o levels of navigation1 "st level navigation 2nd level navigation

72

Da%igation Bar and 7ser RolesC Da%igation Bar &+ 7ser Role
Business e!uirement

ifferentiation of User Menu according to user0s Business Role. %ystem functionalities availa,le to users can ,e selected depending on client0s organi3ational reDuirements and needs. ?or e7ample Aavigation .ar can differ ,et'een departments Emar!eting vs. salesF, or depend on positions in organi3ational chart Esales managers vs. agentsF.
Sample

ifferent Aavigation .ar menus ,et'een %ales Professionals and &ar!eting Professionals

Sales Pro)essional

Mar,eting Pro)essional
Tips & Tricks

-arly identification of reDuired roles to determine the different navigation ,ar menus. A limited num,er of navigation ,ar entries helps to avoid relevant maintenance effort.
76

Da%igation Bar and 7ser RolesC Role*GDa%igation Bar Customi.ingC Assignments

"rgani.ation Model
"rg. 7nit Position 7ser G Bus. Partner

Business Role
Da%igation Bar Pro)ile
#@or, Center Pages #@or, Center ?in, Groups #(irect Group ?in,s

EJC CRMCH7/HDB?/DKS

EJC PP"MAHCRM

Role Con)iguration SM:0C Ke+ CRM>H7/HC"D=/G P=CGI Role /( Eechnical Pro)ile ?a+out Pro)ile =unctional Pro)ile
RP?C)1 Profile )enerator 78

EJC P=CG

SM:0C CRM>H7/HPR"=/?!

Da%igation Bar and 7ser RolesC Role*GDa%igation Bar Customi.ingC Eerminolog+

"e#inition

@he Role;GAavigation .ar Customi3ing controls ,ased on .usiness Role ho' the Aavigation .ar is structured and 'hich lin!s are availa,le on the 5or! Center G Home G Report Pages and in the irect /in! )roup.
Terminolog$

79

S+stem (emo 3C Da%igation Bar and 7ser Roles

7:

Agenda
# %AP CR& 5e, B*
( Architecture ( Concept and B* Component Concept ( Aavigation .ar and .usiness Roles ( B* Configuration ( Personali3ation ( Additional ?eatures ( BOL & GenIL ( Knowledge Check

# KJA and ay " 5rap;up

77

7/ Con)iguration Eool
# @he B* Configuration @ool acts at the level of the vie's and the CR& B* 5e, Client. # *t ena,les advanced users to configure the layout of the vie' 'ithout handling and 'riting H@&/ code # *t ena,les the user to perform ,asic configuration activities. Presentation ?a+er Controller
ReFuest Bser input
(ri%es /nteraction ?ogic

CRM @e&Client

Model
set
?in,s to underl+ing Structure

>ie
Response ata output
0andles >isual "utput

get

Business ?a+ers Business !ngine

(B"? and Gen/?)

((ata&es ta&les) 7>

Access the 7/ Con)iguration Eool

.efore you start the configuration of a specific screen you need the technical name of the component 'hich contains the vie' and the technical name of the vie'1 Choose =3 in the CR& 5e,Client Application to get the technical information

2ou can access the B* Configuration @ool in %AP )B* and in the CR& 5e,Client B*. SAP G7/1 Hia the .%P Component 5or!,ench -nter the B* Configuration %tool via the Configuration ta, of the .%P Component 5or!,ench %elect the correct vie' of the component
7=

Access the 7/ Con)iguration Eool (cont.)

CRM @e&Client 7/C 1. Da%igation Bar1 Access the B* Configuration @ool via the Administration 'or! center Elogical lin!1 .%P; /C;HCF
-nter the component %elect the correct vie'

3. (irectl+ )rom the CRM ApplicationC

Configure Page T -nter B* Configuration @ool %ho' Configura,le Areas

PrereFuisiteC @he configuration mode has to ,e activated in the personal settings, other'ise the configure page icons are not availa,le

>0

7/ Con)iguration EoolC Con)iguration (i))erentiators

Sample

o not change the standard configuration ,ut copy it to an o'n configuration and modify that. Configuration can ,e stored according to differentiators, using the follo'ing parameters1

Role Con)iguration Ke+C /ayout Profile +ey contained in .usiness Role Component 7sageC Component 'ith an interface can ,e included in other components and therefore have different usage depending on component "&'ect and "&'ect Su&t+peC Application specific parameters Eallo's to create content type dependent configurationsF
Tips & Tricks

ifferent Configurations can ,e used to display the vie' according user specific parameters. -.g. dependent on the country 'here the system is used different address schemes E -uropean or B% schemeF are used.
>"

7/ Con)iguration EoolC Con)iguration o) >ie

Business e!uirement

Configure an e7isting vie' according customers reDuirements1 Add G remove G shift fields from field set, rename field la,els and set field to mandatory G display only.

1 3 9 : :

". 2. 6. 8.

Create ne' configuration %hift fields Change field properties Add G Remove fields
Tips & Tricks

@he configuration of a vie' can ,e influenced ,y the implementation of field getter methods. -.g. the type of a field Einput, chec!,o7,LF is defined in the properties getter method of the field and the property M isplay only< depends on the implementation of the input;readiness getter method as 'ell.

>2

!$ercise 1 Customi.e (etail Page

7nitC Customi.ing o) a @e& 7/ %ie . @opic1 Customi3e a standard etail page ,y using the B* Configuration @ool directly out of the 5e,B*. At the conclusion o) this e$ercise- +ou # Access the B* Configuration @ool # Customi3e a standard ill &e a&le toC

etail page in the 5e, B*.

>6

7/ Con)iguration
@o adapt the user interface of %AP CR& to customers ,usiness needs a ,undle of frame'or! tools is availa,le. @he figure ,elo' sho's the relationship ,et'een the reDuirements, the corresponding tools and the affected soft'are layer. ReFuirement
?a+out change- e.g. mo%e a )ield Add e$isting )ield to 7/ ?a+er 7/ Con)iguration Eool Business ?a+er (B"?) Add a ne custom )ield to the data model
Custom ?ield .usiness -ngine

Eool

So)t are ?a+er

Presentation ?a+er (BSP)

/nteraction ?a+er (gen/?) !as+ !nhancement @or,&ench (!!@B)

AP/

Application !nhancement Eool (A!E)

Business !ngine
@a,les

>8

!as+ !nhancement @or,&enchC "%er%ie

#Customer %pecific ?ields can ,e added to CR& 5e, Client B* ,y means of the -asy -nhancement 5or!,ench E--5.F. #$nce a field has ,een created, the B* configuration tool can ,e used to configure these fields. #&ain CR& $,4ects that can ,e enhanced 'ith the --5. are1 (.usiness Partners (.usiness Partner Relationships (.usiness @ransactions EActivities, %ales $rders etcLF (Account Planning (&ar!eting Planner

-nhancement through all layers

>9

!as+ !nhancement @or,&enchC 0o Eo !!@B

# epending on reDuirements, o,4ects that can ,e created, are split into t'o main groups1
( 5hen a single value has to ,e displayed, a )ield should ,e used. ( 5hen multiple values have to displayed for the same o&'ect, a ta,le should ,e used.

"&'ects to create

=ields %ingle valueG?lag ?ree *nput or ropdo'n /ist

Ea&les &ultiple values ?ree *nput or ropdo'n /ist Chec! ta,le to filter values

>:

!as+ !nhancement @or,&enchC !nhancement Process

=/!?(
Add ne' fields 'ith --5. CR& @a,les G AP*s are enhanced ?ields are availa,le in .$/ E'ithin the --5. including the corresponding o,4ectF

EAB?!
Add ne' ta,le 'ith --5. E.P J .usiness @ransactionF @a,les G AP*s are generated Ae' $,4ect G relations in .$/ are generated Create Emanually vie' in Component 5or!,enchF ?ields are availa,le in the field set of the B* Configuration @ool

?ields are availa,le in the field set of the B* Configuration @ool Efor the corresponding vie'F

Position fields on the screen J set attri,utes

7/ C"D=/G7RAE/"D E""?

Position fields on the screen J set attri,utes

>7

Application !nhancement EoolC "%er%ie

# @he Application -nhancement @ool EA-@F provides a B* ,ased overvie' over all enhancements. # *t is possi,le to search for enhancements, and to display, create, change, or delete enhancements. *t features1 ( Creating custom fields ( efining dropdo'n list ,o7es for custom fields ( @ranslating field la,els and entries in dropdo'n list ,o7es ( Assigning search helps and chec! ta,les to custom fields ( &a!ing ne' custom fields availa,le for search criteria andGor result lists, .usiness *ntelligence E.*F reporting, RG6 Adapter, CR& &o,ile... ( Bsing different data types, e.g. characters, dates, times, num,ersL ( Reusing fields in other ,usiness o,4ects, if they are ,ased on the same enhancement place
>>

Application !nhancement EoolC Start the Application Eool

@here are three different 'ays to start the Application -nhancement @ool in %AP CR&.
Overvie w %& Con#iguration o# Application

# -na,le the configuration mode in the general settings on the central personali3ation page of %AP CR& # Choose one of the sym,ols for B* configuration in the header area of the application # @o start the Application -nhancement @ool, clic! %ho' -nhancements in the Configurations ,loc!

>=

Application !nhancement EoolC Start the Application Eool (cont.)

%& Con#iguration o# Administration Work Center

# Choose UHie' Configuration0 in the navigation ,ar of the Administration 'or! center Esystem administrator roleF # -nter a B* component, and choose a vie'. # @o start the Application -nhancement @ool, clic! U%ho' -nhancements0.
Navigation Bar

# %tart the Application -nhancement @ool directly in the navigation ,ar of the system administrator role # Choose U-nhance Applications0 in the Administration 'or! center # %earch for enhancements at the %earch page

=0

(esign ?a+er Customi.ing

# esign /ayer 'as introduced to give a more simple and easy to use functionality for changing several B* Components on one time. # @he design layer lin!s B*;related settings to design o,4ects, 'hich span several vie's that implement the same ,usiness content. @he design layer features1 # Rename )ield la&els # 0ide )ields %et a field to UHidden01 ?ield isnUt visi,le for the end user in the application # Set a )ield to K=ield e$cluded )rom )ield setL ?ield is not visi,le in the field set of the B* Configuration@ool E@his 'ill ,e used to reduce the availa,le fields in the field setF. # Assign e$isting %alue help from dictionary1 Halue help E%earch help, Chec! ta,le, omain valuesF ?ield type E*nput field, Chec!,o7, ropdo'n list ,o7

# Ke+ =eatures and Bene)itsC # *ncrease efficiency ,y reducing the tas! of maintaining the same field la,els on every vie' they are visi,le # Centrali3ed 'ay to maintain field la,els # Reduce the num,er of fields 'ithin the B* Configuration @ool that are not needed Ee.g. technical fieldsF

="

Con)iguration "%er%ie
Eas,
Configure vie's1 position fieldsGcolumns, add fieldsGcolumns from field set, remove fieldsGcolumns, rename la,els, set fields to mandatoryGdisplay only, and define load option for ,loc!s and more Bse parameters to save your configuration Bse customer;specific fields 'ithin vie' configuration Add customer;specific fields and ta,les to e7isting ,usiness o,4ects *mplement same configuration content for several vie's -asy -nhancement 5or!,ench E--5.F esign /ayer Customi3ing

Eool
B* Configuration @ool

Assign value helps G drop do'n list ,o7es from data dictionary for customer specific fields CreateG -nhance B* components, create o'n vie's, conte7t nodes.. .%P Component 5or!,ench Configure ,uttons, define value helps G drop do'n list ,o7es Change Aavigation .ar E"st J 2nd level navigationF, /ogical /in!s, .usiness Role Customi3ing Add customer;specific fields to e7isting ,usiness o,4ects Aavigation .ar G .usiness Role Customi3ing Application -nhancement @ool EA-@F
=2

S+stem (emo :C 7/ Con)iguration %ia Component @or,&ench

7nitC 7/ Con)iguration %ia Component @or,&ench @opic1 $pen and customi3e a vie' in the B* Configuration @ool from the B* Component 5or!,ench.

=6

Agenda
# %AP CR& 5e, B*
( Architecture ( B* Concept and B* Component Concept ( Aavigation .ar and .usiness Roles ( B* Configuration ( Personali3ation ( Additional ?eatures ( BOL & GenIL ( Knowledge Check

# KJA and ay " 5rap;up

=8

Personali.ation
# 2ou can use a ,undle of tools and options to set up and personali3e %AP CR& to your individual preferences. # &ost of the functions to personali3e the user interface of %AP CR& are conveniently accessi,le on the central personali3ation page. # ChangeGChec! Personal data, assigned .us.Role. # Change current pass'ord # ChangeGChec! general settings Etime 3one, dateGtime format, currency etc.F # Activate screen reader mode # -na,le Configuration &ode # efine the settings for the group'are integration in %AP CR& Ee.g. &% $utloo!F
=9

Personali.ation (cont.)
-nter the central personali3ation page #Change /ayout E%!in, @e7tF #Pers. /in!s in Aav. .ar Ee.g. V of recent itemsF %et up personal !ey,oard shortcuts Personali3e your favorites for the home page su,scri,e to your personal feed. -nter the lin! to your feed reader
=:

Personali.ation (cont.)
5hen you log on, all pages have a particular default layout, ,ut you can personali3e your pages. Hia drag and drop or enter the personal setting options via this &utton $ptions for layout personali3ation1 ( $vervie' page Ee.g. visi,ility and order of Assignment .loc!sF ( @a,les and /ists Ee.g. order and visi,ility of columnsF ( Home page Earrangement of Assignment .loc!sF 2ou can find some e7amples on the ne7t pages. DoteC @he personali3e settings are saved for your personal user account. *n most of the cases the changes can ,e reset to the default settings that are defined 'ithin CR& customi3ing.
=7

Personali.ationC Personali.e Ea&les

Business e!uirement

Bser should have the possi,ility to create his o'n @a,le /ayout E'ithin certain degree of freedom defined in configuration ,y system e7pertsF.
Solution

-ach user can define1 # Column to visuali3e E'ithin the ones defined as availa,le in configurationF # Column order # Column 'idth # Aum,er of displayed lines

Tips & Tricks

Bser personali3ation cannot overrule page configuration. @hat means that user can only personali3e ta,les in the ,orders of the given configuration. ?or e7ample they can only sho' or hide fields, 'hich are already availa,le for the screen.
=>

Personali.ationC Personali.e 0ome Page

Business e!uirement

Bser should have the possi,ility to create their o'n Home Page /ayout E'ithin certain degree of freedom defined in configuration ,y system e7pertsF.
Solution

-ach user can define1 # Assignment .loc! to visuali3e E'ithin the ones defined as availa,le in configurationF # Assignment .loc! /ayout

Tips & Tricks

Home page personali3ation could ,e deactivated if users must not have this fle7i,ility Ee.g. to simplify application maintenanceF.
==

Agenda
# %AP CR& 5e, B*
( Architecture (L ( B* Configuration ( Personali3ation ( Additional ?eatures
( @ransaction /auncher ( @as! .ased B*

( BOL & GenIL ( Knowledge Check

# KJA and ay " 5rap;up

"00

Eransaction ?auncherC /ntroduction

@ransaction /auncher can ,e used to launch BR/s Eand .%P transactions from other systemsF or .$R transactions of any %AP system. %teps to follo' in order to configure the transaction launcher1 # efine BR/ Repository EBR/s and .%P transactionsF # or efine /ogical %ystem and Create .$R $,4ect @ype E.$R transactionsF # Configure the @ransaction /auncher ( ?ollo' 'i3ard steps # *ntegrate the BR/ into the Aavigation .ar ( efine /ogical /in! * ( efine irect /in! )roup and assign /ogical /in! ( Assign irect /in! )roup to Aavigation .ar ( Ad4ust the definition of .usiness Role to activate the /ogical /in!
"0"

Agenda
# %AP CR& 5e, B*
( Architecture (L ( B* Configuration ( Personali3ation ( Additional ?eatures
( @ransaction /auncher ( @as!ed .ased B*

( BOL & GenIL ( Knowledge Check

# KJA and ay " 5rap;up

"02

Eas, Based 7/
2ou can ,uild tas!;,ased user interfaces EB*sF to ma!e it easier for users to perform their daily tas!s. @he user interface dynamically supports users in performing their daily tas!s. # @he user interface is structured in several steps. # -very step represents a small, easy part of the overall tas!. # @he users are guided through these steps to accomplish their tas!. # *n the B* configuration, you can select the vie's that you 'ant to use for the tas!;,ased B*. # 2ou can define the steps of the tas!;,ased B* and define the order of these steps. A vie' can ,e assigned to every step.
"06

Eas, Based 7/ < !$ample

@hese screenshots sho' an e7ample for succesive steps of a process dealing 'ith a certain tas! Eflight ,oo!ingF. @he current step is highlighted in the topline W,readcrum,U navigation.

"08

Eas, Based 7/ < Con)iguration

# *n the configuration you can assign vie's to the @as! .ased B*. # 2ou can easily define the order and the name of each step. # Additionally, you can define an optional e7planatory te7t for every step.

"09

Agenda < (a+ 1

# %AP CR& 5e, B*
( Architecture ( B* Concept and B* Component Concept ( Aavigation .ar and .usiness Roles ( B* Configuration ( Personali3ation ( Additional ?eatures ( BOL & GenIL ( Knowledge Check

# KJA and ay " 5rap;up

"0:

Business ?a+er
@he &usiness la+er consists of the1 # Business "&'ect ?a+er (B"?) @he .$/ stores data of ,usiness o,4ects such as ,usiness partners and sales orders, during runtime of a 5e,Client session. *t 'as implemented to guarantee the separation of the CR& 5e,Client B* and the underlying ,usiness logic. # Generic /nteraction ?a+er (Gen/?) @he )en*/ handles the data transfer from the .$/ to the Application Programming *nterfaces EAP*sF of the underlying ECR&F ,usiness engine Eapplication logic and data,ase ta,lesF. *n other 'ords, the )en*/ connects the .$/ to the underlying ,usiness logic and data,ase through the Application Programming *nterfaces EAP*sF of the underlying application E'hich can ,e even different from %AP -RP %ystems Ee.g. %AP -CC, non; %AP,LF. Business "&'ect )roup of unstructured attri,utes, 'hich characteri3e a .usiness o,4ect Ee.g. Accounts, -mployees, $rdersI ActivitiesLF. .$ can ,e hierarchically aggregated in order to create an $,4ect &odel.
"07

Business "&'ect ?a+er and Generic /nteraction ?a+er

(ata structures o) the B"? hold Business "&'ects )or CRM e& client sessions Gen/? Model and /mplementation Classes connect B"? to CRM AP/s and (B
e.g. %AP -RP, %AP *%B, &% -7cel, %ie,elL

"0>

Main B"? Business "&'ect E+pes

# Access "&'ect An access o,4ect is a special type of .$, 'hose * can ,e used to determine ,oth its attri,utes and those of its dependent o,4ects. Root "&'ect A root o,4ect is the superior element 'ithin a group of o,4ects that are aggregated to one another in a Mparent;children< hierarchy structure. *ts * can ,e used to determine ,oth its attri,utes and those of its dependent o,4ects. (ependent "&'ect A dependent o,4ect is a Mchildren< o,4ect, 'hose attri,utes cannot ,e determined solely from the * of this .$, ,ut instead, only or together 'ith the * of the superior o,4ect. Search "&'ect A Duery o,4ect is a special type of .$ 'hose attri,utes are the parameters of a search reDuest. (+namic Search "&'ect A dynamic Duery o,4ect is a type of .$ 'hose attri,utes are the parameters of a search reDuest. *t is possi,le to create select options ,y com,ining these parameters. Search Result "&'ect @he result o,4ect of a search reDuest is an associated access o,4ect at the uppermost level of the hierarchy. "0= #

Business ?a+er Eools

G!D/?HM"(!?HBR"@S!R Hisuali3es the .$/ model and the relations ,et'een .$/ o,4ects.

G!D/?HB"?HBR"@S!R @est data retrieval from data,ase to .$/ through the )-A*/. Hery useful for testing Dueries.

""0

Genil Model Bro ser

# %ystem representation of data ,inding # .$/ &odel .ro'ser ena,les accessing1 ; Bnderlying .$/ model ; ata,ase entities Efields, data elements, domainsF to 'hich B* attri,utes refers to

"""

!$ercise 3 Genil Model Bro ser

7nitC Genil Model Bro ser @opic1 -7plore the )enil &odel .ro'ser. @S1 )-A*/X&$ -/X.R$5%-R

At the conclusion o) this e$ercise- +ou ill &e a&le toC # -7plore the )enil model via the )enil model ,ro'ser # -7amine the )enil data model and the relations ,et'een .$/ o,4ects modeled in the )enil Additional in)ormationC # Ans'er some Duestions to the )enil model ,y using the )enil &odel ,ro'ser.
""2

!$ercise : Genil B"? Bro ser

7nitC Genil B"? Bro ser @opic1 -7plore the )enil .$/ .ro'ser. @S1 )-A*/X.*/X.R$5%-R

At the conclusion o) this e$ercise- +ou ill &e a&le toC # -7plore the .$/ via the )enil .$/ ,ro'ser # -7amine and change the values .$/ o,4ect attri,utes # -7ecute Dueries Additional /n)ormationC # Ans'er some Duestions to different .$/ o,4ects and Dueries ,y using the )enil .$/ ,ro'ser.
""6

Agenda
# %AP CR& 5e, B*
( Architecture ( B* Concept and B* Component Concept ( Aavigation .ar and .usiness Roles ( B* Configuration ( Personali3ation ( Additional ?eatures ( BOL & GenIL ( Knowledge Check

# KJA and ay " 5rap;up

""8

Kno ledge Chec,

". +no'ledge chec!s tie ,ac! to learning o,4ectives and !ey content covered in the day. 2. +no'ledge chec!s are revie' Duestions listed on the slide for the participants to ans'er. Ans'ers should ,e added to the ?aculty )uide E+no'ledge Chec!s sectionF. 6. +no'ledge chec!s occur at the end of each day or can ,e included at the end of longer topics.

""9

Kno ledge Chec,

"":

Kno ledge Chec,

". @he CR& 5e,Client is ,ased on a multi;layer architecture on the server side. 5hat are the main /ayersQ 2. 5hat is the difference ,et'een .$/ o,4ects and conte7t nodesQ 6. 5hich parts of the )B* are depending on the ,usiness role. 8. Aame the four parameters ,y 'hich the configuration of a vie' is differentiated. 9. Ho' can you find out the technical name of a vie'Q :. Aame the different configuration tools and descri,e them.

""7

Agenda
# %AP CR& 5e, B*
( Architecture ( B* Concept and B* Component Concept ( Aavigation .ar and .usiness Roles ( B* Configuration ( Personali3ation ( Additional ?eatures ( BOL & GenIL ( Knowledge Check

# KJA
"">

?essons ?earned
# 5e have introduced ourselves and e7changed our e7pectations # 5e have no' a first understanding of %AP CR& 7.0 functionalities # 5e understand 'hich enhancements have ,een introduced 'ith %AP CR& 7.0 # 5e can no' e7plain the concept of CR& 5e, B* # 5e have no' a ,asic understanding ho' to configure the B* and some additional features # 5e can no' e7plain the purpose and the structure of a .usiness Role
""=