5. bw bpc integration deep dive

SAP BPC 10 NW MEGA ELITE Enablement

BW-BPC Integration Deep Dive

© 2011 SAP AG. All rights reserved. 2

Overview of Day 3: BW/BPC Integration Exercises

Business Case

Exercise 1 - Loading the BW Staging Cube

Exercise 2 - Transaction Data Loading to BPC

Exercise 3 - Using BEx reporting to visualize data

Exercise 4 - Creating a custom Process Chain to automate the Load Process

Exercise 5 - Creating a Data Manager Package

Exercise 6 - Loading Master Data into BPC


Business Case

BW Integration

• A major driver for our customers to select the Netweaver version of BPC is the inherent integration with existing ECC and BW systems.

Today we will explore the following integration scenarios:1. ECC to BW integration 2. BW Cube to BW Data Store Object integration3. BW Data Store Object to BW Data Store Object integration4. BW Data Store Object to BPC integration5. Automation of the total process using Process Chains6. Execution of custom process chains from BPC Data Manager7. Using various reporting tools (BEx Analyzer, EPM 10 Add-in) to visualize and reconcile

data transfers


Agenda

BW Terminology & BasicsBW Modeling OverviewBW/BPC Delta Load processBPC Data ManagerAutomationUsing BW/BPC reporting to validate the BW/BPC Integration process

–Business Explorer (BEx) Query Designer–BEx Analyzer–LISTCUBE–EPM 10 Add-In – BPC connections–EPM 10 Add-In – BW connections


BW and BPC

BPC 10 Objects BW Objects

Comparison of BPC Objects with native BW objects

Model

Texts

SignedData

Info Provider


BW ModelingUseful BW Transaction Codes

RSA1 Admin WorkbenchRSDCUBE InfoCube editingRSDMPRO Initial Screen: MultiProvider Proc.LISTCUBE List viewer for Info CubesRSINPUT Manual Input of Data into CubeRSOR BW Metadata Repository

RSMO Data-Load-Monitor StartRSRQ Data Load Monitor for a RequestRSPC Process Chain MaintenanceRSA2 Datasource RepositoryRSA6 Maintain DataSourcesRSRT Query Monitor

RSBBS Query Jump TargetsRSZC Copy Queries between cubesRSZDELETE Delete queries and workbooksRSBBS Query Jump Targets



RSA1 Admin WorkbenchRSDCUBE InfoCube editingRSDMPRO Initial Screen: MultiProvider Proc.LISTCUBE List viewer for Info CubesRSINPUT Manual Input of Data into CubeRSOR BW Metadata Repository

RSMO Data-Load-Monitor StartRSRQ Data Load Monitor for a RequestRSPC Process Chain MaintenanceRSA2 Datasource RepositoryRSA6 Maintain DataSourcesRSRT Query Monitor

RSBBS Query Jump TargetsRSZC Copy Queries between cubesRSZDELETE Delete queries and workbooksRSBBS Query Jump Targets



Go to transaction code “SE93” and type “RS*” to view all the transaction codes starting with RS (BW related Transaction Codes):


BW ModelingData Warehouse Workbench

To open the Administrative workbench type the transaction code : RSA1



To open the Administrative workbench has several work areas:



Modeling– you create/maintain all of the key BW objects here, such as:

Info Providers – cubes, data store objects (DSOs), Multi-providers, virtual providers, etc.

Info Objects – Characteristics (BPC Dimensions) and Key Figure (SignData) definitions

InfoSource - prepares consolidated data from multiple sources for updating to the data targets

DataSource - used to extract data from a source system and to transfer the data to the BW system

Source Systems – define general connection settings between SAP/Non-SAP systems and BW



Administration – monitor BW operations (Admin Cockpit), broadcast reports, view logs and exceptions



Transport Connection – create BW and BPC transports (new in BPC10) transports.



Documents – create/maintain documents loaded into BW.



BI Content – contains all of the “delivered” objects from your BW installation. Specific objects can be selected and activated so they can be available in your system



Translation– translate short and long texts for Business Information Warehouse objects


Data flow from ERP to BW - Terminology

•Different type of source systems can be defined in the BW system

•Extractors are used to move data from any source into the BW system

•InfoPackages are used to move data from source system to PSA

•Transformations are built to map the fields between the source and target

•Data Transfer Processes (DTPs) are used to move the data from the PSA to Target (i.e. characteristic or info provider)


Integrating BPC NW with SAP NetWeaver® BW

Profit Center Master

FI/CO or other

Extractor Extractor

0PROFIT_CTRFI/CO Actual Cube

BPC Planning

Cube

Planning and Consolidation Profit Center

SAP

ERP

SAP

Net

Wea

ver B

W S

yste

m

SAP

Net

Wea

ver

BW

ED

WSA

P B

usin

essO

bjec

ts

Plan

ning

and

C

onso

lidat

ion

DSO DSO


Why Delta Processing?

Some processes — especially the fast-close — require frequent data updates

There are several options to accelerate the data loading speed:

• Architect for delta loading

• Increase load frequency

• Leverage real-time daemon in SAP NetWeaver BW

With SAP NetWeaver BW 7.3 and the Hybrid-Provider, and with SAP HANA and the Sybase replication server, SAP has taken the next steps to making real time a reality

FI/CO or other

Extractor

FI/CO Actual Cube

BPC Planning

Cube

DSO DSO

BPC

BW

ECC


The Delta Load Process for BW/BPC

1. Flat File – the contents of the flat file simulates an extracted data load from ECC (or any connected system)



2. The Flat File is loaded into the delivered info provider, 0FIGL_C10 cube using the data source



3. Mapping between the flat file and the target 0FIGL_C10 cube is facilitated by the transformation definition



4. 0FIGL_C10 cube’s load is executed by the associated Data Transfer Process (DTP) by linking the DataSource, Transformation, and target info provider:



5. The Full Snapshot DSO is created. This DSO will hold all of the records that will eventually be submitted to BPC.



6. A mapping between the 0FIGL_C10 source cube and the Full Snapshot DSO is created. Rule Groups are used to facilitate the transition from a multi key figure based model into a single key figure model easily consumed by BPC.


Flat File (ECC) record:

0FIGL_C10 record:

Staging DSOs:

BPC:

Deltas Only

The Delta Load Process for BW/BPCRecord Flow



7. The Full Snapshot DSO load is executed by the associated Data Transfer Process (DTP) by linking the DataSource, Transformation, and target 0FIGL_C10 info provider.



8. The Deltas Only DSO is created. This DSO will be the source for BPC Data Manager. The DSO will be loaded with all new/changed records sourced from the 0FIGL_C10 cube through the Full Snapshot DSO change log.



9. A mapping between the Full Snapshot DSO and the Deltas Only DSO is created.

Key to this process is the correct filtering of the Snapshot DSO change log to ensure that only true delta records are moved from the Full Snapshot DSO into the Deltas Only DSO.



10. The Deltas Only DSO load is executed by the associated Data Transfer Process (DTP) by linking the DataSource, Transformation, and target Full Snapshot DSO.

Key to this process is the correct filtering of the Snapshot DSO change log to ensure that only true delta records are moved from the Full Snapshot DSO into the Deltas Only DSO.



Process Summary

Flat file simulates ECC load into BW

Data Sources connects FF load to targeted delivered BW cube

Transformation maps the fields between FF and 0FIGL_C10

0FIGL_C10 cube is loaded with transactional data

DSO is created to hold extracted records from 0FIGL_C10 cube.

Transformation maps 0FIGL_C10 to Full Snapshot DSO

DTP moves data from FF to 0FIGL_C10 cube

DTP moves data from 0FIGL_C10 cube to Full Snapshot DSO

DTP moves data from Full Snapshot DSO to Delta Only DSO Transformation maps Full Snapshot DSO to Delta Only DSO

DSO is created to hold “delta only” records sourced from the Full Snapshot DSO

Start



A few additional comments….

•Note that the process to load the delivered info providers (the 0FIGL_C10 cube in our example) in BW is typically already established by the time a BPC project is started.


BPC Data Manager

Data Manager is BPC’s ETL (extract, transform and load ) tool

Once new records have been loaded into the Delta Only DSO, a Data Manager package is executed to pull that data into the BPC model.


BPC Data Manager

The Data Manger package targets the Delta Only DSO.

The Data Manager package uses the BPC Transformation file for field to field mapping between the DSO and the target BPC Model.


BPC Data Manager

When loading data into BPC using the standard “Load Transaction Data from BW Info Provider” data manager package, you have the option to choose “Merge” or “Replace & Clear”. The “Merge” type load into BPC is used since the “final value” of the record will be delivered to BPC. This means we are not actually loading the “difference” but rather the “final” value of each record. The filters applied on the DTP for the Snapshot DSO, selects only the After Image and the New Image change log records. This filtering ensures the records to be sent into BPC are new records at their “final” value (not at their true “delta” value). BPC will calculate the appropriate record offset natively with the “Merge” type load.


Automation

We now have all the pieces to move data from ECC, through BW, into BPC. The BW process chain provides a means for bundling all of these operations together so the entire process can be automated, scheduled, and controlled.

•You can access BW process chains using the transaction code RSPC.


Automation

Process Chain basics:•A process chain is a sequence of BW related activities that are organized to perform certain functions, such as loading master data or transaction data.

•Process chains can be designed to include branching logic that will execute certain paths of the chain if no errors occur, and a completely different path if errors do occur.

•BPC Data Manager packages are technically executed as a BW process chain.

•Process chains can be scheduled or they can be triggered by events (such as the completion of an extraction of data from ECC).

•All process chains must start with a unique “start process”. The start process provides information on the method of execution of the process chain, including whether the process chain is immediately executed when called or executed by schedule.

•Developers and users may visualize the process by using network graphics

•Each process chain can generate a log that includes details of the execution


Automation

Process Chain can be view in Tree or Network display:

You can switch between the two view using the “Settings” options.


Automation

Process Chains contain one or more process type (links in the chain).


Automation

To construct a chain you select the desired process and drag and drop into the forming process chain


Automation

Use the connection tool to establish a relationship between each link of the chain.


Automation

Conditional Logic can be incorporated, as well as branching of the process due to errors encountered:


Automation

Key automation for executing BPC Data Manger Packages from BW process chains:


Automation

The Data Manager prompt file is stored as a program variant


Automation

Additional programs that can call BPC Data Manager functions from a BW process chain:

UJD_TEST_PACKAGE_LONGPROMPT - allows the assignment of a text file containing large prompt instructions. Required for prompts greater than 1000 characters.

UJD_TEST_PACKAGE_LINK – Package links are Data Manager collections of individual packages to be executed in a sequence. A simple BPC process chain of sorts.


Automation

The completed BW process chain can be executed from BW, either by direct scheduling or by triggering based upon other BW events (such as ECC to BW loads).

The real time evolution of the process chain execution can be observed via the process chain Monitor. Each process type is color coded to indicate execution status:Green for successfully passed,

for currently being executed, Red for execution failure.Yellow


Automation

The completed BW process can be executed from BW, either by direct scheduling or by triggering based upon other BW events (such as ECC to BW loads).

You can also trigger the execution of the BW process chain from BPC. Use the Trigger a BW Process Chain delivered data manager package.


Automation

The completed BW process can also be attached to a BPC data manager package. This has the advantage of being able to use the established BPC security surrounding the access to a specific BW process chain and convenient access to the data manager execution logs.


Reporting Options

There are several reporting options utilized:Business Explorer (BEx) Query Designer

BEx Analyzer

LISTCUBE

EPM 10 Add-In – BPC connections

EPM 10 Add-In – BW connections


Reporting OptionsBEx Query Designer

BEx queries are used for accessing the information in data warehouse area and presenting it in a user-friendly manner to the analyst or business user



Characteristics and Key Figures can be entered into Row/Column formats for presentation using “drag and drop”. A preview section is displayed as you build the query.



Characteristics can be filtered on selected value(s), and proposals can be made to default specific values upon opening the query.



The display characteristics are fully controllable by the Properties panel.


Reporting OptionsBEx Analyzer

The BEx Analyzer uses an MS Excel Add-on to access the BEx query in display results in an Excel format:


Reporting OptionsBEx Analyzer

BEx Analyzer can display the results of a previously designed query, or several queries and functions can be combined into one BEx Analyzer workbook.


Reporting OptionsLISTCUBE

The BW transaction LISTCUBE allows access directly into the BW info provider.



LISTCUBE allows a variety of selection options so you can retrieve the exact data you are looking for:



Records are presented via the SAP GUI viewer, and can be downloaded into a local file or viewed in Excel.


Reporting OptionsEPM 10 Add-In BPC Connections

The SAP EPM 10 Add for Microsoft Office provides direct integration with the BPC data set.



If you enter the EPM 10 Add-In from within BPC Web, a list of available connections will be displayed based upon your current login status. Of course you can always create/edit your own connection definition if desired:



The EPM 10 Add-In has report wizards that leads the user through the process of creating a report:



The final EPM 10 Add-In report uses native Excel as well as unique BPC “EPM” functions to yield the exact custom report desired:


Reporting OptionsEPM 10 Add-In BW Connections

The EPM 10 Add-In is also able to directly connect to BW systems (via a ODBO connection). Creating the connection requires the identification of the target BW system and the technical name of the source info provider.


Reporting OptionsEPM 10 Add-In BW Connections

The EPM 10 Add-In offers all of the BW info provider characteristics (as well as all available key figures) for inclusion into the report:


Agenda – Review

BW Terminology & BasicsBW Modeling OverviewBW/BPC Delta Load processBPC Data ManagerAutomationUsing BW/BPC reporting to validate the BW/BPC Integration process

–Business Explorer (BEx) Query Designer–BEx Analyzer–LISTCUBE–EPM 10 Add-In – BPC connections–EPM 10 Add-In – BW connections


Five Take Aways

1. The SAP Business Warehouse can extract, transform, and load (ETL) transactional and master data from a variety of SAP and non-SAP sources.

2. There is deep integration with ECC (and other SAP systems, such as CRM, APO, etc.) through the delivered BW extractors and target info providers.

3. A fully functional Delta Load process can easily be created using BW and BPC tools.

4. The load processes can be fully automated using BW process chains.

5. BW and BPC provide deep and cross integration with a variety of data reporting tools.


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, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

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. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, 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 other countries.

© 2011 SAP AG. All rights reserved

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company.

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.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 of SAP 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 of the 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 be changed 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 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.

Thank You!

Contact information:

Sheldon EdelsteinCSA [email protected]