SAP Net Weaver

I T Sc enar i o Over vi ew
<i nser t sc enar i o name>
BPC 7.x St at us & NW
I nt egr at i on Over vi ew
DRAFT CONFI DENTI AL
SAP AG 2007, 2
Saf e Har bor
This document is intended to outline future product
direction, and is not a commitment by SAP to deliver any
given code or functionality. Any statements contained in
this document that are not historical facts are forward-
looking statements. SAP undertakes no obligation to
publicly update or revise any forward-looking statements.
All forward-looking statements are subject to various
risks and uncertainties that could cause actual results to
differ materially from expectations. The timing or release
of any product described in this document remains at the
sole discretion of SAP. This document is for informational
purposes and may not be incorporated into a contract.
Readers are cautioned not to place undue reliance on
these forward-looking statements, and they should not be
relied upon in making purchasing decisions.
Agenda
High Level Architecture & Landscape
Functional Overview
Detailed Functionality & Implementation
Transports Overview
Status & Timeline for BPC 7.x
Terminology & Definitions
Agenda
High Level Architecture & Landscape
Functional Overview
Detailed Functionality & Implementation
Transports Overview
Status & Timeline for BPC 7.x
Terminology & Definitions
SAP AG 2007, 5
Mi c r osof t Obj ec t s vs SAP Obj ec t s
SAP AG 2007, 6
Mappi ng t he Tool s w i t h t he Pl at f or m
This diagram is a good starting point to understanding some of the same terms used and leveraged
within SAP BPC and how they correlate to NetWeaver.
Below is a diagram which draws dotted lines between SAP BPC 5.1 objects and SAP BI objects.
These correlations are my own and have helped me understand quickly SAP BPC and the
environment in which it runs.
SAP AG 2007, 7
Mappi ng OLAP Obj ec t s
1. A Property is an attribute but SAP BPC has a feature by which you can flag a property as inApp
which is similar to Navigational Attributes.
2. A Hierarchy in SAP BPC is not the same thing as a BI Hierarchy. A BPC Hierarchy is conceptially
like an Attribute within the master data table of a Characteristic InfoObject. Technically, it is more
than that in Analysi s Services, even though not in SQL Server.
Agenda
High Level Architecture & Landscape
Functional Overview
Detailed Functionality & Implementation
Transports Overview
Status & Timeline for BPC 7.x
Terminology & Definitions
SAP AG 2007, 9
SAP
BPC Rel eases by Dat e
2008
Today
27
J une
2008
~Dec
2008
BPC 5.x
BPC 7 BPC 7 M
BPC 7.5 BPC 7.5 M
Microsoft based
SAP based
SAP AG 2007, 10
SAP
BPC 7 Maj or Sc ope Changes
In Scope Out of Scope
- Major architectural changes to remove
Microsoft dependencies and integrate to
NetWeaver BI and BIA
- ABAP A/S is now where most logic is
run: 64-bit, database independent, etc
- New validations engine (replacing
Journals only validations)
- Transports / Lifecycle Management
- Statistics framework for monitoring
performance
- Remote debugging capability
- Planned: client able to access multiple
systems; vastl y increased dimensions &
members
- BPFs (new functionali ty, so limited customer
adoption biggest loss is for sales / demos)
- Books (Distributor/Collector functionality
included in scope, but Books are out)
- Drill-Through (will investigate workarounds
with RIG)
- Dynami c Hi erarchy Editor (workaround using
normal Excel input templates)
- Custom Menus (intended to be replaced by
BPFs when BPFs are fully functional)
- Insight (only impacts a few customers and
sales/demos)
- SQL Logic in K2 Scripts (MDX Logic & ABAP
available)
SAP AG 2007, 11
SAP
BPC 7
Where are we?
All of these changes have been implemented with less
than six months of development!
Dev Close is 21
st
March. Going to be close, but we are
on track to reach this milestone
Able to get the first build out this week, where you can
use the BPC clients without any SQL Server/Analysis
Services dependencies.
This is coming late, but it was a significant effort to
get to this point as all client initialization functions
had to be provided from ABAP before this could
happen, and they had all sorts of dependencies on
other modules.
SAP AG 2007, 12
SAP
BPC 5.x
Web Server (IIS) & .NET Application Server
Client
Web Services
MS Offi ce
Clients
Admin Web
Platform Services
Application Services
Data
OLAP (MSAS)
HTTP/SOAP
MDX UNC SQL
Others
Relational Database
(MS SQL Server)
File Share
Server side
Requirements
MS SQL Server
MS Anal ysis
Servi ces
MS Reporting
Servi ces
MS DTS (or SSIS)
.NET 1.1 A/S
Web Server (IIS)
Fil e Share
SAP AG 2007, 13
SAP Busi ness Pl anni ng and Consol i dat i on 5.0 Tec hni c al
Ar c hi t ec t ur e
.NET
DB Access
Thin Client
Persistency
Application Services Utilities
PlatformServices
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 Reporting
Services
R
Local File
Store
Logging
Data Mgmt.
Audit
Configuration Admin
Shared Query
Engine
Comments WorkStatus
Metadata
Email
User Mgmt.
Insight
J ournal
LiveUpdate
BPF
Content LiveReport
Session Publish
Write Back
Web Services
DB
Connection
Factory
Admin Configuration
Send
Govenor
BPF ... WorkStatus
Rich Clients
Admin
ActionPane
Browser
HTTP/SOAP
WebUI
(ASP.NET)
R
Logic
Script Logic
HTTP
Source
Systems
R
BPC for Excel
ActionPane
BPC for Word
ActionPane
BPC for PP
ActionPane
R R
R
R
R
R
R
Logic
Stored
Procedures
R
R
R
R
R
SAP AG 2007, 14
SAP
BPC 7
Server side
Requirements
NW BI (ABAP A/S &
OLAP Engine)
Any Database
.NET 1.1 A/S
Web Server (IIS)
What was removed?
No MS Reporting
Services
No MS DTS/SSIS
No MS Anal ysis
Services
Database agnostic
~85% processing to
ABAP (not .NET 1.1)
All files stored in DB
SAP AG 2007, 15
SAP Busi ness Pl anni ng and Consol i dat i on 7.0 Tec hni c al
Ar c hi t ec t ur e
ABAP
BPC ABAP Function Modules BPC Data Access Objects
SAP BPC (.NET)
ApplicationServices
Source
Systems
Database
BPC
Customizing
InfoProvider BI Metadata
BI
Masterdata
BPC App
Services
BPC Audit ...
ThinClient
Web Services
Admin Configuration BPF ... WorkStatus
Browser
HTTP/SOAP
WebUI icl.
Reporting
(ASP.NET)
R
HTTP
ApplicationServices Proxies Utilities
PlatformServices
Scheduling
Proxy
File Service
ZIP, XML,
Chart, etc.
Local File
Store
Logging Data Mgmt.
Audit Configuration
Admin
SharedQuery
Engine
Comments
WorkStatus
Metadata Email
User Mgmt.
Insight
J ournal
LiveUpdate
BPF
Content
LiveReport
Session Publish
Write Back
Logic Proxies
Script Logic
Parameter-
driven Logic
Unstructured
Docs
Audit Configuration
Admin
Shared Query
Engine
Comments WorkStatus
Metadata Email User Mgmt.
Insight
J ournal
LiveUpdate
BPF
Content
LiveReport
Session
Publish Write Back
SAP BI (ABAP)
MDX IF BI ETL
BI BAPIs RSDRI IF
Process
Chains
Logic
Script Logic
Logic
Modules
ABAP Basis
ABAP Batch
Scheduler
R
DAO Proxies
R
File Service
Proxy
HTTP/RFC HTTP/RFC
Data Mgmt.
Data Mgmt.
Process
Components
SAP Connect
(Email)
RichClients
Admin
ActionPane
BPC for Excel
ActionPane
BPC for Word
ActionPane
BPC for PP
ActionPane
R
R
R
R
R
R
R
R
R R
R
R
R R
SAP AG 2007, 16
Separ at e Namespac e f or BPC Gener at ed Obj ec t s
InfoCube
/CPMB/IXXIC1
InfoObject
/CPMB/XXIO01
All BPC Objects will be stored in the /CPMB/ namespace
BPC will not be able to create objects in the EDW Namespace
All BI Objects within the /CPMB/ namespace have generated technical
names (no technical names exposed to user in BPC)
MultiProvider
/CPMB/MXXIC1
Technical Pre-requisites:
BPC .NET Server
Windows Server 2003:
MS IIS
.NET 1.1
MS XML 3.0
ABAP:
SAP AG 2007, 17
4 Cust omer I mpl ement at i on Opt i ons
Option 1 Fully Utilize BPC Admin Console
Within this Option, Actual and Plan Data are stored in a single cube
within the BPC namespace
Option 2 - Utilize Logical Partitioning for BPC Cubes
Within this option, you will do the initial configuration within BPC,
but can utilize BI Admin Workbench for more technical operations
Option 3 Utilize Actuals and Plan in Separate Cubes
Within this option, you will do the initial configuration within BPC,
but can utilize BI Admin Workbench for more technical operations
Option 4 Dont Replicate EDW Actuals
Within this option, you will do the initial configuration within BPC,
but can utilize BI Admin Workbench for more technical operations
NOTE: If you use the BI Administrator Workbench (RSA1) to create
any partitioned cubes, you will have to manually maintain these
cubes. You cannot use the BPC Admin Console on these cubes.
BPC Admin Console only works on cubes created within the BPC
Admin Console. Option 1 is supported by BPC. Option 2, 3, and 4 are
customer implementations and the responsibility of customers.
SAP AG 2007, 18
Opt i on 1 Ful l y Suppor t s Osof t Admi n Consol e
Generated
FinanceApplication
Generated
MultiProvider
ApShell
Generated
Finance BIQuery
Data is Stored Here
Persistency
No Data is Stored Here
(Virtual Layer)
No Data is Stored Here
(Virtual Layer)
Supports Osoft
Change
Changed directly in
BPC Admin Console
Application Mgmt
Changed directly in
BPC Admin Console
Application Mgmt
Changed directly in
BPC Admin Console
Application Mgmt
All Data
SAP AG 2007, 19
Generated
FinanceApplication
Generated
MultiProvider
ApShell
Generated
Finance BIQuery
Opt i on 2 Ut i l i ze Logi c al Par t i t i oni ng f or BPC Cubes
Data is Stored Here
Persistency
No Data is Stored Here
(Virtual Layer)
No Data is Stored Here
(Virtual Layer)
Supports Osoft
Change
Only One Cube is
managed through
Osoft, and others are
done through Manual
BI Work
Changed directly in
BPC Admin Console
Application Mgmt
Changed directly in
BPC Admin Console
Application Mgmt
2005 Data
(locked)
2007 Data 2006 Data
(locked)
These cubes are created through NW BI and copied from the generated
BPC Cubes using RSA1 and manually attached to the MultiProvider.
Anytime a change is made using the BPC Admi n Console, the logi cally
partitioned cubes wi ll need to be manually maintained and added to the
MultiProvider using NW BI (RSA1). All Previous year data is moved from
the Generated BPC cube to previous year cubes using BI ETL.
SAP AG 2007, 20
Generated
FinanceApplication
Generated
MultiProvider
ApShell
Generated
Finance BIQuery
Data is Stored in both EDW
Actuals Cube as well as
BPC cube
Persistency
No Data is Stored Here
(Virtual Layer)
No Data is Stored Here
(Virtual Layer)
Supports Osoft
Change
Only One Cube is
managed through
Osoft, and others are
done through Manual
BI Work
Changed directly in
BPC Admin Console
Application Mgmt
Changed directly in
BPC Admin Console
Application Mgmt
EDW
Actuals Cube
Plan Actuals Data
The BPC Actuals cube is created through NW BI and copi ed from the
generated BPC Cubes using RSA1 and manuall y attached to the
MultiProvider. Anytime a change is made using the BPC Admi n Console,
the BPC Actuals cube wi ll need to be manually maintai ned and added to
the MultiProvider using NW BI (RSA1).
COPY DATA
Opt i on 3 Ut i l i ze Ac t ual s and Pl an i n Separ at e Cubes
SAP AG 2007, 21
Generated
FinanceApplication
Generated
MultiProvider
ApShell
Generated
Finance BIQuery
Opt i on 4 Dont Repl i c at e EDW Ac t ual s
Data is Stored in both EDW
Actuals Cube and virtually
read into BPC cube (not
copied)
Persistency
No Data is Stored Here
(Virtual Layer)
No Data is Stored Here
(Virtual Layer)
Supports Osoft
Change
Only One Cube is
managed through
Osoft, and others are
done through Manual
BI Work
Changed directly in
BPC Admin Console
Application Mgmt
Changed directly in
BPC Admin Console
Application Mgmt
EDW
Actuals Cube
Plan Actuals Data
The BPC Actuals cube is a vi rtual provider that is created through NW BI
and has the same structured as the generated BPC Cubes using RSA1 and
manual ly attached to the MultiProvider. Anytime a change is made using
the BPC Admin Console, the BPC Actuals Virtual Provider wil l need to be
manuall y maintained and added to the MultiProvider using NW BI (RSA1).
Virtuall y Read
SAP AG 2007, 22
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, 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, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or
registered trademarks of IBM Corporation 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.
J ava is a registered trademark of Sun Microsystems, Inc.
J avaScript 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 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 are the trademarks of their respective
companies. Data contained in this document serves informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies
("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be
liable for errors or omissions with respect to the materials. The only warranties for SAP Groupproducts and services are
those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing
herein should be construed as constituting an additional warranty.
Copyr i ght 2007 SAP AG. Al l Ri ght s Reser ved.