Beruflich Dokumente
Kultur Dokumente
InfoProvider
Source System
Customer 2
Source System
Customer 2
Cent r al Dat a Model
SAP AG 2005, SAP Business Intelligence and Analytics Conference / F1_Hennecke / 9
Dec ent r al i zed Dat a Model
Source System
Customer 1
SAP NetWeaver BI
InfoProvider
Source System
Customer 2
Source System
Customer 2
SAP AG 2005, SAP Business Intelligence and Analytics Conference / F1_Hennecke / 10
Hybr i d Dat a Model
Source System
Customer 1
SAP NetWeaver BI
InfoProvider
Source System
Customer 2
Source System
Customer 2
*
* Only if ASP customer specific queries are required
SAP AG 2005, SAP Business Intelligence and Analytics Conference / F1_Hennecke / 11
Ac c ess t o SAP Net Weaver BI t ool s
BEx Query Designer
Information Broadcasting
MS Excel
Add-in
BEx Web
DB
Connect
BAPI
Service
API
File XML/A
BEx Analyzer
BI Platform
Data Warehouse
Enterprise Portal
Analytic Engine Meta Data Mgr
Business Explorer
Suite (BEx)
ASP
Cust omer
ASP
Vendor
n Example: Do ASP customers
need to define their own
queries ?
u If yes hybrid data model
u If no central data model or
hybrid data model
n In a common system, data
warehouse operation should
always be the task of the ASP
vendor.
SAP AG 2005, SAP Business Intelligence and Analytics Conference / F1_Hennecke / 12
Busi ness Requi r ement s and Dat a Model i ng
Do ASP
customers share
the same
requirements?
Master data Transaction Data
The decision, whether business requirements to the data warehouse
can be harmonized is decisive for the modeling of the whole
solution:
Shared master data
objects
Shared transaction
data models (hybrid
or central approach)
Separate master data
objects
Separate transaction
data models
(decentralized approach)
Separate systems and /
or hardware
FLEXI-
BILITY
TCO But:
SAP AG 2005, SAP Business Intelligence and Analytics Conference / F1_Hennecke / 13
Busi ness Requi r ement s and TCO
Customer 1
Customer 2
Customer 3
ASP Vendor
Harmonized
requirements
in the
business
blueprint
Reduced
complexity
in
implementation
Basic assumption:
ASP customers have similar requirements or the same business environment
n Flexibility in terms of
u Responding to individual requirements
u Responding to specific needs for security or availability
n will in return raise the TCO!
n In the business blueprint you should strive to harmonize and standardize
the requirements of your ASP customers
n This is the basis for data modeling and therefore for optimal TCO
concerning complexity in the implementation and efficient operation.
Increased
efficiency in
operation and
administration
SAP AG 2005, SAP Business Intelligence and Analytics Conference / F1_Hennecke / 14
Si zi ng t he ASP Envi r onment and Dat a Model i ng
Size of a single ASP customer
Central data
model
n The number of ASP customers as well as their individual size will play a
predominant role in defining the optimal data model
Hybrid data
model
n In addition,
other technical
requirements
will influence
this decision
(depending on
their individual
priority)
u Availability
u Expandability
(Scalability)
u Performance
u TCO
N of ASP customers
P E R F O R M A N C E
Decentralized
data model =
Not in scope
as not typical
E
X
P
A
N
D
A
B
I
L
I
T
Y
Central data
model
Hybrid data
model
Implementation
Operation and Performance
Introduction
Business Blueprint and Data Modeling
SAP AG 2005, SAP Business Intelligence and Analytics Conference / F1_Hennecke / 16
I mpl ement i ng Mast er Dat a Obj ec t s
In an ASP scenario you should consider compounding for
modeling your central master data objects
n ASP customers are legally independent.
n Future harmonization among customer is not probable.
n Less effort in implementing the ASP scenario
n All characteristics (except special characteristics like time
characteristics) will be compounded to a central ASP Customer
specific characteristic: Tenant, Client, Company,
Tenant Bus. Partner Tenant / Bus.Partner
SAP AG 2005, SAP Business Intelligence and Analytics Conference / F1_Hennecke / 17
Gl obal Tr ansf er Rout i ne
EF 4714 2000
AC 4713 2000
CD 4712 1000
AB 4711 1000
Region Bus. Partner Tenant
CD 4712
AB 4711
Region Bus. Part
Source system Tenant 1
ERPCLNT100
Mapping Table
EF 4714
AC 4713
Region Bus. Part
3000 DEBCLNT100
2000 ERPCLNT200
1000 ERPCLNT100
Tenant Source system
Master data of InfoObjekt 0BPARTNER
(Compounded to ZTENANT)
PSA PSA
global Transfer
Routine
Source system Tenant 2
ERPCLNT200
Usually, the additional characteristic Tenant can be derived from
the source system in master data and transaction data loading.
n If not, it might be included in the
data to be extracted or can be
derived from other data fields.
SAP AG 2005, SAP Business Intelligence and Analytics Conference / F1_Hennecke / 18
Authorizations for displaying
data in the BI front end
Tenant 1000
Tenant 2000
Tenant .
Sales
.
Subject / Assigned queries
C
r
e
a
t
i
n
g
q
u
e
r
i
e
s
E
x
e
c
u
t
i
n
g
q
u
e
r
i
e
s
Authorization
for using BI
front end
tools
Financials
Ac hi evi ng Sec ur i t y Thr ough Rol es
SAP AG 2005, SAP Business Intelligence and Analytics Conference / F1_Hennecke / 19
I mpl ement i ng Aut hor i zat i ons
n Clear naming conventions for shared and tenant specific objects have
to guide the implementation project. In this way, you can considerably
improve the implementation and administration of authorizations.
n For secure display of data in the reporting, reporting authorization
objects are to be defined on the central compounding characteristic.
u No displaying of data from other tenants possible.
u In queries, this characteristic will be restricted in the global filter using
authorization variables.
n You can use the authorization object S_TABU_LIN to attain secure input
helps for characteristic values in the front end.
n Make sure that you store hierarchies for each ASP customer separately.
You can use authorization object S_RS_HIER to implement
authorization-based access to hierarchies.
n ASP vendor employees involved in support should be subject to a
legally binding obligation to maintain confidentiality, within which the
extensive possibilities for offering technical support in the system can
still be granted.
SAP AG 2005, SAP Business Intelligence and Analytics Conference / F1_Hennecke / 20
Tar get ed Ac c ess t o Tenant Spec i f i c Dat a
Tenant = 1000
Tenant = 2000
Filter
Tenant = 1000
Filter
Tenant = 2000
Tenant = 2000
n In a hybrid data model constants
on characteristic tenant in
basic InfoCubes are used for
selection the relevant InfoCubes
n In a central data model, a
characteristic value filter on
characteristic tenant will
allow for targeted access to
relevant data
Implementation
Operation and Performance
Introduction
Business Blueprint and Data Modeling
SAP AG 2005, SAP Business Intelligence and Analytics Conference / F1_Hennecke / 22
I mpor t ant Topi c s i n Oper at i on & Per f or manc e Tuni ng
n Shared master data tables might become large
u Special consideration is needed in performance monitoring and tuning
n A high number of data loading and administration processes has to be
administrated
u The optimum use of the available time slot can be achieved the best through
usage of parallelization options on process chains and process level.
n Changes on shared objects will affect a high number of ASP
customers
u Only carry out changes in cycles (templates)
n With a central data model you must consider how to proceed if
individual requests cannot be loaded successfully
u This can affect whether data for other users is released for reporting.
u Solution: Immediately deleting incorrect requests and rolling up all requests
that have not yet been released for reporting or as a temporary solution,
unreleased requests can be accessed using variable 0S_RQALL
n Maximum usage of shared, cross customer objects and template
transports for easy expandability of scenario to additional customer
u Guidelines & Tools can be found in the paper ASP with SAP BW
SAP AG 2005, SAP Business Intelligence and Analytics Conference / F1_Hennecke / 23
Ser vi c e Level Agr eement s
Possible Criteria for charging operational costs in a Service Level
Agreement (SLA)
n Usage of system resources
u Using CPU, DB,
n Number of queries and reports the ASP customer is authorized for
u An additional fee applies if ASP customer specific objects have to be
administrated
n Number of times queries are accessed
u Can be monitored using the technical content
n Number of active users per user type. Here we refer to the categories
and assumptions defined in the BW Quicksizer
(http://service.sap.com/quicksizer)
u Different user types create different system load
n Validity of data: the more frequently report results have to be updated,
the more frequently data transfer have to be scheduled
u Alternatively: number of data loads / day
SAP AG 2005, SAP Business Intelligence and Analytics Conference / F1_Hennecke / 24
Summar y
n ASP vendors have important requirements to a BI solution in
terms of security, TCO, quality and scalability.
n Implementing a common solution for all your end customers on
harmonized requirements with minimum complexity is the key
for optimal TCO.
n A data modeling strategy has not only to be based on
customers requirements but also on number and size of
customers that will use the solution.
n BI tools will allow you to model your solution for optimal
security and scalability.
SAP AG 2005, SAP Business Intelligence and Analytics Conference / F1_Hennecke / 25
Fur t her I nf or mat i on
Internet
www.sap.com/bi or www.sap.com/analytics
SAP Service Marketplace:
www.service.sap.com/bi
- BI InfoIndex - Application Service Providing (ASP)
www.service.sap.com/nw-howtoguides
- Business Intelligence - How toCreate Efficient MultiProvider Queries
Training courses
http://www.sap.com/education
Contact person
Rudolf Hennecke, SAP AG
SAP AG 2005, SAP Business Intelligence and Analytics Conference / F1_Hennecke / 26
Q&A
Quest i ons?
SAP AG 2005, SAP Business Intelligence and Analytics Conference / F1_Hennecke / 27
n 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.
n Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
n Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
n IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP,
Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation.
n Oracle is a registered trademark of Oracle Corporation.
n UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
n Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWinare trademarks or registered trademarks of Citrix Systems, Inc.
n HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C