BW Reconciliation

Applies to:
SAP Net Weaver Business Warehouse (Formerly BI) Business Intelligence homepage. For more information, visit the Business Intelligence homepage. For more information, visit the EDW homepage.

Summary
This Article will explain you about BI/BW “Data Reconciliation” process by accessing Source Request table and Target Request table in BW Virtual info Cube. Reconciliation is the process of comparing the Source system (SAP Source) data with Target system data (BI/BW System). Author: Maruthi Chowdary Movva

Company: HP Created on: 1 January 2011

Author Bio
Maruthi Chowdary Movva is a SAP BI consultant having around 6 years of Experience in SAP BI, Working with HP. He has extensively worked in SAP BW/BI Development, Production Support, BI Technical Upgrade and Functional upgrade projects

SAP COMMUNITY NETWORK © 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 1

.................................................................................................... ................................. BW Data Source and Virtual Info Cube.... 12 Record Count Validation in SAP Source System Table.......boc............ 12 Record Count Validation in BW System Table............................................uac............................................................. 13 Demo Result: ............................................... ..................................................... ................................................................... 10 DTP Creation between SAP Source System Data Source....................................BW Reconciliation Table of Contents Introduction: ..................................................................... 3 Design Architecture ................................................................................. 11 Direct Access Activation on Virtual Info Cube: ......sap.....................................com | BOC .......................................com 2 ........sdn............................................................................................................................................................................... 3 Approaches: We have different approaches for reconciliation.......................................com | UAC ...........................................................................................................................................sap...................................... 13 Validation of Source and Target tables record count in Virtual Info Provider.............................................................................................................................................. 8 Creation Virtual provider: ............................................................................................................................................... 13 Related Content ................................................................. . 9 Transformation mapping details: ..................... 12 Demo on the Reconciliation process: ...........................sap..................................................................................................................................sap........6 Direct Access Enabled Characteristic and Key Figure Creation:...... ....... 3 Step By Step Process in Detail: ..................................................bpx........ ...................... 4 Create Data Source based on RSSTATMANPART Table in BW System and Enable as “Real time Enable”..............................................com | BPX ............ 14 Disclaimer and Liability Notice ......... 4 Create Data Source based on RORQSTPRMS table and Enable Properties as “Real time enable” in SAP Source System................. 15 SAP COMMUNITY NETWORK © 2011 SAP AG SDN .......

com | BOC . I am going to explain reconciliation process by taking the 3 approach. This provoked me pen this article.com 3 . 3) Accessing the Source request table and target request table directly in BW side via Virtual Info cube.BW Reconciliation Introduction: In SDN we frequently get posts on Reconciliation.sdn.sap.uac.sap. which will give count of records for the particular day and Create Report on the Virtual Provider.com | BPX . Do RRI form BW report to the Application Table report. Approaches: We have different approaches for reconciliation.sap.com | UAC . 2) Creating ABAP report on the RORQSTPRMS tables in SAP source system and Create Report on Virtual Provider created on the RSSTATMANPART in BW. I have posted my comments/thoughts in the forums but this is common to everyone and many people still think how to do reconciliation. Do RRI from BW report to the Application Table report. 1) Creating ABAP report on the SAP Base Application tables in Source system with one of the KPI.sap. rd Design Architecture SAP COMMUNITY NETWORK © 2011 SAP AG SDN . which was created on the BW data target.boc.bpx. In this article.

2) Fill the required columns in RSO2.sap.Etc).com | UAC ..uac.com 4 . while creating generic data source as shown below Error! Reference source not found.sdn. APO. based on the RORQSTPRMS table in SAP Source system(R/3. CRM..sap.sap.com | BOC .boc.com | BPX ..sap.BW Reconciliation Step By Step Process in Detail: Create Data Source based on RORQSTPRMS table and Enable Properties as “Real time enable” in SAP Source System.. SAP COMMUNITY NETWORK © 2011 SAP AG SDN .bpx. 1) Create Generic data source via RSO2 transaction. 3) it on the Generic Delta ( ) for maintaining data source as Real time enabled as shown below Error! Reference source not found.

com | UAC .uac.sap. ZRORQSTPRMS) as direct access.com | BOC .com 5 . 1) Open RSDS transaction for replicated data source maintains.sap. 5) Enabled Source system Data source as direct access in BW post Data Source replication: Make sure to follow below steps for enabling Data source (i.com | BPX .sap.BW Reconciliation 4) Replicate the data source in BW side by selecting only the required application component node. 2) Enable Data source as direct access by selecting Sync Extraction SAPI(for Direct Access and SAP COMMUNITY NETWORK © 2011 SAP AG SDN . which are not required data source.bpx.e.boc. because it will replicate all Meta data and takes lots of time and replicates all the newly/activated created data sources. Note: Do not replicate the “BW Data Sources” just for replicating one data source.sap.sdn.

sap. Click on the Generic Delta ( ) tab in the menu level and enable “Real-Time Enabl” check mark. 2) Fill the required columns of RSO2 transaction. while creating the generic data source as shown below Figure 4.sdn. 1) Create Generic data source via RSO2 transaction.com | BOC .com | BPX .bpx.uac.BW Reconciliation Tests) in “Adaptor” drop down of Data source “Extraction” menu as shown in the below. 3) Enable “Real time” on the generic data source created on RSSTATMANPART table. based on the RSSTATMANPART table in BW system.sap.com | UAC .boc.sap. Create Data Source based on RSSTATMANPART Table in BW System and Enable as “Real time Enable”. SAP COMMUNITY NETWORK © 2011 SAP AG SDN .com 6 .sap.

ZRSSTATMANPART) maintains.uac.sap.sap.bpx.e. SAP COMMUNITY NETWORK © 2011 SAP AG SDN . 1) Open RSDS transaction for replicated data source (i.BW Reconciliation 4) Replicate the data source by selecting only the required application component node (i.e.sap. because it will replicate all the Meta data and takes lots of time and replicates all the newly created data sources.sdn.com | UAC .com | BPX .com | BOC . Note: Do not replicate the “BW Data Sources” just for replicating one data source. in this scenario we have BW as application component as defined earlier (F5). BW Data Source as direct access enabled:Make sure to follow below steps for enabling Data source as direct access.sap. 2) Enable Data source as direct access by selecting “Sync Extraction SAPI”(for Direct Access and Tests) in “Adaptor” drop down of Data source Extraction menu as shown in the below.boc. hence we need to replicate on BW app component. which are not really required for us.com 7 .

com | UAC .sap. Number of records sent and number records inserted.uac.sap.com 8 .sap.com | BPX .boc. Direct Access Enabled Characteristic and Key Figure Creation: Create required Key figures i.etc.sdn.sap.. SAP COMMUNITY NETWORK © 2011 SAP AG SDN .bpx.e.com | BOC .BW Reconciliation 6) Activate the Data source for making it into Active version.

sap.com | BOC .com | BPX .sap.sap.uac.BW Reconciliation Create required characteristics (Request number.com | UAC .sap.boc. SAP COMMUNITY NETWORK © 2011 SAP AG SDN . Data target and Data target type) and enable direct access in Master Data Access drop down under Master data/Text menu level as shown below. 1) Create Virtual Info Cube via RSA1 and tick on “Based on Data Transfer Process for Direct Access” Radio button as shown below.sdn.com 9 .bpx. Creation Virtual provider: For accessing both “Source system data source” and “BW data source”.

uac. All the fields are direct mapping.boc. Below are the details of Transformation mapping details.com 10 .com | UAC .sap. to get more details in the output we can map all other fields too.bpx.BW Reconciliation Below is the over view of Virtual info cube. we are mapping only few fields.sap.com | BPX .sap. SAP COMMUNITY NETWORK © 2011 SAP AG SDN .sap. Transformation mapping details: Create Transformation between Virtual Info Cube (ZVC_REC) and BW Data source (ZRSSTATMANPART).sdn.com | BOC . Note: In this article.

SAP COMMUNITY NETWORK © 2011 SAP AG SDN .com 11 .com | BOC .sap.boc.BW Reconciliation Similarly we need to create the transformation between Source system Data Source (ZRORQSTPRMS) and Virtual Info Cube (ZVC_REC). BW Data Source and Virtual Info Cube.com | UAC .sap. Create DTP on DTP folder generated post transformation activation and activate the DTP.sap.sdn.sap. DTP Creation between SAP Source System Data Source.uac.bpx. Similarly we need to create one more DTP between Source system Data Source (ZRORQSTPRMS) and Virtual Info Cube (ZVC_REC).com | BPX .

sap. Go to context menu of the Virtual info provider and tick on Activate Direct Access. Demo on the Reconciliation process: REQU_49VXXXXXXXXX is the Request number.com | BPX .boc.sap.com | UAC .BW Reconciliation Direct Access Activation on Virtual Info Cube: Finally step is in this process is to activate the direct access on the Virtual provider created for reconciliation process.sap.uac. SAP COMMUNITY NETWORK © 2011 SAP AG SDN . we are taking for data validation/demo purpose.sdn. Record Count Validation in SAP Source System Table.com 12 .bpx. Check the number of records sent and Number of records extracted via RORQSTPMS table in SAP source system. We have 3 records extracted and 3 records sent in the RORQSTPMS table as shown below.sap.com | BOC .

we have not created any report on the Virtual info provider.com | UAC .com | BPX .sap. Demo Result: We are able to see same data record count in Virtual info cube as in Source request table and target request table.sdn. SAP COMMUNITY NETWORK © 2011 SAP AG SDN .com 13 . Note: >>In this example. Validation of Source and Target tables record count in Virtual Info Provider. I just took few fields for validation purpose. Record Count Validation in BW System Table.sap. Below is the Virtual Info cube result for the request REQU_49VXAIBM04FUX8KPAEF3OAQGI.sap.bpx. Validate the request record count by RSSTATMANPART table in BW side.uac. RCRDSENT: Number of Sent Data Records.boc. data is directly read from Info provider itself and posted the result in the article.BW Reconciliation RCRDEXTR: Number of Data Records Extracted. request status …etc) for more details. We have 3 records extracted into BW and 2 records inserted as shown below. ANZ_RECS: Number of Selected Data Records INSERT_RECS: Number of Selected Data Records inserted.com | BOC . time. >> As this an example. we can map other fields (Date.sap.

For more information.sap.com | BPX .boc.sap. visit the EDW homepage SAP COMMUNITY NETWORK © 2011 SAP AG SDN .bpx.Informatica Integration Architectural”.uac. “Navigational attribute F4 Help” Performance Improvement.BW Reconciliation Related Content Dictionary Fields of RORQSTPRMS Table Dictionary Fields of RSSTATMANPART table.com 14 . BI .sdn.sap.com | BOC .sap. 2.com | UAC . My Previous Submissions in SAP SDN Portal: 1.

SAP responsible or liable with respect to the content of this document. SAP COMMUNITY NETWORK © 2011 SAP AG SDN .sap. and anyone using these methods does so at his/her own risk.com | UAC .sap.uac.BW Reconciliation Disclaimer and Liability Notice This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP.sap.bpx.sdn.com 15 .com | BOC . code or methods suggested in this document. including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP.boc.com | BPX . You agree that you will not hold. Changes made based on this information are not supported and can be overwritten during an upgrade. or seek to hold. SAP will not be held liable for any damages caused by using or misusing the information. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample.sap.