cancel
Showing results for 
Search instead for 
Did you mean: 

Regarding R/3 Extraction

Former Member
0 Kudos

Hi,

Can any one give me step by step process for "R/3 extraction using LO cockpit"

Regards

Anusha

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

First of all delete set up table using LBWG

Fill the setup table using OLI*BW where * is application component.

extract the data in extractor using RSA3.

Then you can pull the data in bw after replcating the data source.

[https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/8134] [original link is broken] [original link is broken] [original link is broken];

[https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1096] [original link is broken] [original link is broken] [original link is broken];

Hope it helps...

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi,

Well LO Cockpit embraces 3 Delta methods which are different from the previous V3 Serializer.

These are the 3 Delta methodologies:

1 - Direct Delta

2 - Queued Delta

3 - V3 Unserialised.

1 - Direct Delta - Whenever any new doc arrives or any doc changes in R/3 it goes to corrosponding application tables and simultaneously the same data passing through the Communication structures (eg MCVBAK, MCVAP) and using the Extract structure sits in Delta Queue (RSA7). From there BW takes through IP.

2 - Queued Delta - Whenever any new doc arrives or any doc changes in R/3 it goes to corrosponding application tables and simultaneously the same data passing through the Communication structures (eg MCVBAK, MCVAP) sits in Extraction queue (SMQ1,a buffer table) and from there we schedule a V3 update Job either hourly or every 30 min depending upon the business data. This V3 update Job taks data from Extraction Queue to Delta Queue (RSA7). From there BW takes through IP.

3 - V3 Unserialised - Whenever any new doc arrives or any doc changes in R/3 it goes to corrosponding application tables and through a V3 module call (which needs to be activated) the data passing through the Communication structures (eg MCVBAK, MCVAP) sits in Update Table (VBDATA,a buffer table) and from there we schedule a V3 collective run job which taks data from update table Delta Queue (RSA7). From there BW takes through IP. Here the serialization of data (the chronological order of changes in R/3) is not maintained.

Having the above background, please find below the steps for LO Cockpit extraction.

1 - Maintain extract structures - LBWE

2 - Maintain Datasouce - LBWE and replicate it in BW (Replicate Metadata)

3 - Activation of update - When you activate, data is written to the extraction structures

immediately.

4 - Job Control

5 - Update Mode (Direct, Queued or V3 Unserialized)

6 - Delete setup tables (LBWG, Setup tables are tables containing historical data. This table is only used

with LO)

7 - Fill Setup tables (OLI*BW)

8 - Do a full load and Initialization of delta.

9 - Start and maintain delta data transfer for daily loads.

Deebanshu

Former Member
0 Kudos

Hi,

1. LO comes under SAP Delivered Extraction, so Install the BC DS

2. Satisfied with content extract structure, continue else go for maintaining the extract structure.

3. Replicate the DS, and maintain the flow in BW side.

4. Data Migration Steps:

a) For Full Load:

i> Run the Statastcial Setup

ii>Run Full Request

b) For Delta Lod

i> Select the appropriate Delta Mode

ii>Extract the deltas regularly.

Hope this helps u, here i explained briefly, most of the steps are common as above. If u still need more information feel free to contact me at 9963101073

Thanks & Regards

Ramakrishna Kamurthy

Former Member
0 Kudos

Hi Anusha ,

1. Go to transaction code RSA3 and see if any data is available related to your DataSource (2LIS_12_VCITM ) . If data is there in RSA3 then go to transaction code LBWG (Delete Setup data) and delete the data by entering the application name 12 for your data source (2LIS_12_VCITM ).

2. Go to transaction SBIW --> Settings for Application Specific Datasource --> Logistics --> Managing extract structures --> Initialization --> Filling the Setup table --> Application specific setup of statistical data --> perform setup (relevant application)

3. In OLI*** (for example OLI7BW for Statistical setup for old documents : Orders) give the name of the run and execute. Now all the available records from R/3 will be loaded to setup tables.

4. Go to transaction RSA3 and check the data.

5. Go to transaction LBWE and make sure the update mode for the corresponding DataSource is serialized V3 update.

6. Go to BW system and create infopackage and under the update tab select the initialize delta process. And schedule the package. Now all the data available in the setup tables are now loaded into the data target.

7. Now for the delta records go to LBWE in R/3 and change the update mode for the corresponding DataSource to Direct/Queue delta. By doing this record will bypass SM13 and directly go to RSA7(Delta queue). Go to transaction code RSA7 there you can see green light # Once the new records are added immediately you can see the record in RSA7.

8. Go to BW system and create a new infopackage for delta loads. Double click on new infopackage. Under update tab you can see the delta update radio button.

9. Now you can go to your data target and see the delta and record. and check this link

I hope it will serve your requirements

regards

Vels