Skip to Content
author's profile photo Former Member
Former Member

LO & COPA Extraction!!

Hi Experts,

I am new to Sap .I am learning extractors now..I find it very difficult understanding from the pdf file 350.Can anyone please give me some other links or a video demonstration of doing Lo and COPA extraction.And also a simple way of understanding delta and V3 update..i am really very confused and feel sad aas i been trying to get hold of this for last 2 days.

Thanks a lot for help in advance.


Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Dec 04, 2005 at 06:15 PM


    Roberto Negro weblogs are very informative.

    follow this link to get a better understnding of LO extraction.

    rewarding points is saying a note of thanks in sdn.


    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member


      here is some notes i saved for myself as a qucik reference for LO. But plz be advised to go thro and make changes as per ur reqt.


      • T-Code: LBWE

      • First we need to check which data source suits the client’s requirements in LBWE.

      • Check whether it is in Active version/Modified version. If it is in M version go to RSA5 and select our data source and press on Transfer. Then go to RSA6 and see whether the datsource is been transferred.

      • If the datasource is already in active version then we need to check whether the datsource is already extracting data in to BW.

      • If the datasource is extracting the data then we need to check the data existence in Setup tables (use SE11 to check the setup tables data. For every extract structure one and only one setup table is generated whose technical name is Extract structure name+ setup, for eg. If extract structure name is MC11VAOHDR then set up tables name is MC11VAOHDRSETUP) and Extraction Queue (LBWQ) and Update tables(SM13) and Delta Queue (RSA7). If data exists in any of these T-codes we need to decide whether we need the data in BW or not. If we need the extract it as we do in LO-Extraction below. I f we don’t need delete the data.

      The dataflow from R/3 into BW:

      • we need to generate the extract structure by selecting the fields from the communication structure in LBWE.

      • Generate the datasource and select the selection fields, cancellation fields, hide fields that we want.

      • Replicate it into BW. Then we need to attach Info source(Transfer rules/communication structure) to the datasource. We got 3 methods to attach the infosource..

      1) Business content:: Business content automatically proposes the transfer rules and communication structure, we don’t have to do anything manually.

      2) Application proposal: Here too proposal is done but some objects will be missing which we need to assign in the transfer rules.

      3) Others: here we need to create the transfer structure, rules, comm. Strct from the scratch.

      • Modeling like infocube, Infosurce attachment,….

      • Then activate the extract structure.

      • We need to fill the setup tables for the first time loading. In filling the setup tables we can select between Full load and delta initialization loads.

      Filling Set up table:

      T Code : SBIW

      Settings for Application-Specific DataSources (PI)->Logistics >Managing Extract Structures >Initialization-->Filling in the Setup Table -->Application-Specific Setup of Statistical Data --> in that Youcan perform the Setup (Example : SD-Sales Orders - Perform Setup) and execute .. or else direct T Code : OLIBW ( means based on your application like sales order/billing/ purchase etc)• For setup tables T-Code is OLI*BW where * equals to application number like 02 fro purchasing,08 for shipment…..

      • First we need to decide whether we want delta loads to be performed in the future. If we want to do delta loads, then we need to go for Delta Initialization process or else do full load.

      • When we perform setup tables extraction, since setup tables are cluster tables, we can’t see the data in the setup tables. So we go for Extractor checker (RSA3) just to see the setup tables data (full/delta initialization).

      • Then create infopackage and select Full or Delta initialization in Update tab and schedule it.

      • Delete the setup tables data by using LBWG.

      • Now we need to do delta loads.

      • Delta load data flow differs with various delta update methods. We got 3 delta update methods as u know.

      • If we select “Queued Delta”update method then the data moves to Extraction queue(LBWQ). Then run Collective update to move the data from LBWQ into Delta Queue (RSA7). Then schedule the data using the infopackage by selecting Delta Load in the update tab.

      • If we select “Direct delta” then the delta data moves into RSA7 directly.

      • If we select “Unserialized V3” method then the data goes into “Update tables(SM13)”, then run Collective update to move the data from SM13 into RSA7. Schedule the data using infopackage.

      • If we click on Maintenance, we can generate the extract structure.

      • If we click on 2LIS_02_CGR button, then we we can generate data source

      • Inactive under Update column: we can make a extract structure as active or inactive.

      • If we click on Job control button the we can maintain the collective update parameters like, start time, and is it hourly once or dialy once ……

      • If we click on Queued delta button under Update mode then we can select among 3 delta update methods.

      • Only Full/Delta initialization data loads only moves into setup tables. Delta load data doesn’t move into setup tables.

      **RSA3 contains only setup table’s data

      • Only Delta update data moves into RSA7/LBWQ/SM13 no full/delta initialization loads data.

      The type of work process:

      DIA - Work process for executing dialog steps in user transactions

      UPD - Update process for executing update requests

      ENQ - Process for executing enqueue requests

      BTC - Process for executing batch requests

      SPO - Process for executing spool requests

      UP2 - Process for executing V2 update requests

      **all the credit goes to the person who wrote this**


  • author's profile photo Former Member
    Former Member
    Posted on Dec 05, 2005 at 02:52 AM

    Hi kavi,

    Thanks a lot for the references but the thing is i am new to this feild and trying to learn.i saw robert's weblogs but i didn't find any step by step guide.Till now with the help of pdf350 Leson:LO Customizing Cockpit.

    I created extract structure,datasource.Now,the problem i am facing is i am not able to find my datasource in E13CLIENT800.This is what i did so far:

    1.rsa1 >context menu(T90CLNT090) >Customizing for Extractors.

    2.Selected Information Structure S523.(which was available but had no LIS environment setup )

    3.result said LIS envir..not setup,,Infosource 2LIS_02_S523 not generated.

    4.I set up LIS environment and generated datasource for the information structure i created.

    Now the problem arises.It says go to rsa1 >context menu(T90CLNT090) >Datasource Overview >context menu on Apllication component MM(not MM-IO) >Replicate datasources.

    I did till right clicking on T90CLNT090 and selected datasource overview. but i didnt find any application component for MM neither i found my datasource name when i searched.

    Can anyone help me regarding this please?


    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.