Integrating Business Planning and Consolidation With Sap Erp and Sap Netweaver

IM206
Integrating Business Planning and

Consolidation with SAP ERP and SAP
NetWeaver
Ron Silberstein, EPM RIG, Business Objects, an SAP Company

Jean-Claude Pizzi, EPM RIG, SAP Italia
Disclaimer
This presentation outlines our general product direction and should not be
relied on in making a purchase decision. This presentation is not subject to
your license agreement or any other agreement with SAP. SAP has no
obligation to pursue any course of business outlined in this presentation or to
develop or release any functionality mentioned in this presentation. This
presentation and SAP's strategy and possible future developments are
subject to change and may be changed by SAP at any time for any reason
without notice. 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
assumes no responsibility for errors or omissions in this document, except if
such damages were caused by SAP intentionally or grossly negligent.
SAP 2008 / SAP TechEd 08 / <IM206> Page 2
Agenda
1. BPC Technical architecture and Overview

1.1. Technical Architecture
1.2. Terminology mapping
2. BI Data modeling related to BPC

2.1. MultiProvider
2.2. Implementation options
3. Specific aspects of BI Architecture and BPC

3.1. EDW and Data Integration
3.2. Recommendations
4. Data Flow handling using Data Manager in BPC

3.1. Introduction and Definitions
3.2. Handling Master Data
3.2. Handling Transaction Data
Architecture of SAP BPC 7.0, Version for the

Microsoft Platform
Server-side
Requirements
Client
MS Office
Clients
Admin
Web
Others
MS SQL Server
MS Analysis
Services
MS Reporting
Services
MS DTS (or SSIS)
.NET 1.1 A/S
Web Server (IIS)
File Share
HTTP/SOAP
Web Server (IIS) & .NET Application Server

Web Services
Application Services
Platform Services
MDX
SQL
UNC
Data
OLAP (MSAS)
Relational Database
(MS SQL Server)
File Share
Architecture SAP BPC 7.0, Version for

SAP NetWeaver
Server-Side Requirements for SAP BPC 7.0,

Version for SAP NetWeaver
Server-side requirements
SAP NetWeaver BI Enhancement Pack1
SAP NetWeaver BI for Add-on SAP BPC for NetWeaver SAP

NetWeaver Edition
Any RDBMS SAP NetWeaver Supports
.NET application server (both .NET 1.1 and 2.0 are required)
Web Server (IIS)
SAP BPC 7.0, Version for NetWeaver

Architectural Notes
Multi-tier architecture of the SAP BPC
NetWeaver Edition
BPC for Office and BPC Admin Clients

use Web services to connect to the
.NET Web Server Tier (.NET 1.1)
The .NET Web Server connects to the
ABAP Web Application Server using
the SAP .NET Connector (v2.0)
Thus, .NET 1.1 and .NET 2.0 are
required
Internally, each RFC (Remote Function
Call) is a wrapper around an objectoriented class within the UJ package
(also known as development class)
Metadata is stored in BPC-specific
tables
Master data (aka: dimension members)
and transactional data (aka :fact data)
are stored in NetWeaver BI objects
and tables
SAP BPC 7.0, Version for SAP NetWeaver:

Some Key Basic Points
SAP Business Planning and Consolidation, version for SAP NetWeaver is built
on SAP NetWeaver BI as a platform.
The general development approach has been to implement (most of) the
application functionality and features that exist on SAP BPC, version for the
Microsoft Platform.
SAP BPC, version for SAP NetWeaver is implemented using SAP NetWeaver BI
objects (i.e. InfoCubes, InfoObjects), in a separate namespace than data
warehouse version of SAP NetWeaver BI objects.
SAP BPC InfoCubes are referred to as applications and have a slightly
different design than basic SAP NetWeaver BI InfoCubes. For example, time
characteristics are handled differently, etc.
The business user is the focus of SAP BPC. The business user should not
have to access the backend of the system, for example the data warehousing
workbench.
In BPC, data (transactional, master) IS NOT shared across AppSets. Appsets
are like InfoAreas, but without shared data.
Agenda


2.1. MultiProvider


Terminology Mapping (step 1): Microsoft

Objects vs SAP NetWeaver BI Objects
Mapping MS components with the SAP

NetWeaver Platform
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 approximates equivalencies between SAP BPC version for
the Microsoft Platform components and SAP BI objects.
Mapping OLAP Objects

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 conceptually
like an Attribute within the master data table of a Characteristic InfoObject. Technically, it is more
than that in Analysis Services, even though not in SQL Server.
SAP 2008 / SAP TechEd 08 / <IM206>

<Session Page
ID> Page
12 12
Separate Namespace for BPC Generated

Objects
All BPC Objects are stored in the /CPMB/ namespace

BPC will not be able to create objects in the EDW Namespace ((i.e. /BIC*,
/BI0*)
All BI Objects within the /CPMB/ namespace have generated technical

names (no technical names exposed to user in BPC)
MultiProvider
/CPMB/MXXIC1
InfoCube
/CPMB/IXXIC1
InfoObject
/CPMB/XXIO01
Agenda


2.1. MultiProvider


Relevant SAP NetWeaver BI Concepts:

MultiProvider
Definition
Combination of various objects, including possibly InfoCubes, DataStore

objects, InfoObjects, VirtualProviders and InfoSets
MultiProvider
No Data
With Data
Basic
InfoCube
VirtualProvider
Master Data
InfoSet
DataStore Object
SAP NetWeaver BI Data Modeling:

MultiProvider
Benefits
Queries are split automatically and distributed to InfoProviders (parallel execution)
Single InfoProviders smaller, less complex and less sparsely filled than one big
InfoProvider
No additional data storage
(Parallel) Data load into individual InfoProviders
Transparent usage for Reporting
Local queries on each InfoProvider possible
Archiving of single basic InfoProvider is very easy
Disadvantages
Administration
SAP NetWeaver BI MultiProvider Logical

Partitioning
MultiProvider (or Logical) Partitioning
Possible partitioning criteria: year, plan/actual, regions, business area
Parallel sub-queries are spawned automatically to base InfoCubes
9 Use MultiProvider partitioning to cut large amounts of data in smaller units

Queries on MultiProvider
MultiProvider
Consolidated
view on all data
Parallel Sub-queries
Base InfoCubes
Homogenous
Data Models
Europe
Asia
North America
Parallel processing built into design

Agenda


2.1. MultiProvider


SAP BPC, Version for SAP NetWeaver

Implementation Options
Option 1 Fully Utilize BPC Admin Console (default appliction behavior)
Option 2 - Utilize Logical Partitioning for BPC Cube
Perform initial configuration within BPC Admin Console, but utilize NetWeaver BI
Data Warehousing Workbench for more technical operations
Option 3 Utilize Actuals and Plan in Separate Cubes
Actual and Plan Data are stored in a single cube within the BPC namespace
Option 4 Dont Replicate EDW Actuals
NOTE: If you use the Data Warehousing 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 considered project solutions.
Details: Implementation Option 1 SAP BPC

Admin Console
Persistency
AppSet
Generated
Finance BI Query
No Data is Stored
Here (Virtual Layer)
Generated
MultiProvider
No Data is Stored
Here (Virtual Layer)
Generated
Finance
Application
Data is Stored Here
All Data
Supports BPC
Changes
Change directly in BPC
Admin Console
Admin Console

Admin Console
Details: Implementation Option 2 Logical

Partitioning for BPC InfoCubes
Persistency
AppSet
Generated
Finance BI Query
Generated
MultiProvider
Generated
Finance
Application
No Data is Stored Here

(Virtual Layer)
Changed directly in
BPC Admin Console

(Virtual Layer)
Changed directly in
BPC Admin Console
Data is Stored Here

2005
(locked)
2006
(locked)
2007 Data
Supports BPC
Changes
Only one InfoCube is

managed through
BPC; others are done
through RSA1
The InfoCubes (in this example) were manually created by copying the
generated BPC InfoCube using RSA1 (and manually attached to the
MultiProvider). Anytime a change is made using the BPC Admin Console, the
logically partitioned cubes will need to be manually maintained and added to
the MultiProvider using RSA1. All Previous years data is moved from the
generated BPC cube to previous year cubes using normal dataflow.
Details: Implementation Option 2 Logical

Partitioning for BPC InfoCubes
Persistency
AppSet
Supports BPC
Changes
Generated
Finance BI Query

(Virtual Layer)
Changed directly in
BPC Admin Console
Generated
MultiProvider

(Virtual Layer)
Changed directly in
BPC Admin Console
COPY DATA
EDW
Actuals Cube
Data is stored in both

EDW actuals cube as
well as BPC cube
Actuals
Plan

managed through
through RSA1
Copy data model from

generated BPC InfoCube
The BPC actuals cube is created by copying from the generated BPC Cubes
using RSA1 and manually attached to the MultiProvider. Anytime a change is
made using the BPC Admin Console, the BPC Actuals cube will need to be
manually maintained and added to the MultiProvider using RSA1..
Details: Implementation Option 4 Dont Replicate

Actuals InfoCube, Use VirtualProvider
Persistency
Supports BPC
Changes
Generated
Finance BI Query

(Virtual Layer)
Changed directly in
BPC Admin Console
Generated
MultiProvider

(Virtual Layer)
Changed directly in
BPC Admin Console
Data is Stored in both

EDW Actuals Cube
and virtually read into
BPC cube (not copied)

managed through
through RSA1
AppSet
Virtually Read
Actuals
EDW
Actuals Cube
Plan
Copy data model from generated BPC

InfoCube to help create VirtualProvider
The BPC actuals cube is a virtual provider created in RSA1 and has the same
structure as the generated BPC Cubes, and is manually attached to the
MultiProvider. Anytime a change is made using the BPC Admin Console, the
BPC actuals VirtualProvider will need to be manually maintained and added to
the MultiProvider using RSA1.
Agenda


2.1. MultiProvider


Overview: SAP NetWeaver BI Architecture,

Including Source System Types
Architecte
d
Data Ma
rts
Standard SAP NetWeaver BI Data Flow Concepts in

SAP BW 3.x and SAP NetWeaver 7.0
SAP BW 3.x
InfoProvider
BI in SAP NetWeaver 7.0
InfoProvider
Update Rules
InfoSource
Transformation
Transfer Rules
PSA
DataSource 3.x
DataSource 7.0
(PSA)
InfoPackage
InfoPackage
Source System
Source System
Data Warehousing: Inmons Corporate

Information Factory and SAP NetWeaver BI
= Potentially covered by SAP NetWeaver BI
Data Warehousing Layers in

SAP NetWeaver BI
Data Warehouse
Operational Data Store
Multidimensional Models
Non volatile
Operational Reporting
aka Data Marts
Granular
Near Real-Time / Volatile
Multidimensional analysis
Integrated
Granular
Aggregated view
Historical foundation
Integrated
Built with DataStore

Objects
Built with DataStore

Objects
Built with InfoCubes
Comparison of Layered Architecture in SAP

NetWeaver BI
Frequency Historical Historical Primary Granularity Owner

of Load background complete Reporting
of
Target
Information
Data Marts
ODS
DW
daily,
weekly,
monthly
near real
time - daily
daily,
weekly,
monthly
Overwrite/
change loaded
data
>= 2 years
aggregated
functional yes, with respect to

area
project scope
< 6 month
granular
several years
in
Archive
granular
functional yes, with respect to

area
project scope
corporate
no
Customer Example: SAP NetWeaver BI

Modeling Layers
Global Reporting Layer
Leveraged Reporting Layer
Business-specific reporting logic applied in routines filling this layer
Fed from Regional Data Mart

Layer as necessary
Function-shared
SBU-shared
Special Need
Requests loaded without activation Event Chains used to
activate all requests in a given region during regional off hours
Regional Data Mart Layer (not SBU-specific)

Billing
Billing
Americas
Billing
EMEA
Asia-Pacific
(structures copied from Global Data Mart Layer using Start Routines to limit delta loads per InfoProvider by region)
Global Data Warehouse Layer (not region or SBU-specific)
ERP Fed by initialization &
Billing
Legacy
Legacy ERP
subsequent delta loads

throughout day
(templates built from Standard Business Content extended to satisfy corporate SBU/Common data needs)
source system data
Billing
Info
Source
Info
Source
Info
Source
Info
Source
ETL Platform
Legacy application systems

Billing
Agenda


2.1. MultiProvider

Observations / Recommendations: Data Warehouse

Strategy and BPC, version for SAP NetWeaver
BPC is a business-user driven application the business user drives their
own modeling, data acquisition, etc
An intelligent architecture is important in any data warehousing strategy, as
is governance
Utilize a data provisioning approach focus on meeting corporate
requirements in the data warehousing layer, and either provision data from
the DataStore objects in the DW layer and/or create somewhat generic data
marts (InfoCubes) that BPC business users can leverage
Avoid flavoring data with specific business rules ensure that BPC
business users have good awareness of existing DataStore objects and
InfoCubes from which they can derive their modeling and the data they need
Be prepared to enable significant flexibility to BPC users focus governance
on data warehouse objects, without imposing too much on BPC users
Agenda


2.1. MultiProvider


Data Manager in SAP BPC, version for SAP

NetWeaver: Overview
Data
Manager is an SAP Business Planning and Consolidation feature that

allows the user to manage loading, transforming, and manipulating data.
Data
Manager is delivered with a set of packages to import, copy, clear and

move data within and across applications.
Data
Manager supports mapping and complex transformations of

transactional data files as well as master data files.
Data Manager Terminology
Object:
Data Manager
Acronym
DM
Package
Task / Process
Type
Process Chain
PC
Transformation File
Conversion File
Description
The module to transform and load and manipulate data
The operational unit that user can execute for a data process, like
import, export, etc.
The module to deal with specific functionality. E.g. load helps to
transfer data from file to cube, from cube to cube, from cube to file.
Package is built on Process Chains which include task(s).
PC is a framework, which is provided by BW, that helps to schedule
packages, maintain status of running packages, wrap tasks into
packages and so on. PC is the foundation of a package.
An SSIS package is roughly equivalent to a NW BI Process Chain.
This is an Excel Workbook that defines mappings for data
transformations
This is an Excel Workbook that defines conversions within data
transformations.
Data Manager Packages
Data
Manager packages are implemented as process chains and allow you to

do common data manipulation activities
The
packages that come with SAP BPC, version for NetWeaver are designed
to be dynamic so that you do not need to modify the packages in order for
them to work with your applications and dimensions.
You might want to modify packages to behave differently or to perform
additional tasks.
You can make modifications to the packages supplied with SAP Business
Planning and Consolidation , version for SAP NetWeaver (not best
practice) or use those packages as templates to build package, as per
your requirements
Data Manager Package Type in

SAP BPC, version for SAP NetWeaver
In SAP BPC, version for NetWeaver, only one package type is available (called Process
Chain)
You can then choose which process chain to use for Data Manager
Only Process Chains in the /CPMB/ namespace are displayed
You can then name your SAP Business Planning and Consolidation Data Manager Package
Example, Import into Financial Application
Data Manager Under the Covers: Delivered

Process Chain Templates
There
are four broad types of

delivered Process Chain
Templates which can be used
to build SAP Business
Planning and Consolidation
Packages:
Standard Data Loading

Packages
Financial Packages
Administrative Packages
Example Packages
These process chain
templates can be displayed
and edited in ABAP
transaction RSPC.
Standard Data Manager Delivered Packages

(1)
PROCESS CHAIN
DESCRIPTION
TECH NAME
TEMPLATE
/CPMB/IMPORT_MASTER
BPC: Import Master Data This package allows you to load dimension
member data directly into a SAP Business
Planning and Consolidation Dimension's
Member Table (InfoObject's master data table)
/CPMB/IMPORT_DESCRIPT
BPC: Import Master Data This package allows you to load dimension
Description
member texts directly into a EVDESCRIPTION
(InfoObject's text table)
/CPMB/IMPORT
BPC: Import Transaction This package imports one or more ASCII files
Data
into the current application. You are prompted
for one or more import file and associated
transformation files. The signs of the amounts
are reversed based on the Account type.
You can use the import.xls transformation file
with this package.
/CPMB/LOAD_INFOPROVIDER
BPC: Load Transaction
This package allows you to load data from one
Data from Other Cube
InfoCube (EDW or BPC) into a SAP Business
Planning and Consolidation Application. You can
associate a transformation file to do the
mapping.
Standard Data Manager Delivered Packages

(2)
PROCESS CHAIN
TEMPLATE
BPC: Move Transaction
Data in one cube
DESCRIPTION
TECH NAME
This package lets you move any selection of data within an /CPMB/MOVE
application. You are prompted for source and destination
data selections for all dimensions. The destination
selection's fact table records are cleared before the source's
records are moved. The source's fact table records are
cleared after they are moved to the destination.
BPC: Clear Transaction
This package clears the data in the SAP Business Planning /CPMB/CLEAR
Data in One Cube
and Consolidation Application by importing zero values. The
optimize process removes the zero values, which clears all
values from the table. Running this package also clears
comments from the comments table.
You can use the import.xls transformation file with this
package.
You must select at least one dimension in order to run this
package. If you select [All], the package will not run.
BPC: Copy Transaction
This package copies data between dimensions within an
/CPMB/COPY
Data in One Cube
application.
BPC: Append Transaction This package imports data into the application by appending /CPMB/APPEND
Data
the data to the fact table, and then runs default logic against
the imported data set.
You can use the import.xls transformation file with this
package.
Delivered Process Chain Process Types

Utilized by Data Manager
SAP BPC for NetWeaver delivers the following process types:

Admin Task
Audit Archive
Clear BPC Table
Clear Comments
Clear Cube
Convert
Convert for Copy and Move
Create Dimension
Dynamic Modify
Email
FTP
Finalize Optimize
Journals
Load
Master Data Load
Master Data Description Load
Optimize Cube
Ownership Calc
Run Logic
OnLine Status
Agenda


2.1. MultiProvider



Loading Master Data into BPC, version for SAP

NetWeaver
There are numerous options to loading your master data into BPC:
Plan Master Data
Option 1 Plan Master Data directly in BPC (Using Dimension Member Sheets)
Option 2 Members on the Fly (End Users Add new master data from Excel)
Using Comments and Dummy Members (natively available)
Load Master Data from SAP NetWeaver BI InfoObjects:
Option 3 Load Master Data from SAP NetWeaver BI characteristics using SAP NetWeaver BI dataflow
(Full Load)
Option 4 Load Master Data from SAP NetWeaver BI characteristics directly using Data Manager (Full
Load) Requires a Custom Process Type (project solution, ie not available out of the box)
Load Master Data from SAP ERP
Option 5 Load Master Data from ERP directly into BPC - Requires a Custom Process Type (project
solution, ie not available out of the box)
Option 6 Load SAP ERP Master Data into SAP NetWeaver BI first and then use options 4-5
Load Master Data from 3rd Party
Option 7 Load Master Data from flat file using SAP NetWeaver BI dataflow
Option 8 Load Master Data from flat file using BPC Data Manager
Master Data Option 1 Plan Master Data

Directly in BPC
To plan master data directly within BPC, you can utilize the Dimension Member Sheet within the
Administration Console - this is an excel workbook sheet that allows you to copy and paste in dimension
member data and assign the members to hierarchies
Pros:
This is maintained directly by the BPC Administrators
Cons:
BPC End Users cannot create new members as they dont have access to the Admin Console
Master Data Option 2 Members on the Fly

(Using Comments and Dummy Members)
Within BPC, there may be requirements to add members on the fly (meaning end users
can add dimension members from the BPC for Office Client). The most common way to
do this is by utilizing comments and dummy members.
To do this, you can follow these steps:
1. BPC Administrator creates dummy members within BPC Dimension Member

sheet for adding members on the fly
2. BPC for Excel user can now plan against these members. Using the =EVCOM()
functionality within the BPC for Excel client, users can replace the DUMMY
value with the value from comments to display the actual new members they want
to plan against within this Input Schedule
Pros:
Planning against New Dimension Members is directly available for BPC End
Users
Cons:
Requires BPC for Excel User to be savvy with using EV Functions
Requires BPC Administrators to add these dummy members as an upfront

investment
Master Data Option 3 Load Master Data from SAP

NetWeaver BI Characteristics using BI Dataflow
With BPC, you may source your master data (Dimension Members) from
InfoObjects. Utilizing SAP NetWeaver BI data flow, you can load the BPC
Dimensions from the (EDW-based) BI InfoObjects. This is a full load.
Pros:
ABAP provides extensive functionality to do any transformations for

loading master data
Cons:
Any changes to properties within the BPC Admin Console will invalidate
your SAP NetWeaver BI dataflow (transformations, update rules) and they
will need to be updated.
Business users are probably not proficient with ABAP
Master Data Option 4 Load Master Data from SAP

NetWeaver BI Characteristics Directly Using Data
Manager
With BPC, you may want to acquire master
data (Dimension Members) from
InfoObjects. Utilizing BPC Data Manager
will allow you to natively load master data
from InfoObjects
Pros:
End User can schedule loads from

BPC Data Manager and can utilize
the BPC Transformation and
Conversion Files
Data Manager loads are not

invalidated based on changes made
to BPC Dimensions from Admin
Console
Cons:
Requires a custom process type

(Not shipped with the product)
Master Data Option 5 Load Master Data from SAP ERP

directly into BPC, version for SAP NetWeaver
With BPC, you may want to acquire

master data (Dimension Members) from
InfoObjects. Utilizing BPC Data Manager
will allow you to natively load master data
from SAP ERP Master Data
Pros:
End User can schedule loads from

BPC Data Manager and can utilize
the BPC Transformation and
Conversion Files
Data Manager loads are not

invalidated based on changes made
to BPC Dimensions from Admin
Console
Cons:
Requires a custom process type

(Not shipped with the product)
Master Data Option 6 Load SAP ERP Master Data into

SAP NetWeaver BI First, and then Use Options 4-5
In
BPC, you may want to acquire master data (Dimension Members) from
InfoObjects. Utilizing BPC Data Manager will allow you to natively load master
data from SAP ERP. If you some additional cleansing or staging is required, it
is recommended that you load your SAP ERP master data into SAP
NetWeaver BI first before loading it into BPC, version for SAP NetWeaver.
Pros:
Ability to stage and cleanse master data
Cons:
Requires setting up SAP NetWeaver BI master data load
Master Data Option 7 Load Master Data from

flat file using SAP NetWeaver BI Dataflow
Within BPC, you may acquire your master data (Dimension Members) from an external,
non-SAP system. Utilizing SAP NetWeaver BI data flow, you can load the BPC
Dimensions from the (EDW-based) BI InfoObjects. This is a full load.
Pros:
Full control over writing ABAP to do any transformations for loading master data
Cons:
Any changes to properties within the BPC Admin Console will invalidate your
SAP NetWeaver BI dataflow structures, and they will need to be updated.
Master Data Option 8 Load Master Data from

flat file using BPC Data Manager
Within BPC, you can load BPC Dimension Members from a flat file through data
manager packages for loading BPC Dimension Members
Pros:
End User can schedule loads from BPC Data Manager and can utilize the BPC
Transformation and Conversion Files
Will not overwrite existing dimension members
Will update dimension member sheet
Cons:
Requires a flat file
Full Load Only
Agenda


2.1. MultiProvider



Loading Transaction Data into BPC, version

for SAP NetWeaver (1)
Options to loading transaction data into BPC, version for SAP NetWeaver
Load actuals data from SAP NetWeaver BI InfoCubes:

Option 1 Load transaction data from SAP NetWeaver BI InfoCubes
using SAP NetWeaver BI data flow
directly using data manager (Full Load)
Option 3 Load transaction data from a DataStore Object in SAP
NetWeaver BI through data manager (Delta Load)
Option 4 Load transaction data from SAP NetWeaver BI using an Open
Hub destination that provides flat files for data manager to load (Delta
Load)

directly using data manager custom process type (project solution not
available out of the box) (Delta Load)
Loading Transaction Data into BPC, version

for SAP NetWeaver (2)
Options to loading transaction data into BPC, version for SAP NetWeaver
Load Transactional Data from SAP ERP

Option 6 Use a custom process type to load transactional data from
SAP ERP directly into BPC, version for SAP NetWeaver
Option 7 Load ERP transaction data into SAP NetWeaver BI first using
standard SAP NetWeaver BI dataflow, and then use options 1-5
Load Third Party Data

Option 8 Load transaction data via flat file via SAP NetWeaver BI
dataflow
Option 9 Load transaction data via UD Connect (SAP NetWeaver BI
dataflow )
Option 10 Load transaction data via Flat File using BPC data manager
Transaction Data Option 1 Load transactional data

from SAP NetWeaver BI InfoCubes using
SAP NetWeaver BI data flow
To load transaction data from SAP NetWeaver BI InfoCube into BPC, version for SAP
NetWeaver, you can utilize SAP NetWeaver BI data flow
BPC is based on NetWeaver 7.0, transformation groups and data transfer process
(DTP) can be used
Since NetWeaver 7.0 supports the BW 3.x based staging, update rules, transfer
rules, and InfoPackages are also available for staging and loading transaction data.
Pros:
DTPs can be used for delta based loading.
Cons:
Data load must be managed by IT.
Any change to an application within the BPC Admin Console will delete your BI
dataflow structures completely
Transaction Data Option 2 - Load transactional data from

SAP NetWeaver BI InfoCubes directly using data
manager (Full Load)
To load transaction data from SAP NetWeaver BI
cubes into BPC, you can utilize BPC data
manager.
The BPC data manager has functionality to
load directly from NetWeaver BI EDW
Cubes directly into BPC Applications.
Since NetWeaver 7.0 supports the BW 3.x
based staging, update rules, transfer rules,
and InfoPackages are also available for
staging and loading transaction data.
Pros:
BPC business users can schedule their
own loads
You can use BPC transformation and
conversion files for your load
Validation of transformation files supports
SAP NetWeaver BI cubes
Cons:
Always must be a full load
Requires BPC end user to know technical
name of InfoCube in SAP NetWeaver BI
EDW
Transaction Data Option 3 Load transaction data from

a DataStore Object in SAP NetWeaver BI via data
manager (Delta Load)
To load transactional data, you can utilize SAP
NetWeaver BI dataflow to send delta data to an
outbound staging layer (stored in a DataStore
Object). Older data is completely deleted from the
DataStore object with each new data load. BPC
Data Manager packages can be used to load into
BPC Applications from this DataStore object.
Pros:
BPC business users can schedule data

loads, and data load is delta data only
You can use BPC transformation and

conversion files for your data load
Validation of transformation files supports

SAP NetWeaver BI InfoProviders (i.e.
DataStore Objects)
Cons:
Requires SAP NetWeaver BI data modeling

to setup the staging layer. Dependency on
the business user to consistently load data
if the user fails to load, they could be
missing data.

SAP NetWeaver BI using an Open Hub destination that
provides flat files to data manager (Delta Load)
You can utilize SAP NetWeaver BI dataflow to provision delta data to an
staging layer (stored in a flat file) through an Open Hub Destination. Data
Manager packages can be used to load into BPC Applications from this file.
There will be a separate file for each daily delta dataset.
Pros:
BPC business users can schedule data loads, and data load is delta data
only
You can use BPC transformation and conversion files for your data load
Validation of transformation files supports SAP NetWeaver BI
InfoProviders (i.e. DataStore Objects)
Cons:
Requires SAP NetWeaver BI data modeling to setup the staging layer.
Dependency on the business user to consistently load data if the user
fails to load, they could be missing data.
Requires IT to setup staging layer. Dependency on user for failover. If

user fails to load, they could be missing data, but openhub output can
be persisted so user can load the missing file again

SAP NetWeaver BI InfoCubes directly using data
manager custom process type (Delta Load)
To load transaction data from SAP
NetWeaver BI InfoCubes into BPC, version
for SAP NetWeaver using data manager
and delta data, you can implement a
custom process type.
Pros:
BPC business users can schedule
data loads, and data load is delta
data only
You can use BPC transformation
and conversion files for your data
load
Validation of transformation files
supports SAP NetWeaver BI
InfoProviders (i.e. DataStore
Objects)
Cons:
Requires customer development
not delivered out of the box
Transaction Data Option 6 Use Custom Process Type

to load Transactional Data from ERP directly into BPC
To load transaction data from SAP ERP
into BPC, version for SAP NetWeaver
directly (and utilize a delta based loading
mechanism), you can implement a
custom process type.
Pros:
BPC business users can schedule
data loads, and data load is delta
data only
You can use BPC transformation
and conversion files for your data
load
Data can be loaded directly from
the source system with no
replication
Cons:
Requires customer project
solution to implement this custom
process type not delivered out
of the box
Transaction Data Option 7 Load SAP ERP Transaction

Data into SAP NetWeaver BI EDW First and then Use
Options 1-5
To load transaction data from SAP ERP into BPC, version for
SAP NetWeaver, it is recommended that you load the data into the
SAP NetWeaver EDW first to stage the data (although this is not
technically required).
Pros:
General data staging benefits of an EDW strategy.
Cons:
Requires data modeling in SAP NetWeaver BI and IT management
of data provisioning .
Transaction Data Option 8 Load transaction data

via flat file via SAP NetWeaver BI dataflow
To load transaction data from external source systems, you can load data into
BPC, version for SAP NetWeaver via flat files using SAP NetWeaver BI data flow.
Pros:
All the general benefits of the SAP NetWeaver BI data flow (industrialstrength transformations, data quality, etc)
Cons:
SAP NetWeaver BI dataflow structures are invalidated if structural
changes are made to the application in the BPC Admin Console
Data must be stored in flat files prior to loading
Transaction Data Option 9 Load transaction data

via UD Connect (SAP NetWeaver BI dataflow )
To
load transaction data from external source systems, you can load data
into BPC using UDconnect which is ones of the SAP NetWeaver BI dataflow
features
Pros:
All the general benefits of the SAP NetWeaver BI data flow (industrialstrength transformations, data quality, etc)
Cons:
SAP NetWeaver BI dataflow structures are invalidated if structural
changes are made to the application in the BPC Admin Console
Transaction Data Option 10 Load Transaction

Data via Flat File using BPC Data Manager
To
load transaction data from

external source systems, you can
load data into BPC, version for SAP
NetWeaver using BPC Data Manager
to load flat files
Pros:
Business users can schedule
their own data loads
Can utilize BPC transformation

files and conversion files (ease
of use for business user)
Cons:
Data Must be stored in flat files
prior to import
Building Your Business with

SDN Subscriptions
SDN Subscriptions offers developers and consultants like you,
an annual license to the complete SAP NetWeaver platform
software, related services, and educational content, to keep
you at the top of your profession.
SDN Software Subscriptions: (currently available in U.S. and Germany)
A
one year low cost, development, test, and commercialization

license to the complete SAP NetWeaver software platform
Automatic notification for patches and updates
Continuous learning presentations and demos to build
expertise in each of the SAP NetWeaver platform components
A personal SAP namespace
SAP NetWeaver Content Subscription: (available globally)

An
online library of continuous learning content to help build skills.
Starter Kit
To learn more or to get your own SDN Subscription, visit us at the

Community Clubhouse or at www.sdn.sap.com/irj/sdn/subscriptions
Fuel your Career with SAP Certification
What the industry is saying
Teams with certified architects and

developers deliver projects on
specification, on time, and on budget
more often than other teams.
2008 IDC Certification Analysis
82% of hiring managers use

certification as a hiring criteria.
2008 SAP Client Survey
SAP Certified Application

Professional status is proof of
quality, and thats what matters most
to customers.*
Conny Dahlgren, SAP Certified Professional
Take advantage of the enhanced, expanded and multi tier certifications from SAP today!
Further Information
SAP Public Web:

SAP Developer Network (SDN): www.sdn.sap.com
Business Process Expert (BPX) Community: www.bpx.sap.com
Related SAP Education and Certification Opportunities

http://www.sap.com/education/
Related Workshops/Lectures at SAP TechEd 2008

IM100 Business Planning and Consolidation Architecture, Functionality, and
Roadmap
IM106 SAP Business Planning and Consolidation Data Manager: Now and the Future
IM163 SAP Business Planning and Consolidation 7.0 Hands-On Exercises for
Business Planning (hands-on session)
IM208 SAP Business Planning and Consolidation 7.0 and SAP NetWeaver
Enhancements and Features
IM269 Migrating to SAP Business Planning and Consolidation Version 7.0 From 5.1

<Session Page
ID> Page
67 67
Thank you!

<Session Page
ID> Page
68 68
Feedback
Please complete your session evaluation.
Be courteous deposit your trash,
and do not take the handouts for the following session.
Thank You !

Integrating Business Planning and Consolidation With Sap Erp and Sap Netweaver

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Integrating Business Planning and Consolidation With Sap Erp and Sap Netweaver

Uploaded by

Copyright:

Available Formats

IM206

Integrating Business Planning and

Ron Silberstein, EPM RIG, Business Objects, an SAP Company

SAP 2008 / SAP TechEd 08 / <IM206> Page 2

1. BPC Technical architecture and Overview

2. BI Data modeling related to BPC

3. Specific aspects of BI Architecture and BPC

4. Data Flow handling using Data Manager in BPC

Architecture of SAP BPC 7.0, Version for the

MS DTS (or SSIS)

.NET 1.1 A/S

Web Server (IIS)

Web Server (IIS) & .NET Application Server

SAP 2008 / SAP TechEd 08 / <IM206> Page 4

Architecture SAP BPC 7.0, Version for

SAP 2008 / SAP TechEd 08 / <IM206> Page 5

Server-Side Requirements for SAP BPC 7.0,

SAP NetWeaver BI Enhancement Pack1

SAP NetWeaver BI for Add-on SAP BPC for NetWeaver SAP

Any RDBMS SAP NetWeaver Supports

Web Server (IIS)

SAP 2008 / SAP TechEd 08 / <IM206> Page 6

SAP BPC 7.0, Version for NetWeaver

SAP 2008 / SAP TechEd 08 / <IM206> Page 7

BPC for Office and BPC Admin Clients

SAP BPC 7.0, Version for SAP NetWeaver:

SAP 2008 / SAP TechEd 08 / <IM206> Page 8

1. BPC Technical architecture and Overview

1.2. Terminology mapping

3. Specific aspects of BI Architecture and BPC

4. Data Flow handling using Data Manager in BPC

Terminology Mapping (step 1): Microsoft

SAP 2008 / SAP TechEd 08 / <IM206> Page 10

Mapping MS components with the SAP

SAP 2008 / SAP TechEd 08 / <IM206> Page 11

Mapping OLAP Objects

SAP 2008 / SAP TechEd 08 / <IM206>

Separate Namespace for BPC Generated

All BPC Objects are stored in the /CPMB/ namespace

All BI Objects within the /CPMB/ namespace have generated technical

SAP 2008 / SAP TechEd 08 / <IM206> Page 13

1. BPC Technical architecture and Overview

2. BI Data modeling related to BPC

3. Specific aspects of BI Architecture and BPC

4. Data Flow handling using Data Manager in BPC

Relevant SAP NetWeaver BI Concepts:

Combination of various objects, including possibly InfoCubes, DataStore

SAP 2008 / SAP TechEd 08 / <IM206> Page 15

SAP NetWeaver BI Data Modeling:

Queries are split automatically and distributed to InfoProviders (parallel execution)

No additional data storage

(Parallel) Data load into individual InfoProviders

Transparent usage for Reporting

Local queries on each InfoProvider possible

Archiving of single basic InfoProvider is very easy

SAP 2008 / SAP TechEd 08 / <IM206> Page 16

SAP NetWeaver BI MultiProvider Logical

Possible partitioning criteria: year, plan/actual, regions, business area

Parallel sub-queries are spawned automatically to base InfoCubes

9 Use MultiProvider partitioning to cut large amounts of data in smaller units

Parallel processing built into design

1. BPC Technical architecture and Overview

2. BI Data modeling related to BPC