BW Reconciliation. Applies to: Summary. Author Bio

Size: px

Start display at page:

Download "BW Reconciliation. Applies to: Summary. Author Bio"

Bartholomew Mathews
5 years ago
Views:

1 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 2011 SAP AG 1

2 Table of Contents Introduction:... 3 Approaches: We have different approaches for reconciliation Design Architecture... 3 Step By Step Process in Detail:... 4 Create Data Source based on RORQSTPRMS table and Enable Properties as Real time enable in SAP Source System Create Data Source based on RSSTATMANPART Table in BW System and Enable as Real time Enable.6 Direct Access Enabled Characteristic and Key Figure Creation:... 8 Creation Virtual provider:... 9 Transformation mapping details: DTP Creation between SAP Source System Data Source, BW Data Source and Virtual Info Cube Direct Access Activation on Virtual Info Cube: Demo on the Reconciliation process: Record Count Validation in SAP Source System Table Record Count Validation in BW System Table Validation of Source and Target tables record count in Virtual Info Provider Demo Result: Related Content Disclaimer and Liability Notice SAP AG 2

Introduction: In SDN we frequently get posts on Reconciliation, I have posted my comments/thoughts in the forums but this is common to everyone and many people still think how to do reconciliation.

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

4 Step By Step Process in Detail: Create Data Source based on RORQSTPRMS table and Enable Properties as Real time enable in SAP Source System. 1) Create Generic data source via RSO2 transaction, based on the RORQSTPRMS table in SAP Source system(r/3, CRM, APO...Etc). 2) Fill the required columns in RSO2, while creating generic data source as shown below Error! Reference source not found.. 3) it on the Generic Delta ( ) for maintaining data source as Real time enabled as shown below Error! Reference source not found SAP AG 4

5 4) Replicate the data source in BW side by selecting only the required application component node. Note: Do not replicate the BW Data Sources just for replicating one data source, because it will replicate all Meta data and takes lots of time and replicates all the newly/activated created data sources, which are not required data source. 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.e. ZRORQSTPRMS) as direct access. 1) Open RSDS transaction for replicated data source maintains. 2) Enable Data source as direct access by selecting Sync Extraction SAPI(for Direct Access and 2011 SAP AG 5

1) Create Generic data source via RSO2 transaction, based on the RSSTATMANPART table in BW system.

6 Tests) in Adaptor drop down of Data source Extraction menu as shown in the below. Create Data Source based on RSSTATMANPART Table in BW System and Enable as Real time Enable. 1) Create Generic data source via RSO2 transaction, based on the RSSTATMANPART table in BW system. 2) Fill the required columns of RSO2 transaction, while creating the generic data source as shown below Figure 4. 3) Enable Real time on the generic data source created on RSSTATMANPART table, Click on the Generic Delta ( ) tab in the menu level and enable Real-Time Enabl check mark SAP AG 6

4) Replicate the data source by selecting only the required application component node (i.e. in this scenario we have BW as application component as defined earlier (F5); hence we need to replicate on BW app component.

7 4) Replicate the data source by selecting only the required application component node (i.e. in this scenario we have BW as application component as defined earlier (F5); hence we need to replicate on BW app component. Note: Do not replicate the BW Data Sources just for replicating one data source, because it will replicate all the Meta data and takes lots of time and replicates all the newly created data sources, which are not really required for us. BW Data Source as direct access enabled:make sure to follow below steps for enabling Data source as direct access. 1) Open RSDS transaction for replicated data source (i.e. ZRSSTATMANPART) maintains. 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 SAP AG 7

8 6) Activate the Data source for making it into Active version. Direct Access Enabled Characteristic and Key Figure Creation: Create required Key figures i.e. Number of records sent and number records inserted..etc SAP AG 8

Create required characteristics (Request number, 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.

9 Create required characteristics (Request number, 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. Creation Virtual provider: For accessing both Source system data source and BW data source. 1) Create Virtual Info Cube via RSA1 and tick on Based on Data Transfer Process for Direct Access Radio button as shown below SAP AG 9

Data source (ZRSSTATMANPART). All the fields are direct mapping.

10 Below is the over view of Virtual info cube. Transformation mapping details: Create Transformation between Virtual Info Cube (ZVC_REC) and BW Data source (ZRSSTATMANPART). All the fields are direct mapping. Note: In this article, we are mapping only few fields, to get more details in the output we can map all other fields too. Below are the details of Transformation mapping details SAP AG 10

Similarly we need to create the transformation between Source system Data

DTP Creation between SAP Source System Data Source, BW Data Source and

Create DTP on DTP folder generated post transformation activation and

11 Similarly we need to create the transformation between Source system Data Source (ZRORQSTPRMS) and Virtual Info Cube (ZVC_REC). DTP Creation between SAP Source System Data Source, BW Data Source and Virtual Info Cube. Create DTP on DTP folder generated post transformation activation and activate the DTP. Similarly we need to create one more DTP between Source system Data Source (ZRORQSTPRMS) and Virtual Info Cube (ZVC_REC) SAP AG 11

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

Demo on the Reconciliation process: REQU_49VXXXXXXXXX is the Request number; we are taking for data validation/demo purpose.

12 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, 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; we are taking for data validation/demo purpose. Record Count Validation in SAP Source System Table. 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 AG 12

RCRDEXTR: Number of Data Records Extracted. RCRDSENT: Number of Sent Data Records. Record Count Validation in BW System Table. Validate the request record count by RSSTATMANPART table in BW side.

13 RCRDEXTR: Number of Data Records Extracted. RCRDSENT: Number of Sent Data Records. Record Count Validation in BW System Table. Validate the request record count by RSSTATMANPART table in BW side. 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. Validation of Source and Target tables record count in Virtual Info Provider. Below is the Virtual Info cube result for the request REQU_49VXAIBM04FUX8KPAEF3OAQGI. Demo Result: We are able to see same data record count in Virtual info cube as in Source request table and target request table. Note: >>In this example, I just took few fields for validation purpose, we can map other fields (Date, time, request status etc) for more details. >> As this an example, we have not created any report on the Virtual info provider, data is directly read from Info provider itself and posted the result in the article SAP AG 13

14 Related Content Dictionary Fields of RORQSTPRMS Table Dictionary Fields of RSSTATMANPART table. My Previous Submissions in SAP SDN Portal: 1. Navigational attribute F4 Help Performance Improvement. 2. BI - Informatica Integration Architectural. For more information, visit the EDW homepage 2011 SAP AG 14

15 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. Changes made based on this information are not supported and can be overwritten during an upgrade. SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk. 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, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document SAP AG 15