e-dokumen.com

Data Extraction and Retraction inBPC-BIApplies to:Document is applicable to all the BPC 7.0 NW version users and the users BI 7.0 integration with BPC. Formore information, visit the Enterprise Performance Management homepage.SummaryThis document provides an overview of data integration between BPC NW with BI 7.0. SAP Net weaver 7.0BI is used as the backend server to hold BPC data. Since BPC tool is used for planning and reportingpurposes, master and transactional data is stored in SAP NW BI objects and tables needs to be pushed toBPC for the reporting of planned and historical data and similarly planned data in BPC can be retracted asnecessary.Author:Kavyashree BKCompany: Infosys Technologies LimitedCreated on: 25 April 2010Author BioKavyashree is a software engineer working for Infosys technologies for the past 2.5 years as a BWconsultant. She has BW skills and along with that the knowledge of BPC-BI integration.SAP COMMUNITY NETWORK 2010 SAP AGSDN - sdn.sap.com BPX - bpx.sap.com BOC - boc.sap.com1

Data Extraction and Retraction in BPC-BITable of ContentsIntroduction . 3Objective. 3Data Extraction . 4Methods of Data Extraction . 4Using BW- ETL process. 4Using Data Manager Functionality . 7Data Retraction . 10Flat File Method . 10Using Query, APD . 10Conclusion . 11Related Contents . 12Disclaimer and Liability Notice . 13SAP COMMUNITY NETWORK 2010 SAP AGSDN - sdn.sap.com BPX - bpx.sap.com BOC - boc.sap.com2

Data Extraction and Retraction in BPC-BIIntroductionSAP BPC is web based collaborative solution that unifies the business planning and performancemanagement process. It is a tool to accomplish the activities of Performance Management – Planning,Financial Consolidation, and Reporting.BPC 7.0 is closely integrated with BI. Whenever an object is created in BPC, correspondingly a BI object iscreated at the back end BI. This close integration enables data movement from BI to BPC and vise versa.For example, for every new dimension created in BPC, a BW characteristic info object is generated in theBPC namespace.ObjectiveSAP BI is used for data warehousing and reporting of historical and transaction data. Hence actual data andhistorical data reside in BI. Consolidated view of planning data and actual data is required for planning andreporting purposes when a client is installing SAP BPC. This requires data integration between SAP BPCand SAP BI. This data integration can be achieved by extraction of BW data into BPC and building BPCreports showing both plan and extracted actual data.Data integration also involves planned data extraction from BPC to BI for the evaluation and comparisonpurposes.1. Data Extraction (BI to BPC): To consolidate all the data from various modules into BPC cube(according to modules).2. Data Retraction (BPC to BI): Push back the Planned and Budgeted Data from BPC Cubes to BI.SAP COMMUNITY NETWORK 2010 SAP AGSDN - sdn.sap.com BPX - bpx.sap.com BOC - boc.sap.com3

Data Extraction and Retraction in BPC-BIData ExtractionSAP Netweaver 7.0 BI is used as the backend server to hold BPC data. The master and transactional datais stored in SAP NW BI objects and tables. This makes the BW data extraction and retraction feasible. BPCengine can access data only from the system generated cubes in BPC namespace. Actual data is needed forreporting and planning purposes which resides in BI Cubes. Hence there is a need to extract BI transactiondata into BPC cubes for combined reporting of actual and planned data.Methods of Data ExtractionEven though BPC also stores the data in SAP BI cubes, it is not recommended that we access the datastored in the cubes in /CPMB namespace using the Business explorer. Similarly, BPC engine can accessdata only from the system generated cubes in /CPMB namespace. Hence a combined reporting of actualand plan data can be achieved by extraction of BI transaction data into the BPC cubes. The figure belowdepicts the same.We can have two different methods of loading data from BI to BPC. They are,1. Using BW- ETL process2. Using data manager functionalityUsing BW- ETL processTransaction Data from Net weaver BI info cube or Data Store Object (Non-BPC info providers) to an infocube generated in the BPC namespace, we can use ETL method to load the data by making the necessarytransformations and master data look ups.In Data Warehousing Workbench (Transaction code RSA1) define Data transfer process for BPC infocubeusing context menu of info provider tree.SAP COMMUNITY NETWORK 2010 SAP AGSDN - sdn.sap.com BPX - bpx.sap.com BOC - boc.sap.com4

Data Extraction and Retraction in BPC-BIThe BI cube/ DSO from which data has to be extracted should be given as Source of DTP. The DTP typeshould be selected as Standard. Please refer following link to learn more about DTP functionalities.http://help.sap.com/erp2005 ehp rameset.htmEnter the details of DTP mentioning Description, source object type and source object technical names.BPC generated info cube is a Real time info cube. Hence before executing the DTP, the info cube needsmode needs to switched to loading mode. Once the loading is done, it should be switched back to Planningmode as shown below.Chose option Change Real-Time Load Behavior from the context menu of infocube. Switch to “Real-timedata target can be loaded with Data ; Planning not allowed” Option.SAP COMMUNITY NETWORK 2010 SAP AGSDN - sdn.sap.com BPX - bpx.sap.com BOC - boc.sap.com5

Data Extraction and Retraction in BPC-BIOnce the real time load behavior is changed, the DTP can be executed. After loading, cube must beswitched back to second option i.e. Real-Time data target can be planned; data loading not allowed followingthe same procedure. It is recommended to use process chain to define and schedule a data transferprocess. The process type Data Transfer Process is available in the Load Process and Post processingprocess category which should be used while creating process chain using Transaction code RSPC. Processtypes for switching real time load behavior are also available.Limitations of ETL process. Whenever the load is being done to BPC Cube, the same will not be available for Planning and viceversa. During ETL process, the validation mechanism in BPC7NW is skipped. This might lead to invalidrecords entry in BPC Cubes. If full optimization is done for the BPC Application, a new optimized cube is generated and all theETL work that was done for the previous cube will be dropped from the new cube.SAP COMMUNITY NETWORK 2010 SAP AGSDN - sdn.sap.com BPX - bpx.sap.com BOC - boc.sap.com6

Data Extraction and Retraction in BPC-BIUsing Data Manager FunctionalityData Manager is a BPC module that helps us move data in to BPC, as well as copy or move data within andacross BPC applications. In addition to allowing us to move and copy data, Data Manager supports mappingand complex transformations of data. It requires a transformation file to be created for field mapping betweenBPC and BI. Data Manager is integrated with BPC for Excel. To start Data Manager, choose BPC Desktopicon BPC for Excel.In the BPC for excel action pane, select Manage Data. For users who are familiar with menus instead of theaction pane, BPC has an “eData” dropdown menu to choose all the actions available within Data ManagerAction pane else BPC also has a Data Manager Toolbar through which data manager can be accessed.Select the Data Management folder listed under the application name. From the packages listed in the rightpane, select „Load Data‟ package and click „Run‟.SAP COMMUNITY NETWORK 2010 SAP AGSDN - sdn.sap.com BPX - bpx.sap.com BOC - boc.sap.com7

Data Extraction and Retraction in BPC-BIThe BI Info provider (Cube or DSO) name whose data has to be extracted has to be entered in the dialogbox and a transformation file needs to be selected. The status of the package can be checked using viewstatus option shown below.1. The package also gives the following options2. Import method : Merge – Imports all records, leaving all remaining records in destination intact;Replace and clear – clears data for any existing records that mirror each entity/category/timecombination defined in the source and then imports source records3. Default logic to be run or not4. Work status to be checked or not when importing data as shown in below screenshot5. Run now/ Schedule.SAP COMMUNITY NETWORK 2010 SAP AGSDN - sdn.sap.com BPX - bpx.sap.com BOC - boc.sap.com8

Data Extraction and Retraction in BPC-BIThe status of the package can be checked using view status option available in Data manager.SAP COMMUNITY NETWORK 2010 SAP AGSDN - sdn.sap.com BPX - bpx.sap.com BOC - boc.sap.com9

Data Extraction and Retraction in BPC-BIData RetractionData Retraction (BPC to BI) is a method to move the Planned and Budgeted Data from BPC Cubes to BI.There is no standard functionality provided by SAP to achieve retraction. Data manager can only be used forextraction purposes (Moving data from BI to BPC namespace).This can be achieved using below methods.1. Flat file method2. BEX Query, APDFlat File MethodIn this method, entire BPC data is downloaded to a flat file using data downloader functionality available inBPC cubes or using data manager functionality of BPC front end. The data from this flat file is extracted intoa flat file data source and further loaded to info providers in BI. Necessary reverse transformations andreverse lookups are maintained while loading data from flat file data source to data targets in BI flat files hasto be maintained in Application server.Using Query, APDSimple BEX Query is built on BPC cubes to extract entire data with all the fields Query designer. A directupdate DSO is built with the fields similar to BPC Cube fields. Analysis process designer is created for themovement of Query results to direct update DSO. From this stage, data can be further moved to anotherStandard DSO or Cube based on the requirement with necessary reverse transformations logicNote: It is not recommended that we access the data stored in the cubes in BPC namespace using the BusinessexplorerSAP COMMUNITY NETWORK 2010 SAP AGSDN - sdn.sap.com BPX - bpx.sap.com BOC - boc.sap.com10

Data Extraction and Retraction in BPC-BIConclusionThe data in BI Cubes can be converted into data available in BPC Cubes by using functionalities inTransformations - Rule Groups and LookUps.As of now for Retraction, the Data from BPC Cubes is first moved to a Flat file and then loaded to BI cubeswith the help of flat file data sources. The reverse lookups are carried out in transformations between datasources and cube. (Another way of taking out data from BPC cubes – by using APD – pulling out the datausing a query and loading into a DSO in BI- This is in progress. Not sure if it is recommended method).SAP COMMUNITY NETWORK 2010 SAP AGSDN - sdn.sap.com BPX - bpx.sap.com BOC - boc.sap.com11