Escolar Documentos
Profissional Documentos
Cultura Documentos
0:
Enterprise Data Warehousing
Overview
November 2007
Agenda
1. Overview
2. Data Modeling
2.1. Data Warehousing Workbench
2.2. DataSource
2.3. Transformation
2.4. DataStore Objects
2.5. Modeling Data Marts
3. Data Flow Design
3.1. Data Transfer Process
3.2. Process Chains
4. Administration & Monitoring
4.1. Administration Cockpit
4.2. Information Lifecycle Management
5. Maintaining Data Security
6. Performance Management
5.1. SAP NetWeaver BI Accelerator
5.2. Other Performance Techniques
Provide each organizational unit or better each role with the needed reliable,
consolidated, integrated, up-to-date, and historical information
e.g.,
at business unit level provide a:
local/subsidary view
regional view
global view
at headquarter level
across business units
provide
regional view
global view
EDW
Planning Enterprise
Composite Ad Hoc BI App Layout Report MS Excel
BI
BI Consumer
Consumer Services
Services Web Services
BI Layer ODBO/XMLA
Query Designer
Master Data
Repository
Meta Data
SAP NetWeaver
Virtual- Planning Modeler BI Accelerator
Provider
Analytic Engine
BI Accelerator
Monitoring / Administration
Aggregation Security
Meta Data Repository / Documents
DataSource / PSA
Source Systems
© SAP 2007 / Page 6
Enterprise Data Warehousing - Processes
Performance Management
Provides all means to accelerate query performance, in particular the SAP NetWeaver BI Accelerator.
1. Overview
2. Data Modeling
2.1. Data Warehousing Workbench
2.2. DataSource
2.3. Transformation
2.4. DataStore Objects
2.5. Modeling Data Marts
3. Data Flow Design
3.1. Data Transfer Process
3.2. Process Chains
4. Administration & Monitoring
4.1. Administration Cockpit
4.2. Information Lifecycle Management
5. Maintaining Data Security
6. Performance Management
5.1. SAP NetWeaver BI Accelerator
5.2. Other Performance Techniques
Usability Features
Favorites
Personalization
Advanced Search
Complete data flow at a glance
1. Overview
2. Data Modeling
2.1. Data Warehousing Workbench
2.2. DataSource
2.3. Transformation
2.4. DataStore Objects
2.5. Modeling Data Marts
3. Data Flow Design
3.1. Data Transfer Process
3.2. Process Chains
4. Administration & Monitoring
4.1. Administration Cockpit
4.2. Information Lifecycle Management
5. Maintaining Data Security
6. Performance Management
5.1. SAP NetWeaver BI Accelerator
5.2. Other Performance Techniques
Information Access
(Architected)
Data Marts
Operational
Data Store
Data
Warehouse
Any Source
Sources
Support of virtually all sources
DataSource
ETL Tool
Multi-
Relational SAP Legacy
Dimensional File XML
Source Source Applications
Source
e.g. IBM DB2, e.g. Hyperion e.g. SAP CRM e.g. SAP e.g. ORACLE
Teradata NetWeaver PI Financials
(via proxy
framework)
Highlights
unique look and feel for all of the DataSource Types
PSA is attached to DataSource
InfoPackage writes to PSA
Data Transfer Process writes from PSA to data targets
direct/remote access is optional
preview feature is standard
automated conversions (e.g. date format detection)
General Information
Descriptions
Reconciliation flag (not
functional)
Opening Balance
(inventory)
Error handling (duprecs)
SAP NetWeaver BI
Process Chain
InfoProvider
Data Transfer
Process
Transformation
DataSource / PSA
InfoPackage
Source System 1
Source
SAP NetWeaver BI
Process Chain
(optional) InfoProvider
Restrictions: X
DataSource / PSA
1. Overview
2. Data Modeling
2.1. Data Warehousing Workbench
2.2. DataSource
2.3. Transformation
2.4. DataStore Objects
2.5. Modeling Data Marts
3. Data Flow Design
3.1. Data Transfer Process
3.2. Process Chains
4. Administration & Monitoring
4.1. Administration Cockpit
4.2. Information Lifecycle Management
5. Maintaining Data Security
6. Performance Management
5.1. SAP NetWeaver BI Accelerator
5.2. Other Performance Techniques
Transformation Transformation
DTP DTP
InfoProvider
Transformation Data
Transfer
Process
DataSource / PSA
Target
Universal transformation from source
to target objects
* optional
© SAP 2007 / Page 21
Transformation – Definition
Transformation
Update rule
Source Target
fields fields
Rules per
Note: Key figures, characteristics and date group
fields are shown on the same level
(transformation group)
InfoProvider
Data
Transfer
Transformation Process Transformation
InfoSource
Transformation directly links from a source InfoProvider (or DataSource) to a target
InfoProvider
An InfoSource is usually not needed
New InfoSource architecture is used (flat InfoObject-based structure)
Scenarios for (flexible) InfoSource
A flexible InfoSource is necessary in order to use currency or unit conversion
from the source DataSource Define InfoSource as an intermediate structure
You can use a flexible InfoSource as a uniform source for several targets; the
InfoSource can the be target from different sources (see next slide)
Note: for ‘direct’ InfoSources (for master data updates), there is no difference
between ‘old’ and ‘new’ InfoSource, i.e. you can define a transformation as well as
transfer rules
Pre-requisite: InfoObject is defined as InfoProvider
InfoSource
Scenario: InfoSource as a uniform source for several targets and as target from
different sources
SAP NetWeaver Business Intelligence
InfoProvider
InfoProvider 1 InfoProvider 2 … InfoProvider m
Transformation
…
InfoSource
Transformation
…
Transformation Groups
Summarize key figures with the same characteristics assignments
All key figures of one transformation are updated based on the same characteristic
values
If other characteristic updates are necessary for particular key figures, a new
transformation is created
Transformation Groups
Use / Example
Scenario: overview on bonus-relevant sales of all employees
An employee generates a certain sales volume, which is the basis for his/her
bonus
The manager of the employee will be assigned 10% of the employee’s bonus as
manager’s bonus relevant
two transformation groups are generated (e.g. ‘employee’ and ‘manager’)
Source
Employee Sales Volume Manager
Johnson 1000 Giles Transformation Group 1
Employee Employee
Sales Volume Bonus-relevant Sales
1. Overview
2. Data Modeling
2.1. Data Warehousing Workbench
2.2. DataSource
2.3. Transformation
2.4. DataStore Objects
2.5. Modeling Data Marts
3. Data Flow Design
3.1. Data Transfer Process
3.2. Process Chains
4. Administration & Monitoring
4.1. Administration Cockpit
4.2. Information Lifecycle Management
5. Maintaining Data Security
6. Performance Management
5.1. SAP NetWeaver BI Accelerator
5.2. Other Performance Techniques
Activ-
EDW ODS Delta / Change Fast Access Active Change ation Integration
DataStore object type layer Layer Data Capture (no activation) Others Data Log Queue into data flow
Delta
determination
from after
Standard DataStore images via staging
Object X X on record level X X X (DTP)
Staging layer
esp. for large
sets of data
with
Write-optimized On request (generally) via staging
DataStore Object X level X unique key X (DTP)
Details
Option ‘Generation of SID Values’
Improves query performance
Queries are also possible if SID
values are not generated
Option ‘Unique data records’
Only available if ‘Generation of
SID Values’ is set
Activation process is optimized
(only inserts, no sorting, no
before image)
Note: error if key already exists
For (non-reporting) scenarios, write-optimized DataStores are recommended instead of
standard DataStore objects with unique flag
Performance Improvement
Rollback
Instead of rolling back in serial and in one transaction
rollback now is in parallel and for each data package there is a single task
Structure
Activation queue
Used to store data to be updated in DataStore Object which has not been activated
After activation the data can be deleted
Technical key: Request SID, Package ID, Record number
Active Data Table
Same structure as
the DataStore Object
definition
Change Log
Change history for delta mechanism from the DataStore Object into other InfoProvider
Key fields:
– Request GUID, Package ID, Record number
Scenarios
Fast EDW inbound layer (no activation needed)
For large sets of data records on detailed level (e.g. document level)
“wide” structure is possible (16 key fields, 749 data fields)
“Load of new records”:
Every record has a new key No update, only inserts
E.g. for POS data
“Load & Drop”:
Full Upload into DataStore Object
Update subsequent InfoProvider
Drop DataStore Object data
Continue with full uploads
Details
Definition
Only active data table (key: request ID, Packet No., Record No.)
– No change log and no activation queue
– Technical key is unique
Partitioned on request ID
No SID generation
–Nevertheless: Reporting is possible (but not optimized for performance)
Fully integrated in data flow: usable as data source and data target
–Export into InfoProviders via request delta
Can be included into MultiProvider or InfoSet
Uniqueness of Data
Checkbox “Do not check Uniqueness of data”
Performance improvement during data load
– Does not create/maintain unique index on
semantic key
Details
Definition
Only active data table
Can be used as data target within APD
cannot be used for transformation (upload) scenarios
no loading process within BI
but export into next InfoProvider is possible
Reporting is possible
Scenarios
Used for direct input of (external) transactional data
– E.g. BI table for user interaction
An API is available with a set of function modules
(some are RFC enabled)
Fed by APD processes
1. Overview
2. Data Modeling
2.1. Data Warehousing Workbench
2.2. DataSource
2.3. Transformation
2.4. DataStore Objects
2.5. Modeling Data Marts
3. Data Flow Design
3.1. Data Transfer Process
3.2. Process Chains
4. Administration & Monitoring
4.1. Administration Cockpit
4.2. Information Lifecycle Management
5. Maintaining Data Security
6. Performance Management
5.1. SAP NetWeaver BI Accelerator
5.2. Other Performance Techniques
InfoCube
Star Schema optimized for multi-dimensional reporting
Master
Master Master
Master
Data
Data Data
Data
Surrogate Key
Dimension
Dimension Dimension
Dimension
Dimension ID
Fact Support of
FactTable
Table degenerated
dimensions
Dimension
Dimension Dimension
Dimension
Master
Master Master
Data Master
Data Data
Data
© SAP 2007 / Page 38
InfoCube
Example:
MultiProvider
Logical definition without data persistency
Abstraction level for queries
Can integrate the following InfoProviders via union operator
InfoCube
InfoObject
DataStore Object
VirtualProvider
InfoSet
Aggregation Level
InfoSet
Logical definition without data persistency
Can integrate InfoCubes, DataStore Objects and InfoObjects
join and outer join operator
InfoSet
w/o data
persistency
1. Overview
2. Data Modeling
2.1. Data Warehousing Workbench
2.2. DataSource
2.3. Transformation
2.4. DataStore Objects
2.5. Modeling Data Marts
3. Data Flow Design
3.1. Data Transfer Process
3.2. Process Chains
4. Administration & Monitoring
4.1. Administration Cockpit
4.2. Information Lifecycle Management
5. Maintaining Data Security
6. Performance Management
5.1. SAP NetWeaver BI Accelerator
5.2. Other Performance Techniques
SAP Netweaver BI
TR
Process Chain
InfoSource Process Chain
DTP
TR DTP
TR
DataStore Object 3
DTP TR TR DTP
DTP DTP
TR TR
DataSource
DataSource (PSA)
(PSA) DataSource
DataSource (PSA)
(PSA)
IP IP
Extraction
mode: Delta or
Full
Loading directly
into Data Target
without PSA
Prerequisite
DataSource is enabled for direct access (table ROOSOURCE)
Or SAP Basis Plug-In Release 2005.1 SP8, or SAP Plug-In Release 2004.1 4.6C Support
Package 13
Or if you want to have the correction before the above support packages are released, please
apply note 923783.
Process chain
can automate
the loading
process
DTP
DTP Scheduler
Scheduler
IP DTP
DataSource
DataSource (PSA)
(PSA)
Source System
Error Handling
Possibility to choose in the scheduler to...
abort process when errors occur
process the correct records but do not allow reporting on them
process the correct records and allow reporting on them
Number of wrong records which lead to a wrong request
Invalid records can be written into an error stack
Keys should be defined for error stack to enable the error handling of DataStore object
Temporary data storage can be switched on/off for each substep of the loading process
Invalid records can be updated into data targets after their correction.
Error Handling
Once errors occur, the whole
Data Package is terminated.
The request is not released
for reporting.
Error Stack
Stores erroneous records
Automatic checks: Existence of master data, conversion exit (restricted, e.g.
Alpha)
Customer-defined checks in transformation routines (see appendix for more
information)
Keeps the right sequence of records for consistent DataStore handling
Key of error stack defines which data should be detained from the update after the
erroneous data record
After correction, Error-DTP updates data from error stack to data target
Note: Once the request in the source object is deleted, the related data records in
error stack are automatically deleted
Error Stack
Key of Error Stack = Semantic Groups
Subset of the key of the target object
Max. 16 fields
Defining which data should be detained from the update after the erroneous
data record (for DataStore Object)
Semantic groups bundle records with the same semantic group key into the
same request see transformation chapter for more details (for DataStore
Object and InfoProvider)
DTP Monitor
Integrated in InfoProvider management screen
Integrated in DTP maintenance
Additional information: duration of each step
Temporary storage access – if activated
Error Stack is displayed in DTP Monitor
Error Stack
Data display in
temporary storage
Data Transfer
Process Initialization
without data transfer
1. Overview
2. Data Modeling
2.1. Data Warehousing Workbench
2.2. DataSource
2.3. Transformation
2.4. DataStore Objects
2.5. Modeling Data Marts
3. Data Flow Design
3.1. Data Transfer Process
3.2. Process Chains
4. Administration & Monitoring
4.1. Administration Cockpit
4.2. Information Lifecycle Management
5. Maintaining Data Security
6. Performance Management
5.1. SAP NetWeaver BI Accelerator
5.2. Other Performance Techniques
Start
Activate
Data in
DataStore
Object
Write a message
and fill in recipient
and type. Info
saved within
process variant.
Planning view
context menu
1. Overview
2. Data Modeling
2.1. Data Warehousing Workbench
2.2. DataSource
2.3. Transformation
2.4. DataStore Objects
2.5. Modeling Data Marts
3. Data Flow Design
3.1. Data Transfer Process
3.2. Process Chains
4. Administration & Monitoring
4.1. Administration Cockpit
4.2. Information Lifecycle Management
5. Maintaining Data Security
6. Performance Management
5.1. SAP NetWeaver BI Accelerator
5.2. Other Performance Techniques
Easy administration
for complex
Enterprise Data Warehouses
using the BI
Administration Cockpit
Monitoring of
multiple BI systems
in one view
Flexible filtering of
relevant information Graphical display
Main enhancements
New Technical Content for new and enhanced BI Statistics
New Query Runtime Statistics
Process Chain and DTP Statistics
BI Object Request and Process Status
Technical Content for direct access and analysis on persistent data
Per default, queries from the Technical Content filter on reading from
persistent InfoProviders only
Reading from Virtual Providers can be enabled on query level by customers
Technical Content on detailed and aggregated level
For Query Runtime Statistics
New maintenance for statistics data collection
Enabling statistics and selection of detail level for statistics
BI Administration Cockpit
1. Overview
2. Data Modeling
2.1. Data Warehousing Workbench
2.2. DataSource
2.3. Transformation
2.4. DataStore Objects
2.5. Modeling Data Marts
3. Data Flow Design
3.1. Data Transfer Process
3.2. Process Chains
4. Administration & Monitoring
4.1. Administration Cockpit
4.2. Information Lifecycle Management
5. Maintaining Data Security
6. Performance Management
5.1. SAP NetWeaver BI Accelerator
5.2. Other Performance Techniques
Analytic Engine
BI Accelerator
Monitoring / Administration
Aggregation Security
Meta Data Repository / Documents
DataSource / PSA
Source Systems
© SAP 2007 / Page 74
Data-Aging Strategies – Initial Steps
Frequently read /
changed data
BI
Data Warehouse
Architected
Data Marts
Operational
Data Store
(volatile)
NLS Engine
Data Warehouse Layer
BIA Engine
(historical) NLS
InfoProvider
InfoCubes
DataStore-Objects
• Multidimensional Model
• High Performance Capabilities
• High Volume Capabilities
• Optimized TCO
BI
InfoCube
Offline Archive
BIA NLS
Indexing Archiving
Staging
RDBMS
BI
InfoCube
Offline Archive
BIA Engine
NLS
RDBMS
BI
Adjoint InfoProvider
InfoProvider
RDBMS
• timeslices + dimensions
• ADK, ADK/NLS, NLS
BI • new process type in
ProcessChains
Data Mart
• flexible for structural changes
BIA Engine • Archive and deleteNLSinEngine
one LUW
Indexing • write protection for removed
areas in Data Store objects
EDW DAP
DTP DTP
PSA
Sources
© SAP 2007 / Page 80
The Near-Line Storage Solution for
SAP NetWeaver BI
Near-Line Storage
Separation of frequently used data and rarely used data via Admin Cockpit
capabilities
NLS support for InfoCubes and DataStore objects
Transparent access to „non-archived“ and „archived“ data for queries
Open interface for certified partners
Development partners
PBS Software – CBW®
FileTek – StorHouse®
OuterBay - LiveArchive®
SAND-Technologies - Searchable Archive®
Selection Schema
Time-Slice Archiving
relative archiving periods, delta oriented,
DSO and compressed InfoCube,
range protection for incoming data
Pure Request-based
for uncompressed InfoCubes
Flexible Selections
Online DB Archive
© SAP 2007 / Page 82
no support for periodic processing
Agenda
1. Overview
2. Data Modeling
2.1. Data Warehousing Workbench
2.2. DataSource
2.3. Transformation
2.4. DataStore Objects
2.5. Modeling Data Marts
3. Data Flow Design
3.1. Data Transfer Process
3.2. Process Chains
4. Administration & Monitoring
4.1. Administration Cockpit
4.2. Information Lifecycle Management
5. Maintaining Data Security
6. Performance Management
5.1. SAP NetWeaver BI Accelerator
5.2. Other Performance Techniques
Authorization
Authorization
Authorization Check ok
Query results will be shown if
query selection is a proper
subset of the authorization Query
Selection
Authorizations
Authorization Check not ok
Query results will not be shown at all (‘not authorized’)
– even if parts of the authorizations are met
Query
Selection
Authorizations
Before restricting
authorizations on
characteristics, you have
to mark them as
authorization-relevant.
A group of users is
authorized only to specific
sales organizations (e.g.
Berlin and Birmingham)
(Berlin)
(Birmingham)
Possible Values
EQ: single value
BT: range of values
CP: contains (simple) patterns ending with ‘*’ or ‘+’
(e.g. XY*)
© SAP 2007 / Page 88
Authorizing Navigational Attributes – 1 –
Special authorizations
* (asterisk): denotes a set of arbitrary characters
+ (plus): denotes exactly one character (e.g. 01.++.2005 until 10.++.2005 : allows
access only the first 10 days of each month in 2005 - only available for time
validity (0TCAVALID))
: (colon): allows only aggregated access to data (e.g. allows information on all
sales areas only on aggregated level – not on particular countries)
Check of Authorizations
Selection of query will be checked against the union of the authorizations
Example:
One authorization grants access to cost center 1000 for year 2004, a second
one grants access to the same cost center for year 2005
Access to a query selection with cost center 1000 and years 2004 and 2005 will
be granted
Cost
Year 2005
Year 2004
Center
CC 1000
Year
Note: In the former concept of authorization objects, the query selection had to
be in the intersection of the two authorization object if the authorization should
be checked (i.e. the mentioned query was not authorized)
Migration Support
ABAP program RSEC_MIGRATION (use transaction SA38)
No complete, automatic migration, but support
About 80% automatic migration expected
The more complex the existing authorization concept, the more manual
migration work might be necessary
Customer-exit variables for 0TCTAUTHH cannot be migrated; the respective
hierarchy nodes must be assigned manually
Intensive tests are highly recommended
Singular event, not for scheduling
During migration to the new authorization concept, the existing concept won‘t be
changed
1. Overview
2. Data Modeling
2.1. Data Warehousing Workbench
2.2. DataSource
2.3. Transformation
2.4. DataStore Objects
2.5. Modeling Data Marts
3. Data Flow Design
3.1. Data Transfer Process
3.2. Process Chains
4. Administration & Monitoring
4.1. Administration Cockpit
4.2. Information Lifecycle Management
5. Maintaining Data Security
6. Performance Management
5.1. SAP NetWeaver BI Accelerator
5.2. Other Performance Techniques
Increasing number
Quick and easy
of information
scalability
workers
Additional Reduce
Administration cost of operation
effort significantly
Queries Queries
SAP NetWeaver
Business BI Accelerator
Intelligence
DBMS
X
Database
1. Overview
2. Data Modeling
2.1. Data Warehousing Workbench
2.2. DataSource
2.3. Transformation
2.4. DataStore Objects
2.5. Modeling Data Marts
3. Data Flow Design
3.1. Data Transfer Process
3.2. Process Chains
4. Administration & Monitoring
4.1. Administration Cockpit
4.2. Information Lifecycle Management
5. Maintaining Data Security
6. Performance Management
5.1. SAP NetWeaver BI Accelerator
5.2. Other Performance Techniques
Aggregates
Pre-aggregated (sub-)InfoCubes
Alternative to SAP NetWeaver BI Accelerator
Month Revenue
July 30
August 30
Aggregate
Query Cache
Stores query results in cross-transactional application buffer
Re-use of similar query results – also for other users
Can be actively used for performance improvement pre-load the cache via
information broadcasting
Query Cache
Aggregates or
SAP NetWeaver BIA
InfoCube
(if BIA is used, InfoCube data on database is not read)
Modeling options
MultiProvider (semantic) partitioning
Line-item dimensions
Database features
Indexing
Database Statistics
Compression
Move data from F to E fact table
Compression usually reduces the number of records by combining records with
the same key that has been loaded in separate requests
When dealing with non-cumulative key figures, it is highly recommended to
regularly compress (also when using SAP NetWeaver BI Accelerator)
Double fact table
As InfoPackages are added, F
“F” Table
Up fact table partitions are created
– Request Information loa
d
– Typically small F - Table
– Optimised for Loading
REQUEST No. Time Material Sales
and Deleting
“E” Table
Compression Fact Table
– Optimised for Queries
– Typically large E - Table
– User-defined DB Partitioning REQUEST No. Time Material Sales
(depending on the DBMS)
– But: no information on requests
© SAP 2007 / Page 105
Copyright 2007 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.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge 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 in several other countries all over the world. All other product and service names mentioned and
associated logos displayed are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.
The information in this document is proprietary to SAP. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document
contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy,
and/or development. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or
other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of
merchantability, fitness for a particular purpose, or non-infringement.
SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation
shall not apply in cases of intent or gross negligence.
The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these
materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages
Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch
SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden.
Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte können Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwähnte SAP-Produkte und Services
sowie die dazugehörigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Ländern weltweit. Alle anderen in diesem Dokument erwähnten
Namen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu
Informationszwecken. Produkte können länderspezifische Unterschiede aufweisen.
Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderen
Vereinbarung mit SAP. Dieses Dokument enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts und ist für SAP nicht bindend, einen bestimmten
Geschäftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht die
Richtigkeit oder Vollständigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewähr, weder
ausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zweck
sowie für die Gewährleistung der Nichtverletzung geltenden Rechts.
SAP übernimmt keine Haftung für Schäden jeglicher Art, einschließlich und ohne Einschränkung für direkte, spezielle, indirekte oder Folgeschäden im Zusammenhang mit der Verwendung
dieser Unterlagen. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit.
Die gesetzliche Haftung bei Personenschäden oder die Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinks
zugreifen, unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen über
Internetseiten Dritter ab.
Alle Rechte vorbehalten.