how to implement delta loading of transaction data from ecc and bw 7.3 into bpc using delta...

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 1

How to Implement Delta Loading

of Transaction Data from ECC and

BW 7.3 into BPC using Delta

Initialization in BPC 10NW

Applies to:

SAP BusinessObjects Planning and Consolidation 10, version for SAP NetWeaver ( SP04 and above),

SAP BW 7.3 ( SP04 and above) and EPM Add-In SP04 patch01 or EPM Add-In SP05 and above.

For more information, visit the Enterprise Performance Management homepage.

Summary

This How-to Guide demonstrates to implement and load ECC FI-GL Transaction data from BW 7.3 into SAP BPC Planning Application ( BusinessObjects Planning and Consolidation 10, version for SAP NetWeaver ) using new Import delta Data Package which runs Delta initialization delivered in SP04 of BPC10NW .It focuses on loading ECC FI-GL transaction data of BW 7.3 infoprovider into SAP BPC 10 NW Planning Application using delivered mechanism with or without any Staging infoprovider as an optional step per business requirement when integrating ECC Transaction data into BPC.

Author: Nakkeeran Govindasamy

Company: SAP America

Created on: 6 January 2012.

Author Bio

Nakkeeran Govindasamy ,PMP is Principal EPM Consultant - Solution Architect EPM/BPC & BI and Ramp-up Coach has around fifteen years of work experience in various products in SAP space and working at SAP America for last 5 years , where he was a key contributor and impact player in the success of multiple customer ERP/BI/IP/BPC go-lives, including all aspects of project lifecycles.

He was working as SAP BI Solution Architect with more than 10 years experience in SAP BI/BW/BPC implementation, Support and Enhancement projects.His SAP expertise includes extensive knowledge of SAP BPC 7.x ,BPC 10NW , BI 7.x and its integration

with other SAP ( ECC, CRM,APO, etc) and non-SAP systems.

.

https://www.sdn.sap.com/irj/sdn/bpx-epm

How to implement Delta loading of Transaction data from BW 7.x to BPC10NW


© 2010 SAP AG 2

Table of Contents

1. Document History and Related Notes. .................................................................................................. 3

2. Assumption and Design option. ............................................................................................................. 3

2.1. Scenario 1 : Using New BW Infoprovider as part of the staging process . ............................................ 3

2.1.1. End to End Dataflow for BPC Delta load using BW. ............................................................................. 4

2.2. Scenario 2 : Using delivered or Existing BW Cube ( eg,0FIGL_C10) as Source Infoprovider . ............ 4

2.2.1. Assign the required Task profile (Edit Delta Initialization) to the Team or the User. ............................. 5

2.2.2. Create Transformation file to Map the BPC Dimensions to the source BW infoobjects in BPC. .......... 6

i. Create the Delta Initialization in BPC Data manager in EPM Add-in. ................................................... 8

ii. Create the Data manager Package for ‘Import Delta Transaction Data from BW info-provider’. ........ 10

iii. Run the Delta Initialization using Delta Import Data Manager Package with required Data selection.11

iv. Run subsequent delta load for the initialized data selection using BPC DM Package. ...................... 12

v. Data Validation: View Package status and run Validation Check using Report. ................................. 12

3. BPC / BW Security Requirement ......................................................................................................... 14

Related Content ................................................................................................................................................ 15

Copyright........................................................................................................................................................... 16



© 2010 SAP AG 3

1. Document History and Related Notes.

Document Version Description

1.1 Added references to related SAP Notes 1.2 Dataflow and assumption added.

BPC 10 NW related SAP Notes

Please make sure your system is up to date by installing the latest support package, or the below notes individually, before attempting to follow the examples in this How to Guide.

SAP BPC and BW Support Package pre-requisites and notes:

SAP BusinessObjects Planning and Consolidation 10, version for SAP NetWeaver (SP04 & above) ( SP05 & above recommended).

SAP BW 7.3 ( SP04 and above)

EPM Add-In SP04 patch01 or EPM Add-In SP05 and above.

Note 1616508 - support InfoProvider delta loading

2. Assumption and Design option.

1. Data is already loaded from ECC into BW 7.3 Infoprovider ( eg,0FIGL_C10 new GL infoprovider) 2. Optional step of Staging Infoprovider ZFIGL_C10 which is not a technical requirement to

implement this Delta initialization functionality ,but NOT to impact the Delivered Infoprovider which is used for BW reporting ,if it is required to enhance more characteristics or to leverage BW Data transformations for BPC .

3. Do not compress BW cubes until all delta records loaded into BPC Model. - If you lost the delta request by compressing BPC staging Cube ,we have to run delta init or

full load with selected period .BW Reporting cube requests does not get compressed ,if the requests not reached to the connected further targets.

2.1. Scenario 1 : Using New BW Infoprovider as part of the staging process .

Reasons for introducing the staging infoprovider :

A) Do not have to modify /impact the delivered info cube used for BW reporting. - Adding new Characteristic like ‘Trading Partner’ to the infoprovider.

B) Leverage BW Transformation while loading from Delivered BW cube to Staging cube to simplify the BPC Transformation and conversion. - Populating empty Char or Dimension with ‘NONE’. - Any Derivation of member using ABAP logic.

C) Data selection, Aggregation and enrichment as per the Business need in the source itself. D) BPC Staging cube or Staging DSO can be loaded in parallel from BW Staging DSO ,while

loading BW Reporting cube as an option ,if you want to reduce the load time.

Pre-requisite Steps to implement the delta load with staging infoprovider:

1. Create the New staging cube copying from delivered infocube and modify it with required characteristics and key figures.

2. Create Transformation and DTP with all mapping logic and data selection. 3. Load the Data into the New Staging infoprovider from delivered infocube.

o Load data from 0FIGL_C10 to ZFIGL_C10.



© 2010 SAP AG 4

2.1.1. End to End Dataflow for BPC Delta load using BW.

2.2. Scenario 2 : Using delivered or Existing BW Cube ( eg,0FIGL_C10) as Source Infoprovider .

- Without Using New BW Infoprovider as part of the staging process .

If the customer already using enhanced infoprovider or the delivered cube meets the business requirement for BW reporting and source for the BPC Data load, you can use the delivered BW cube as the source infoprovider.

There are following Steps to implement the Delta load process without using a Staging infoprovider:

1. Assign the required Task profile (Edit Delta Initialization) to the Team or the User. 2. Create Transformation file to Map the BPC Dimensions to the source BW infoobjects in BPC. 3. Create the Delta Initialization in BPC Data manager in EPM Add-in. 4. Create the Data manager Package for ‘Import Delta Transaction Data from BW info-provider’. 5. Run the Delta Initialization using Delta Import Data Manager Package with required Data selection.. 6. Run subsequent delta load for the initialized data selection using BPC DM Package. 7. Data Validation: View Package status and run Validation Check using Report.



© 2010 SAP AG 5

2.2.1. Assign the required Task profile (Edit Delta Initialization) to the Team or the User.

BPC Administration Security - Task Profiles.

Create a new Task profile or add ‘Edit Delta Initialization’ Task of the Data manager to the existing Task profile of your Team.



© 2010 SAP AG 6

2.2.2. Create Transformation file to Map the BPC Dimensions to the source BW infoobjects in BPC.

1. Launch EPM Add-in Data Manager - Transformation File - New Transformation file

2. Transformation Mapping and conversion file to map the BW data to BPC dimension members . .

Time conversion file (TIME.xls) is used in the Transformation file while loading ECC FIGL data into BPC Planning app to control and restrict the Periods to be loaded or to MAP where period 0 ,13,14,15 or 16 is loaded.

EXTERNAL INTERNAL

2008.00 2008.01

2008.13 2008.12

2008.14 2008.12

2008.15 2008.12

2007.00 2007.01

2007.13 2007.12

2007.14 2007.12

2007.15 2007.12



© 2010 SAP AG 7

2007.16 2007.12

BPC Transformation is used to Map ECC field values to the required BPC Dimension members while loading into BPC Planning application.

TRANSFORMATION MAPPING TABLE (Example data):

ECC Data BW Staging

Cube BPC Dimensions

0000430100 0000430100 A430100 ACCOUNT

Actual VERSION

2008001 2008001 2008.01 TIME

BW AUDITTRAIL

10 10 USD CURRENCY

NONE I_NONE TRADING_PARTNER

Balance FLOW

3000 3000 3000 COMPANY_CODE

SM100 SM100 PC_2000SM100 PROFIT_CENTER

SM300 SM300 CC_2000SM300 COST_CENTER

0400 0400 FA_0400 FUNCTIONAL_AREA

1234.00 1234.00 1234.00 AMOUNT/SignData

*OPTIONS

FORMAT = DELIMITED

HEADER = YES

DELIMITER = ,

AMOUNTDECIMALPOINT = .

SKIP = 0

SKIPIF =

VALIDATERECORDS=YES

CREDITPOSITIVE=NO

MAXREJECTCOUNT=-1

ROUNDAMOUNT=

*MAPPING

VERSION=*NEWCOL(BW)

TIME=0FISCYEAR+*STR(.)+ 0FISCPER3(2:3)

AUDITTRAIL=*NEWCOL(Input)

CURRENCY=*NEWCOL(USD)

TRADING_PARTNER=*STR(I_)+0PCOMPANY

FLOW=*NEWCOL(Balance)



© 2010 SAP AG 8

COMPANY_CODE=*STR(CO_)+0COMP_CODE

PROFIT_CENTER=*STR(PC_)+0CO_AREA+ 0PROFIT_CTR(5:10)

COST_CENTER=*STR(CC_)+0CO_AREA+ 0COSTCENTER(5:10)

FUNCTIONAL_AREA=*STR(FA_)+ 0FUNC_AREA

ACCOUNT=*STR(A_)+0GL_ACCOUNT(5:10)

AMOUNT=Z_SDATA

*CONVERSION

TIME=TIME.xls

ACCOUNT=ACCOUNT.xls

Note : Last 6 Char of Profit center, Cost center, accounts is loaded to avoid leading Zero ( BW infoobject Alpha routine could be used to eliminate leading zero ,if BPC staging cube is used).

i. Create the Delta Initialization in BPC Data manager in EPM Add-in.

Launch EPM Add-in Data Manager

Goto Organize Organize Delta Initialization



© 2010 SAP AG 9

Make sure CHECK ‘ TRIGGER FULL LOAD AT FIRST RUN’ and Select the Transformation file created

And also able to select the Dimensions and selection filter for Initializing the Delta.

Choose the Source Infoprovider ( either delivered BW cube or the staging infoprovider with enhanced char and BW transformations.

1. Selecting check box ‘TRIGGER FULL LOAD AT FIRST RUN’ ,so the initialization run bring the full load and subsequent run bring delta records.

2. Can select the Dimensions and selection filter for Initializing the Delta.



© 2010 SAP AG 10

ii. Create the Data manager Package for ‘Import Delta Transaction Data from BW info-provider’.

Launch EPM Add-in Data Manager -- Organize - Organize Package List.

Check the following TASK also exist in the Advanced Script while generating the standard Data Package. TASK(/CPMB/SOURCE_DELTA_IP,BYPASS_COMPRESS,0)

…

TASK(/CPMB/APPEND_LOAD_DELTA_IP,INFOPROV_INIT_NAME,%INFOPROV_INIT_NAME%)

CREATE DATA PACKAGE- using the Process-chain /CPMB/LOAD_DELTA_IP which is under the Data collection folder of BPC DM in EPM Add-in Excel interface.

Note : Use DM Package Link- to Trigger end to end Delta load from source system to BW and BW to BPC in EPM Add-in Excel interface.



© 2010 SAP AG 11

iii. Run the Delta Initialization using Delta Import Data Manager Package with required Data selection.

Launch EPM Add-in Data Manager --Run Package

Execute Run Package

Choose ’ Import Transaction Data from BW via Delta Load’ and RUN

Select Delta Initialization FIGL_DELTA_INIT ( Delta init created ) --- > NEXT



© 2010 SAP AG 12

iv. Run subsequent delta load for the initialized data selection using BPC DM Package.

Re-execute the Data package and Run the same Delta Init using the Delta DM Package and check this time load brought only the delta records.

v. Data Validation: View Package status and run Validation Check using Report.



© 2010 SAP AG 13

With subsequent Data load with no changes :

VIEW Data Package Status :

1. First run brought all the selected records – Delta init executed like a FULL Load . 2. Subsequent Delta load with now changes in the source data( infoprovider brought No reocords. 3. Another subsequent Load of the same Data delta package brought more New data from source cube

ONLY the New records loaded in the source infoprovider.



© 2010 SAP AG 14

3. BPC / BW Security Requirement

Task Profile : Need DM – Execute task profile to execute the Package along with’ Edit Delta Initialization’ Tasks to create and execute the delta initialization and subsequent delta loads..



© 2010 SAP AG 15

Related Content

1. Looking for BPC demos, customer references, roadmaps, performance and sizing information, training, documentation or tips & tricks?

http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/26506

2. Useful EPM Content

http://www.sdn.sap.com/irj/scn/articles-epm-all

http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/26506

http://www.sdn.sap.com/irj/scn/articles-epm-all



© 2010 SAP AG 16

Copyright

© Copyright 2012 SAP AG. All 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, 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 Business ByDesign, 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.

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 S.A. in the United States and in other countries. Business Objects 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.

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 Group products 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.

how to implement delta loading of transaction data from ecc and bw 7.3 into bpc using delta...

Documents

sap bw

sap ecc

sap ag

sap america

sap expertise

sap space

sap businessobjects

sap netweaver sp04