BPC Technical Architecture and Data Integration

8/3/2019 BPC Technical Architecture and Data Integration

http://slidepdf.com/reader/full/bpc-technical-architecture-and-data-integration 1/49

Techn ica l Arch i t ec t u re Overview – SAP BPC



Agenda – Presentat ion Purpose

Provide an overview of the technology components that comprise the BPC platform Today.

Explain how components can be mixed to design an effective infrastructure of a BPC deployment with Version 5.

Discuss the factors that influence configuration decisions

Identify the hardware and software requirements for the most common configurations

Explain the BPC security components

List the types of BPC users and the client components required for each

Highlight the importance of a development environment

High Availability and Disaster Recovery

The Next Generations



BPC High Level Archi t ec t ure

Vers ion 5



Presentat ion Purpose

Presentation Purpose

Web-based platform with centralized database.

Designed for scalability to thousands.

Zero-footprint, Web-based application leveraging cutting-edge technologies

Next generation Service-Oriented Architecture (SOA) providing easy integration.

Patented, enterprise-scale Microsoft Office integration.



Server Technology Stac k

•Microsoft SQLServer – Enterprise Edition2005 relationaldatabasecomponent

•Supports datamanagementactivities

•100% Open

Standard

• Can be 64 bitwhen separatefromApplication/webservices

SQLServices

•Microsoft SQL2005 ReportingServices

•Powerfulrelational reportgenerator

•Supports Journal,Audit and otherreportingcapabilities

•Can be 64 bitwhen separatefromApplication/webservices or IISinstalled

ReportingServices

•Storage location forall application files,UNC or local drive.

•Book Repository

•Templates

•Unstructured Data

•Conversion &Transformation Files

FileServices

•Microsoft IIS

•Uses SOAP(Service OrientedApplicationProtocol) calls forcommunicationusing XMLbetween web andapplication server.

•Host for ZFP

(Zero footprint)Pages

•Performs userauthentication

WebServer

•Microsoft IIS

•Supports all SOA(Service OrientedArchitecture)

•Collection of BPCServices

•Where BPCApplicationBusiness Logic

Resides•Performs userauthentication

ApplicationServices

•Microsoft SQLServer – Enterprise Edition2005 multi-dimensionaldatabasecomponent

•Provides detailedanalysis & drilldown

•Can be 64 bitwhen separatefromApplication/webservices

AnalysisServices



Fact ors Af fec t ing Ins ta l la t ion

SQL Licensing Requirements … SQL

SQL SQL SQL

SQLServices

ReportingServices

FileServices

WebServer

ApplicationServices

AnalysisServices

EE

Where IIS is Located … IIS

IISIIS IIS



BPC Appl icat ion Tiers

Web Tier

User Interface for BPC Web, Insight

Application Tier

XML services, Business Logic, Shared Query Language

Database Tier

Relational and multi-dimensional data store



Why Single Serve r

When the number of concurrent users is low

If you are setting up a development environment

If there are no requirements for separating the MS IIS component from the SQL Database component

If the server is in a Workgroup not a Domain

No requirements for High Availability (clustering)



Why a Mult i Server

When the number of concurrent users is high

Corporate policies dictate separating certain components – (e.g. IIS and SQL must not share the same server)

Need to separate functional components according to corporate departmental structure

Web Services must be hosted in a DMZ

Database Services must be hosted internally



Single Server Conf igurat ion

SQLServices

ReportingServices

FileServices

WebServer

ApplicationServices

AnalysisServices

EE

SQL

Services

Reporting

Services

File

Services

Web

Server

Application

Services

Analysis

ServicesEE



Sam ple Single Server Guidel ines

OS–RAID 1

Data–RAID 1+0

OS–RAID 1

Data–RAID 1+0

RAID 5RAID 5RAID Level

Recommended Recommended

Contact an BPC Certified Technical Consultant

for more information

Windows 2003 Enterprise Edition SP2/R2 (32 bitonly)

SQL Server 2005 Standard/Enterprise Edition or

Developer’s Edition, Runtime Licensing Supported

Windows 2003 Standard and Enterprise EditionSP2/R2 (32 bit only)

SQL Server 2005 Enterprise Edition or Developer’s

Edition 32 bit only, Runtime icensing supported

OS

MinimumMinimum

144 GB72 GB72 GB36 GBDisk GB

8 GB4 GB4 GB2 GBRAM GB

4 Dual Core442CPU’s

Development Environment Production Environment



Mult i Server Conf igurat ion

SQLServices

ReportingServices

FileServices

WebServer

ApplicationServices

AnalysisServices

EE

Web TierWeb Services & Reporting Services

Application Services & File Share

SQL Services & Analysis Services

Application Tier

Database Tier



Sam ple Tier Centr i c Server Guidel ines

Windows 2003 Enterprise Edition SP2/R2Windows 2003 Standard and Enterprise EditionSP2/R2

OS

OS – 1 Data -1+0

11511RAID Level

1447236723636Disk GB

842222RAM GB

4 Dual Core2 Dual Core2 Dual Core2 Dual Core22CPU’s

DB Tier

Can be 64 bit

App TierWeb TierDB Tier

Can be 64 bit

App TierWeb Tier

RecommendedMinimum



Multi Server Configuration – Web Centric

Web Centric -separates SQLrelational

database fromweb services

Reporting Services, File Share,Application Server and Webserver

Database Server and AnalysisServices and Reporting ServicesDatabase

SQLServices

ReportingServices

FileShare

WebServer

ApplicationServer

AnalysisServices

EE



Multi Server Configuration – Database Centric

Database Centric- separates all

database services

from web/file/appservicesFile Share, Reporting Services,Application Server and Webserver

DB Server, RS Database andAnalysis Services Server

SQLServices

ReportingServices

FileShare

WebServer

ApplicationServer

AnalysisServices

EE



Multi Server Configuration – Database Centric

Database Centric- separates all

database services

from web/file/appservicesFile Share, Application Server andWebserver

DB Server, RS Database and WebPart and Analysis Services Server

SQLServices

ReportingServices

FileShare

WebServer

ApplicationServer

AnalysisServices

EE



Conf igurat ion Opt ions nnn

Several other effective multi server configurations are possible.

Use Technical Consulting to help you determine the optimal configuration for the client.

SQLServices

ReportingServices

FileServices

WebServer

ApplicationServices

Analysis

ServicesEE



Tier Authent ic a t ion

1. Client Web Server

Currently supported using windows (BASIC, NTLM, Kerberos) authentication

2. Client Application Server

Currently supported using windows (BASIC, NTLM, Kerberos) authentication

3. Application Server BPC System Resources

(SQL services, Analysis services, & File Services). Application Server uses service-level accounts to access resources



Types o f Authent ic a t ion

Domain

Users

Is Transparent Authentication or SSO a requirement?

Do you support Active Directory?

Will users log into BPC with their Domain ID?

Do users log into their local machines with a Domain ID?

Are all your users in one domain or many

Do you have external users not part of your domain?

BPC

Users



Authent ic a t ion Mat r ix

Windows ids for

each user

Existing LDAP server we can readWindows ids for each user.

Requires proper Kerberossetup - servers all in same

domain & trusted for

delegation. Users must betrusted, BPC web sites

trusted

Windows ids for each userPrerequisites

YesYesYesYesRequires 1-3 windows service-like accounts (Windows

UserIDs for COM+ Components - sysadmin/admin/user)

YesYesYesYesWorks in multi-server environment

YesYesNoMust use BasicWorks over internet (non-VPN)

YesNoYesYesRequires Windows ID

Yes unless usehttps for all pages

Yes unless use https for login pageNoNoPassword sent in clear text

YesYesOnly if switch to anotherauthentication mode

Yes, if use BASICAlternate userid

LowMedHigherHighRelative security

BasicLDAPKerberosWindows IntegratedSecurity features:

Authentication Mode:



Cl ient Hardw are Requi rement s

NIC 100 MBit

SVGA 800 x 600

Other

1 GB500 MB150 MBHard Drive

512 MB >512 MB >256 MB >RAM

x86 (1.6 GHz >)x86 (1.4 GHz >)x86 (600 MHz >)CPU

Admin UserPower UserStandard User



Cl ient Soft w are Requi rement s

Window XP SP1 (or later), Vista not yet supported

Internet Explorer 6.0 SP1 (or later)

Microsoft Office

Office XP SP2 (or later)

Office 2003 SP3 (or later) Office 2007

Microsoft XML 3.0 SP1 (or later)

Microsoft .NET Framework 1.1

PDF Reader (optional)



Why a Developm ent Environm ent

A development environment is an integral part of a successful implementation. It provides anenvironment for:

Testing third party software updates: Windows, SQL, Analysis Services, Reporting Services

Can be used as a staging area for new BPC releases that require conversions

Testing BPC application set design changes

Environment to develop future BPC applications/ application sets

Provides Fail Over and/or Disaster Recovery hardware

Reduces potential impact on production users resulting from any of the above activities

***Production and Development environments do not have to be identical in hardware or configuration***



Comm on Cl ient Sc enar ios

3 Environments

Test / Dev

UAT (User Acceptance Testing Environment)

Production




3 Environments

Test / Dev

Single server or partner hosted

Can be virtualized


Mirrors production

Production

Should run only production appsets

Highly recommended to be physical servers




3 Environments

Test / Dev


Production



Disast er Rec overy vs High Avai lab i l i ty

Disaster Recovery is the ability to restore the system back to working order in a timely manner.

Includes the recovery of data, hardware, and software

Includes a DR plan with a time specified for maximum acceptable recovery time

High availability is the automatic failover of the system.

Includes identical replicas of complete database and application servers with continuous real-time failover

Should a server fail or have to be shut down for maintenance a synchronized replica will instantaneously and automatically

take its place to ensure continuous application availability and business continuity



Disaster Rec overy Possib i l i t i es

Use Development Environment as a DR Environment

Your decision is then based on sizing – an exact replica or less performance and access for the time it takes to recover.

Use Backups

You need to see how often you need to backup based on the time frame you need to meet.

SQLServices

ReportingServices

FileServices

WebServer

ApplicationServices

AnalysisServices

EE



High Avai lab i l i ty Possib i l i t ies

Complete Redundancy for each component in the BPC 5 Technology Stack

Microsoft SQL Server 2005

Microsoft Analysis Services 2005

Microsoft Reporting Services 2005

BPC Application Services

BPC File Share

BPC Web Services



High Avai lab i l i t y for Mic rosof t SQL Server

Microsoft SQL Server 2005 Clustering

SQL Server 2005 Failover Clustering. Can be 64 bit when separate from web/application tier

Minimum of 2 node cluster, maximum number of nodes dependent on operating system (Windows 2003 STD vs. ENT)

Microsoft Recommends Clustering for data protection and high availability

SQLServices

SQLServices

SAN



High Avai labi l i t y for Mic rosof t Analys is

Servic es 2005

Microsoft Analysis Services 2005 Clustering

SQL Server 2005 Failover Clustering. Can be 64 bit when separate from web/application tier

Minimum of 2 node cluster, maximum number of nodes dependent on operating system (Windows 2003 STD vs. ENT)

Microsoft Recommends Clustering for data protection and high availability

AnalysisServices

AnalysisServices

SAN



High Avai labi l i t y for Mic rosof t Repor t ing

Servic es 2005

Microsoft Reporting Services 2005 Load balancing – all nodes active

Support many third party load balancing solutions, for example:

Microsoft Network Load Balancing

F5 Big IP

Cisco

ReportingServices

ReportingServices

Load balancing device



High Avai lab i l i ty for BPC Applic at ion Serv ices

BPC Application Services Load balancing – all nodes active



F5 Big IP

Cisco

ApplicationServices

ApplicationServices




High Avai l abi l i t y for BPC Web Servic es

BPC Web Services Load balancing – all nodes active



F5 Big IP

Cisco

WebServer

WebServer




HA Mul t iServer Env i ronment

Example


Application

Server, ReportingService andWeb Tiers

SAN

Database Tiers



Architecture Roadmap of Next-GenerationCPM Solutions

Requirements for Next-Generation CPMSolutions

What’s Next?



SAP BPC 5 Technic al Archi t ect ure

.NET

DB Access

Thin Client

Persistency

Application Services Utilities

Platform Services

RDBMS(SQL Server)

MOLAP(Analysis Server)

MD Store

Star Schema

DTS/SSIS

File Server

ADODB ADOMD

R R

OLAP Admin

Scheduling

File Service

Rel. Store(meta data,

etc.)

SQL MDX

ZIP, XML,Chart, etc.

MS ReportingServices

R

Local FileStore

Logging

Data Mgmt.

Audit

ConfigurationAdmin

Shared QueryEngine

CommentsWorkStatus

Metadata

Email

User Mgmt.

Insight

Journal

LiveUpdate

BPF

ContentLiveReport

SessionPublish

Write Back

Web Services

DBConnection

Factory

Admin Configuration

SendGovenor

BPF ...WorkStatus

Rich Clients

Admin

ActionPaneBrowser

HTTP/SOAP

WebUI(ASP.NET)

R

Logic

Script Logic

HTTP

SourceSystems

R

BPC for Excel

ActionPane

BPC for Word

ActionPane

BPC for PP

ActionPane

R R

R

R

R

R

R

Logic

StoredProcedures

R

RR

R

R



ABAP

BPC ABAP Function Modules BPC Data Access Objects

SAP BPC (.NET)

Application Services

SourceSystems

Database

BPCCustomizing

InfoProvider BI MetadataBI

Masterdata

BPC AppServices

BPC Audit ...

Thin Client

Web Services

Admin ConfigurationBPF ...WorkStatus

Browser

HTTP/SOAP

WebUI icl.Reporting

(ASP.NET)

RHTTP

Application Services Proxies Utilities

Platform Services

Scheduling

Proxy

File Service

ZIP, XML,Chart, etc.

Local FileStore

LoggingData Mgmt.

AuditConfiguration

Admin

Shared QueryEngine

Comments

WorkStatus

MetadataEmail

User Mgmt.

Insight

Journal

LiveUpdate

BPF

Content

LiveReport

Session Publish

Write Back

Logic Proxies

Script LogicParameter-driven Logic

UnstructuredDocs

AuditConfiguration

Admin

Shared QueryEngine

CommentsWorkStatus

MetadataEmailUser Mgmt.

Insight

Journal

LiveUpdate

BPF

Content

LiveReport

Session

PublishWrite Back

SAP BI (ABAP)

MDX IFBI ETL

BI BAPIs RSDRI IFProcessChains

Logic

Script LogicLogic

Modules

ABAP Basis

ABAP BatchScheduler

R

DAO Proxies

R

File ServiceProxy

HTTP/RFC HTTP/RFC

Data Mgmt.

Data Mgmt.Process

Components

SAP Connect(Email)

Rich Clients

Admin

ActionPane

BPC for Excel

ActionPane

BPC for Word

ActionPane

BPC for PP

ActionPane

R

R

R

R

R

R

R

R

R RR

R

RR

SAP BPC 7.0 Tech nica l Archi t ec tur e



SAP St rat egy Management 2007 Technic al

Arch i tec tu re

Browser interface thin clientExcel interface via Wininet.dllDiagram strategy manager via .net

MS IIS

PIP (.Net)

Java (JBoss)

EJBWeb

PAS (.NET and Linux/UNIX)

JakartaISAPI Filter

PilotWorksWeb

R

PilotAdministrator

.NET

HTTP TCP/IP

TCP/IP

PASListener

Pilot DB

SQLite

R

Work DB OLAP DB

MSUsermgmt.

R

PIP

Listener

Storedprocedures

JPIP

AUTH

PilotWorksCore

PilotWorksConsole

PilotWorksExt

Excel

PilotWorksSrv

PilotWorksStatic Content

LDAPServer

Users

R

MS Store

(pipadmin)

R

RTCP/IP

DataWarehouse

MDDB

R

ODBC /ODBO

RTCP/IP

R R

R

Browser

R

PilotWorksConfig

RR

DiagramManager

R

MS IIS•static pages•authentication•redirection of dynamic contents

JBoss

•application business logic•common services•authorization•interface with data tier

Pilot Interactive Publisher

•relational connection pooling•PAS connection pooling•result caching

Pilot Application Server•KPI data store•OLAP engine

•Data warehouse interface



SAP St rat egy Management 7.0 Tec hnical

Arch i tec tu re

NW AS Java

NW AS Database

PIP (.NET and Linux/UNIX)

PAS (.NET and Linux/UNIX)

PilotWorksWeb

R

Pilot Administrator.NET

HTTP TCP/IP

PASListener

Pilot DB

Work DB OLAP DB

PIP Listener

Storedprocedures

JPIP UME

PilotWorksCore

Excel withplug-in

PilotWorksSrv


LDAPServer

Users

RTCP/IP

SAP BI

Database

R

MDX over RFC/ OLAP BAPI

RTCP/IP

R

R R

R

Browser

R

PilotWorksConfig

Users

RPIP Config

WS

PIP Config

Web Server

HTTP

R


R

DiagramManager

R

IGS H T T P / X M L

Netweaver CE•application business logic•common services•authorization•interface with data tier•authentication•static content•configuration•database connection pooling•clustering

Pilot Application Server•KPI data store•OLAP engine•Data warehouse interface•Netweaver BI integration

Pilot Interactive Publisher•PAS connection pooling•result caching



Mult i -d im ensional data ac c ess



Dat a Wr i t e Back



Logic Models



Model ing of N W BI Objec t s in BPC



Conf igurat ions



Changes and Flex ib i l i t y for t he Fut ure

?



Thank You for At t ending.



Copyr ight 2007 SAP AG. Al l 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, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z,System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation.

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.MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective l ogos are trademarks or registered trademarks of SAP AGin Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document servesinformational purposes only. National product specifications may vary.

The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission ofSAP AG.

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 ofthe SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may bechanged by SAP at any time without notice.

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 item s contained within thismaterial. This document is provided without a warranty of any kind, eithe r 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 inc luding without limitation direct, special, indirect, o r consequential damages that may result from the use of th ese materials. This limitation shall notapply 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 l inks contained in these materials anddoes not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.



Copyr ight 2007 SAP AG. Al le Rec ht e

vorbehal ten

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.

Die von SAP AG oder deren Vertri ebsfirmen angebotenen Softwareprodukte können Softwarekomponenten auch anderer Softwarehersteller enthalten.

Microsoft ® , WINDOWS ® , NT ® , EXCEL ® , Word ® , PowerPoint ® und SQL Server ® sind eingetragene Marken der Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z,System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower und PowerPC sind Marken oder eingetragene Marken der IBM Corporation.

Adobe, das Adobe Logo, Acrobat, PostScript und Reader sind Marken oder eingetragene Marken von Adobe Systems Inc. in den USA und/oder anderen Ländern.

ORACLE ® ist eine e ingetragene Marke der ORACLE Corporation.

UNIX ® , X/Open ® , OSF/1 ® und Motif ® sind eingetragene Marken der Open Group.

Citrix ® , das Citrix-Logo, ICA ® , Program Neighborhood ® , MetaFrame ® , WinFrame ® , VideoFrame ® , MultiWin ® und andere hier erwähnte Namen von Citrix-Produkten sind Marken von Citrix Systems, Inc.

HTML, DHTML, XML, XHTML sind Marken oder eingetragene Marken des W3C ® , World Wide Web Consortium, Massachusetts Institute of Technology.

JAVA ® ist eine eingetragene Marke der Sun Microsystems, Inc.

JAVASCRIPT ®

ist eine eingetragene Marke der Sun Microsystems, Inc., verwendet unter der Lizenz der von Netscape entwickelten und implementierten Technologie.MaxDB ist eine Marke von MySQL AB, Schweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, und weitere im Text erwähnte SAP-Produkte und -Dienstleistungen sowie die entsprechenden Logos sind Marken oder eingetragene Markender SAP AG in Deutschland und anderen Ländern weltweit. Alle anderen Namen von Produkten und Dienstleistungen sind Marken der jewe iligen Firmen. Die Angaben im Text sind unverbindlich unddienen lediglich zu Informationszwecken. Produkte können länderspezifische Unterschiede aufweisen.

Die in dieser Publikation enthaltene Information ist Eigentum der SAP. Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer,nur mit ausdrücklicher schriftlicher G enehmigung durch SAP AG gestattet.

Bei dieser Publikation handelt es sich um eine vorläufige Version, die nicht Ihrem gültigen Lizenzvertrag oder anderen Vereinbarungen mit SAP unterliegt. Diese Publikation enthält nur vorgeseheneStrategien, Entwicklungen und Funktionen des SAP ® -Produkts. SAP entsteht aus dieser Publikation keine Verpflichtung zu einer bestimmten Geschäfts- oder Produktstrategie und/oder bestimmtenEntwicklungen. Diese Publikation kann von SAP jederzeit ohne vorherige Ankündigung geändert werden.

SAP übernimmt keine Haftung für Fehler oder Auslassungen in dieser Publikation. Des Weiteren übernimmt SAP keine Garantie für die Exaktheit oder Vollständigkeit der Informationen, Texte, Grafi ken,Links und sonstigen in dieser Publikation enthaltenen Elementen. Diese Publikation wird ohne jegliche Gewähr, weder ausdrücklich noch stillschweigend, bereitgestellt. Di es 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 haftet nicht für entstandene Schäden. Dies gilt u. a. und uneingeschränkt für konkrete, besondere und mittelbare Schäden oder Folgeschäden, die aus der Nutzung dieser Materialien entstehenkönnen. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit.

Die gesetzliche Haftung bei Personenschäden oder Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinks zugreifen, unterliegennicht 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.

BPC Technical Architecture and Data Integration

Documents

Transcript of BPC Technical Architecture and Data Integration