BPC 7x Internal NW Tech

8/12/2019 BPC 7x Internal NW Tech

1/22

SAP NetWeaver IT Scenario Overview

BPC 7.x Status NWIntegration Overview

DRAFT CONFIDENTIAL


2/22

SAP AG 2007, 2

Safe Harbor

This document is intended to outline future productdirection, and is not a commitment by SAP to deliver anygiven code or func tionality. Any statements contained inthis document that are not h istor ical facts are forward-looking statements. SAP undertakes no obligation topubl icly update or revise any forward-looking statements.

All forward-looking statements are subject to variousrisks and un certainties that could cause actual results todiffer materially from expectations. The timing or releaseof any product described in this document remains at thesole discretion of SAP. This document is for informationalpurposes and may not be incorporated into a contract.

Readers are cautioned not to place undue reliance onthese forward-looking statements, and they should not berelied upon in making purchasing decisions.


3/22


4/22

Agenda

High Level Architecture & Landscape

Functional Overview

Detailed Functionality & Implementation

Transports OverviewStatus & Timeline for BPC 7.x

Terminology & Defini tions


5/22

SAP AG 2007, 5

Microsoft Objects vs SAP Objects


6/22

SAP AG 2007, 6

Mapping the Tools with the Platform

This diagram is a good st arting poin t to understanding some of the same terms used and leveragedwithin 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 theenvironment in which it runs.


7/22

SAP AG 2007, 7

Mapping OLAP Objects

1. A Property is an attribute but SAP BPC has a feature by which you can flag a property as inAppwhich is simil ar to Navigational Attribu tes.

2. A Hierarchy in SAP BPC is not t he same thing as a BI Hierarchy. A BPC Hierarchy is conceptiallylike an Attribute within the master data table of a Characteristic InfoObject. Technically, it is morethan that in Analysis Services, even though not in SQL Server.


8/22

Agenda

High Level Architecture & Landscape

Functional Overview

Detailed Functionality & Implementation

Transports OverviewStatus & Timeline for BPC 7.x

Terminology & Defini tions


9/22

SAP AG 2007, 9

BPC Releases by Date2008

Today

7June 8

~Dec 8

BPC 5.x

BPC 7 BPC 7 M

BPC 7.5 BPC 7.5 M

Microsoft based

SAP based


10/22

SAP AG 2007, 10

BPC 7 Major Scope Changes

In Scope Out of Scope

- Major architectural changes to removeMicrosoft dependencies and integrate toNetWeaver BI and BIA

- ABAP A/S is now where most l ogic is

run: 64-bit, database independent, etc- New validations engine (replacing

Journals only validations)

- Transports / Lifecycle Management

- Statistics framework for monitoringperformance

- Remote debugging c apabilit y- Planned: client able to access multip le

systems; vastly increased dimensions &members

- BPFs (new func tionality, so limit ed customer adoption biggest loss is for sales / demos)

- Books (Distributor/Collector functionalityincluded in scope, but Books are out)

- Drill-Through (will investigate workaroundswith RIG)

- Dynamic Hierarchy Editor (workaround usingnormal Excel input templates)

- Custom Menus (intended to be replaced byBPFs when BPFs are fully func tional)

- Insight (only impacts a few customers andsales/demos)

- SQL Logic in K2 Scripts (MDX Logic & ABAPavailable)


11/22

SAP AG 2007, 11

BPC 7

Where are we?

All of these changes have been implemented with lessthan six months of development!

Dev Close is 21st

March. Going to be close, but we areon track to reach thi s milestone

Able to get the fi rst build out this week, where you canuse the BPC clients without any SQL Server/AnalysisServices dependencies.

This is coming late, but it was a significant effort toget to this point as all client initialization functionshad to be provided from ABAP before this couldhappen, and they had all sorts of dependencies onother modules.


12/22

SAP AG 2007, 12

BPC 5.x

Web Server (IIS) & .NET Application Server

Client

Web Services

MS OfficeClients

Ad min Web

Platform Services

Ap plic ation Services

Data

OLAP (MSAS)

HTTP/SOAP

MDX UNCSQL

Others

Relational Database(MS SQL Server) File Share

Server sideRequirements

MS SQL Server

MS AnalysisServices

MS Repor tingServices

MS DTS (or SSIS)

.NET 1.1 A/SWeb Server (IIS)

File Share


13/22

SAP AG 2007, 13

SAP Business Planning and Consolidation 5.0 TechnicalArchitecture

.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

Configuration Admin

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

R R

R

R


14/22

SAP AG 2007, 14

BPC 7

Server sideRequirements

NW BI (ABAP A/S &OLAP Engine)

Any Database

.NET 1.1 A/S

Web Server (IIS)

What was removed?

No MS ReportingServices

No MS DTS/SSIS

No MS AnalysisServices

Database agnostic

~85% processing to ABAP (not .NET 1.1)

Al l f iles s tored in DB


15/22

SAP AG 2007, 15

SAP Business Planning and Consolidation 7.0 TechnicalArchitecture

ABAP

BPC ABAP Function Modules BPC Data Access Objects

SAP BPC (.NET)

Application Services

SourceSystems

Database

BPCCustomizingInfoProvider BI Metadata

BIMasterdata

BPC AppServices

BPC Audit ...

Thin Client

Web Services

Admin ConfigurationBPF ...WorkStatus

Browser

HTTP/SOAP

WebUI icl.Reporting

(ASP.NET)

R HTTP

Application Services Proxies Utilities

Platform Services

SchedulingProxy

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 Logic LogicModules

ABAP Basis

ABAP BatchScheduler

R

DAO Proxies

R

File ServiceProxy

HTTP/RFC HTTP/RFC

Data Mgmt.

Data Mgmt. ProcessComponents

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


16/22

SAP AG 2007, 16

Separate Namespace for BPC Generated Objects

InfoCube/CPMB/IXXIC1

InfoObject/CPMB/XXIO01

All BPC Object s will be stored in the /CPMB/ namespaceBPC will not be able to c reate objects in the EDW Namespace

All BI Objects wi th in the /CPMB/ namespace have generated technicalnames (no technical names exposed to user in BPC)

MultiProvider /CPMB/MXXIC1

Technical Pre-requisites:BPC .NET Server

Windows Server 2003:MS IIS.NET 1.1MS XML 3.0

ABAP:


17/22

SAP AG 2007, 17

4 Customer Implementation Options

Option 1 Fully Utilize BPC Admin ConsoleWithin th is Option, Actual and Plan Data are stored in a single cube

within the BPC namespaceOption 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 CubesWithin this option , you will do the initial configuration within BPC,

but can utilize BI Admin Workbench for more technical operationsOption 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 Adminis trator Workbench (RSA1) to cr eateany partitioned cubes, you wil l have to manually maintain thesecubes. You cannot use the BPC Admin Console on these cubes.

BPC Admin Console only works on cubes created within the BPC Admin Conso le. Option 1 is supported by BPC. Option 2, 3, and 4 arecustomer implementations and the responsibility of customers.


18/22


19/22

SAP AG 2007, 19

GeneratedFinanceApplication

GeneratedMultiProvider

ApShell

GeneratedFinance BIQuery

Option 2 Utilize Logical Partitioning for BPC Cubes

Data is Stored Here

Persistency

No Data is Stored Here(Virtual Layer)


Supports OsoftChange

Only One Cube ismanaged throughOsoft, and others aredone through ManualBI Work

Changed directly inBPC Admin Console

Application Mgmt


Application Mgmt

2005 Data(locked)

2007 Data2006 Data(locked)

These cubes are created through NW BI and copied from the generatedBPC Cubes using RSA1 and manually attached to the MultiProvider.

Anytime a change is made using the BPC Admin Console, the logi cal lypartitioned cubes will n eed to be manually maintained and added to theMulti Provider using NW BI (RSA1). All Previous year data is moved fromthe Generated BPC cube to previous year cubes using BI ETL.


20/22

SAP AG 2007, 20



ApShell


Data is Stored in both EDW Actuals Cube as well asBPC cube

Persistency






Application Mgmt


Application Mgmt

EDW Actuals Cube

Plan Actuals Data

The BPC Actuals cube is c reated through NW BI and copied fr om thegenerated BPC Cubes using RSA1 and manually attached to theMultiProvider. Anytime a change is made using the BPC Admin Console,the BPC Actuals cube will need to be manually maintained and added tothe Mult iProv ider using NW BI (RSA1).

COPY DATA

Option 3 Utilize Actuals and Plan in Separate Cubes


21/22

SAP AG 2007, 21



ApShell


Option 4 Dont Replicate EDW Actuals

Data is Stored in both EDW Actuals Cube and virtuallyread into BPC cube (notcopied)

Persistency






Application Mgmt


Application Mgmt

EDW Actuals Cube

Plan Actuals Data

The BPC Actuals cube is a virtual provid er that is created throug h NW BIand has the same structured as the generated BPC Cubes using RSA1 andmanually attached to the MultiProv ider. Anytime a change is made usingthe BPC Admin Console, the BPC Actuals Virtual Provider wil l need to bemanually maintained and added to the MultiProvider using NW BI (RSA1).

Virtually Read


22/22

SAP AG 2007, 22

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof 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 registeredtrademarks 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 andimplemented 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 aswell 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 respectivecompanies. 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 beliable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services, if any. Nothingherein should be construed as constituting an additional warranty.

Copyright 2007 SAP AG. All Rights Reserved.

BPC 7x Internal NW Tech

Documents

Transcript of BPC 7x Internal NW Tech