This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
SAP NetWeaver Business Warehouse (Formerly BI) & ECC 6.0. Business Intelligence homepage.
Summary
This article tells about how to check the data using Extractor Checker (Transaction Code: RSA3) in ECC.
Author: Surendra Kumar Reddy Koduru
Company: ITC Infotech India Ltd. (Bangalore/INDIA)
Created on: 27 November 2009
Author Bio
Surendra Kumar Reddy Koduru is a SAP BI Lead Consultant currently working with ITC Infotech India Ltd (Bangalore/INDIA). He has got rich experience and worked on various BW/BI Implementation/Support Projects.
Live Scenario:............................................................................................................................................ 3
Related Content .......................................................................................................................................... 20
Disclaimer and Liability Notice ..................................................................................................................... 21
Checking the Data using Extractor Checker (RSA3) in ECC Delta and Repeat Delta etc...
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
After reading this article, you will know how to the check the data/records for Delta and Repeat Delta options using Extractor Checker (Transaction Code: RSA3) in ECC.
LBWQ:
qRFC Monitor for the outbound queue, we use this transaction to monitor the status of the LUWs in the outbound queue and restart any hanging queues manually.
RSA7:
BW Delta Queue Monitor, we use this to see transferred data (delta) for a DataSource and a Target system.
RSA3:
The extractor checker can test extracted data at the source, allowing you to find data errors/inconsistencies at an early stage (before data loads into the Target System)
Live Scenario:
We want to know/test how many records there in Delta Queue and Repeat Delta Queue in ECC. Because we can’t count the number of records in LBWQ/SMQ1 or by looking at Total in RSA7, so here we need to use Extractor Checker to check and count the records.
Here I’m explaining the live scenario by using 2LIS_03_BF Extractor/DataSource. And I’m assuming that we already loaded Init load using 2LIS_03_BF Extractor/DataSource in BI/BW and need to load Deltas.
Detailed Steps:
Please follow the below steps…
Step: 1
Go to LBWQ and see the entries for 2LIS_03_BF Extractor/DataSource.
Checking the Data using Extractor Checker (RSA3) in ECC Delta and Repeat Delta etc...
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
Note: I’m assuming that, we already executed Init loads for 2LIS_03_BF DataSource successfully and we are ready to o
for Delta Loads in BI/BW Server.
Step: 2
Go to RSA7 - BW Delta Queue Monitor and see the Total for 2LIS_03_BF Extractor/DataSource.
Update Modes:
Delta update:
A delta update only requests data which has appeared since the last delta. Before you can request a delta update, you must first initialize the delta process.
A delta update is only possible for loading from SAP source systems.
Repeat Delta:
If a delta fails (status ’red’ in the monitor) or the overall status of the delta request has been set to red manually, the next data request will be performed in repeat mode.
A repeat request extracts the incorrect or incompletely loaded data from the failed delta request, along with any new data since the original request. A repeat can only be requested in the dialog. If data from the failed delta request has already been updated to the data targets, delete the data from the data targets affected. If you cannot delete the data from the data targets, duplicate data records may be produced when the repeat request is performed.
Select Delta Update and execute.
Checking the Data using Extractor Checker (RSA3) in ECC Delta and Repeat Delta etc...
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
There are no records in Delta Queue, but still it is showing some records i.e. under Totals it is displaying 2. But actually there are no records in Delta Queue.
Go to Extractor Checker using Transaction Code RSA3 in ECC and give DataSource is 2LIS_03_BF.
Checking the Data using Extractor Checker (RSA3) in ECC Delta and Repeat Delta etc...
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
Go to RSA7 and select the DataSource 2LIS_03_BF and click on Display data entries. Here you can see, the number of Total is increased, after V3 job success.
Now select Delta Update and execute.
We can see 174 new records in Delta Queue. I.e. after V3 job.
Checking the Data using Extractor Checker (RSA3) in ECC Delta and Repeat Delta etc...
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
Then goto Extractor Checker (Transaction Code: RSA3) and Select Update Mode “D” (Transfer of the Delta Since the Last Request). To check the number of records in Delta Queue.
Give the Target sys Logical name (Press F4 and select.), then click on Extraction button.
We can find 174 records. I.e. the same number of records which are there in Delta Queue (RSA7).
Checking the Data using Extractor Checker (RSA3) in ECC Delta and Repeat Delta etc...
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
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