Data Flow from LBWQ/SMQ1 to RSA7 in ECC and Delta Extraction in BI Applies to: SAP NetWeaver Business Warehouse (Formerly BI), Will also work on SAP BI 3.5. Business Intelligence homepage. Summary This article tells about the data flow process from ECC to BI/BW, here we are going to talk about LBWQ - Logistics Queue Overview, RSA7 - BW Delta Queue Monitor and Data Loads in BI/BW. Author: Surendra Kumar Reddy Koduru Company: ITC Infotech India Ltd. (Bangalore/INDIA) Created on: 19 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. 2009 SAP AG 1
Table of Contents Introduction... 3 Live Scenario... 3 Detailed Steps... 4 Step 1... 4 Step 2... 5 Step 3... 8 Step 4 :... 14 Step 5... 15 Step 6... 16 Step 7... 18 Conclusion:... 20 Related Content... 20 Disclaimer and Liability Notice... 21 2009 SAP AG 2
Introduction After reading this article, you will know how the data/records will Transfer from one layer to another layer and finally how it will flow into the BI/BW system using Delta Loads. 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. Live Scenario We want to know how qrfc Monitor for the outbound queue and BW Delta Queue working for Delta records. Here I m discussing about DataSources 2LIS_03_BF (and 2LIS_03_UM), we need set Update mode is Queued Delta. See the below screen. Go to LBWE and set Update Mode is Queued Delta. Note: I m assuming that, we already executed Init loads for 2LIS_03_BF DataSource successfully and we are ready to go for Delta Loads in BI/BW Server. 2009 SAP AG 3
Detailed Steps Please follow the steps for easy navigation. Step 1 Go to LBWQ in ECC and see the Queue for various Modules i.e. SD, MM, PP etc... You can find out using application number, e.g.: For inventory 03. See the below screen which is having 02, 03, 04 and 06 applications, here we are talking about MCEX03 i.e. Inventory DataSources. It is having some entries in Queue i.e. once user will post/do some transactions related to Inventory, the data will come into the Queue and we can see the information in LBWQ. 2009 SAP AG 4
Step 2 Go to RSA7 - BW Delta Queue Monitor. See the DataSource 2LIS_03_BF. There are some entries in Delta Queue. To see the entries select the DataSource and click on Display data entries Icon. 2009 SAP AG 5
Select Delta Update and execute. 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. 2009 SAP AG 6
Then come back to main screen of RSA7 and again select the DataSource and click on display, this time you select Delta Repetition and execute. You can see 408 entries in Delta Repetition. 2009 SAP AG 7
Step 3 Go to LBWE and then run V3 job. Click on Job Control. Click on Start Date. 2009 SAP AG 8
Select Immediate. After that you can see Immediate start like below. I.e. the V3 job will start immediately. 2009 SAP AG 9
Click on Save and come back. 2009 SAP AG 10
Click on Print Program. Give the below parameters and enter. 2009 SAP AG 11
Then Click on Schedule Job, to start the V3 Job. You can find the New Job is Scheduled on the status bar, so our V3 is started. 2009 SAP AG 12
To check the job click on Job Overview. See the below screen, job is completed. 2009 SAP AG 13
Step 4 : You can check in SM37 also Go to SM37 and give Job name is LIS-BW* and if you know user ID give else give * and execute. 2009 SAP AG 14
See the job status, it is finished. Step 5 Then go to LBWQ and see the Queue, you can t find MCEX03, because after executing V3 job, all records/data is moved from Outbound Queue to Delta Queue i.e. from LBWQ to RSA7. 2009 SAP AG 15
Step 6 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, i.e. from 2 to 3. i.e. before V3 job it was 2, after V3 job it is 3. Now select Delta Update and execute. 2009 SAP AG 16
You can see 99 new records in Delta Queue. I.e. after V3 job. Come back and select Delta Repetition and execute. 2009 SAP AG 17
Here you can find totally 507 records. How? Earlier we have 408 records, now 99 records after V3 job, so totally 507 records. Step 7 Now go to BI/BW System and execute DELTA Info Package for 2LIS_03_BF DataSource. You can see 99 records in PSA. See the below screen. 2009 SAP AG 18
See the following diagram, which will give the clear picture about Data Flow. 2009 SAP AG 19
Conclusion: Whenever you execute the Delta Load InfoPackage, you will get the updated/new/changed records from Delta in ECC to BI/BW System. Whenever Delta load InfoPackage is failed and you are trying to load manually it will ask Last Delta is failed and do you want to run Repeat Delta, if you say Ok/Execute, then it will fetch the complete records from Delta Repetition. Related Content Using Customer Exit Variables in BW Reports Part - 3 How to use Customer Exit Variables in BW Reports: Part - 2 Using Customer Exit Variables in BW or BI Reports Part - 1 Using Text Variables with Customer Exits in Report Headings SAP NetWeaver Business Intelligence 2009 SAP AG 20
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. 2009 SAP AG 21