Hi experts why we use set up tables in LO cockpit

please forward to my personal mail id
[email protected]

The logistic cockpit extractors are different from the others. They use setup tables and delta queues for initial loading and delta loading respectively. The delta queues act as a <i>buffer area</i> which is detatched from the business logic of the applications' operations (ref. <a href="/people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146 COCKPIT DELTA MECHANISM - Episode one: V3 Update, the ‘serializer’</a>).
The other extractors read the application tables directly, both during the initial loading and during the delta loading. This means that whenever BW requests the data, a function module extracts the data from the R/3 tables.
I wonder why there is such a technological difference between the 2 classes of extractors. Could someone please shed some light on this? What considerations may have led to this kind of architectural choice? Is the number of transactions occurring in the applications covered by the LO extractors significantly greater than that occuring in other applications (e.g. FI, CO, etc.)? In this case, the ERP system could  certainly benefit from a delta management buffer area.
Thanks&Regards, Davide

Similar Messages

  • Why set up table not used in applications like FI, HR etc

    Hi,
    We all know that we use set up tables for LO Cockpit applications.
    But we dont have for non LO applications like HR , FI...why such a difference is made by SAP...
    One of the fellow suggested that for FI, HR etc, there is huge posting of data and so we dont want to store such a duplicate data
    is this the case?
    or there is some other reason...
    please suggest the same
    Thanking You,
    Tarun Brijwani.

    Hi,
    this question has already been asked a few times. Please search the forums for the answer.
    regards
    Siggi

  • Why we use PCLn tables  only in HR ?

    Hii
        Kindly explain me why we use special PCLn tables for storing data in data clusters ,This kind of storing data is not used in other modules such as SD MM etc why only in HR module ?
             That too in cluster tables we store specific data like Payroll data why ?
    Please help.
    Thanks
    Ajitabh Pradhan

    Hi,
    maybe ask directly SAP
    Cluster table is not really usefull, I prefere transparent table for development. But, you have cluster table like STXL, STXBITMAPS, ... for special requierement.
    Why do you want to use cluster tables  ?
    Rgd
    Frédéric

  • Regarding set up table filling in R3 prod system

    Hi Expert,
    When I fill set-up table for Billing LIS data-source . It is taking lot of time, All though  Data-volume is very less (Around 1 Lakh) .
    It is taken almost 50000 sec and still running .
    Please help.
    Thanks
    Devesh Varshney

    Hi,
    Prod system will be busy during your set up tables filling time.
    Try to check ECC system load burden and fill set up tables data when system have required free application servers(SM50/51). Even try to fill set up tables in background.
    if possible, use selections and fill set up tables.
    Thanks.

  • Set up table?

    Hi,
    Can anybody explain me the concept of setup tables in LO extraction?
    I want each and every word abt setup tables.
    I will assign points.
    Thanks in advance,
    Ravi Alakuntla.

    hi ravi,
    The reason of using Set up table is that the SAP doesn't permit the extraction structure tables to access the database tables directly like.Rather than getting the data directly from the source tables (EKPO, MARC, VBRP, VBRK ), the data is stored in Set up tables, which you can use for update to BW.
    After that all transaction data is posted
    to the delta queues in the source system. After a sucessful full upload you can delete the setup tables.
    the logistics extractors from Logistic Cockpit (LBWE) was designed to replace the LIS info structures (Snnn). When you create, change or delete documents in the applications, the resulting data is staged online in LIS communication structures. In addition, data is transferred from the LIS communication structure, using extract structures, into a central delta management area (using different delta method). So, delta management acts as a buffer for data that can be requested from the BW via an infopackage with the update mode "delta upload".
    When you use infopackages with the update mode "delta initialization" (even "full"), your scope is to used to transfer existing or archived documents. Only afetr this step (initialization) any modification will be available as delta, following the schema explained before. In OLTP (R/3) the infopackages retrieve data from the setup tables (and no postings have to be in the meanwhile, otherwise there would be some data loss!), which are assigned to the extract structures.
    You fill these tables using special setup transactions in OLTP (OLI*BW).
    For each extract structure, one setup table with the name of the extract structure and ‘SETUP’ as a suffix, exists.
    Example: Extract structure MC02M_01TM, setup table MC02M_01TMSETUP.
    Since you are using cluster tables, it does not make sense to display the entries with transaction SE16.
    You cannot determine the number of entries from the number of data records.
    However, you can display data using transaction RSA3, since this transaction uses data from the setup tables.
    Hope it helps!
    Bye,
    partha

  • Why Set up table in LO Extraction ?

    Hi All,
    In LO Extraction we have filling up of set up tables for doing Init and then delta falls into update table etc then using V3 collective run push it to Delta Queue. Then we extract into BW. Why in LO alone this is the methodology for extraction and why not in other extractions like COPA or HR or FISL or anything ? What is the reason for these unique steps in LO extraction alone ?
    Kindly let me know the answer.
    Best Regards,
    Fanie Hudson.

    This question has already been posted several times and lot of documents are available.
    Have a look at these discussions:
    set up tables
    Set up tables
    Set up tables
    view of set up tables data in se11??????????
    Set Up tables..
    lo: delete set up tables: DOUBT
    Blogs of Roberto will be useful as well:
    /people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
    LOGISTIC COCKPIT DELTA MECHANISM - Episode two: V3 Update, when some problems can occur...
    LOGISTIC COCKPIT DELTA MECHANISM - Episode three: the new update methods
    LOGISTIC COCKPIT - WHEN YOU NEED MORE - First option: enhance it !
    LOGISTIC COCKPIT: a new deal overshadowed by the old-fashioned LIS ?
    award points if useful

  • What is the use of delet set up table in lo **** pit, exactly what happenda

    what is the use of delete set up table in lo **** pit, exactly what happened if we do the process, is all tables will lose their data which r available in functional module,
    Why i'm asking this, because we assign functional module in LBWG.
    plz .......
    thanx
    vidhu

    HI Vidhu,
    Initially we don't delete the setup tables but when we do change in extract structure we go for it. We r changing the extract structure right, that means there are some newly added fields in that which r not before. So to get the required data (i.e.; the data which is required is taken and to avoid redundancy) we delete n then fill the setup tables.
    To refresh the statistical data. The extraction set up reads the dataset that you want to process such as, customers orders with the tables like VBAK, VBAP) & fills the relevant communication structure with the data. The data is stored in cluster tables from where it is read when the initialization is run. It is important that during initialization phase, no one generates or modifies application data, at least until the tables can be set up.

  • Why we use Cluster Tables in SAP Hr

    hai friends, i am new to  ABAP-HR and SAP HR, Actually i am core abaper ( working on SD, MM and Fi Modules ) , can any one explain me why and what is the use of Cluster tables in SAP HR, why we use in SAP HR function Module ?
    Thnx in advance
    Vijaya

    Hi Vijaya,
    This may help for ur question..
    Why cluster table:
    Cluster tables combine the data from several tables with identical (or almost identical) keys into one physical record on the database.
    Data is written to a database in compressed form.
    Retrieval of data is very fast if the primary key is known.
    Cluster tables are defined in the data dictionary as transparent tables.
    External programs can NOT interpret the data in a cluster table.
    Special language elements EXPORT TO DATABASE, IMPORT TO DATABASE and DELETE  FROM DATABASE are used to process data in the cluster tables.
    PCL1 - Database for HR work area; (long text, etc)
    PCL2 - Accounting Results (time, travel expense and payroll); (payroll results)
    PCL3 - Applicant tracking data;
    PCL4 - Documents, Payroll year-end Tax data (change logs, etc)

  • How to set the tables parameter to a BAPI using adaptive RFC model

    Hi,
    I have a BAPI ZBAPI that has a tables parameter ZPernr of type ZTable with two elements pernr and name.
    I used adaptive RFC model and created model classes for the BAPI.
    My question how do i set list of pernr and name to the tables parameter in the webdynpro for java.
    I have the following methods available
    ZBAPI input = new ZBAPI();
    1.ZTable table = new ZTable();
    table.setPernr(pernr);
    table.setname(name);
    input.addZPernr(table);
    how do i set the table parameter for multiple pernr and name
    2.
    add all the pernr and name to list and set that list to input in the following way
    input.setZPernr(list) and list of typecom.sap.aii.proxy.framework.core. AbstractList
    out of two methods mentioned which one is correct.
    Please let me know the solution
    Thanks
    Bala Duvvuri

    Hi Bala,
                In your code:
    List pernrList = new ArrayList();
    pernrList  should be declared as the  type of class HROBJECT   ( The structure name in the model  e.g. the node PERFWARN type is Zhrecmfm_002_Perfrat_Warning_Input )
    Try this:
    HROBJECT  pernrList = new HROBJECT();
    pernrList.setPernr(pernr);
    input.setPernr_List(pernrList);
    // call BAPI execute method
    If you want to pass list of pernrs, you can pass in alternate way
    IPrivate<viewname>.I<nodeame>Node prNode = wdContext.node<node>();
    IPrivate<viewname>.I<nodeame>Element prEle;
    for (int i = 0; i < table.size(); i++) {
    HROBJECT  pernrList = new HROBJECT();
    pernrList.setPernr(pernr); // Set the pernr from current record
    prEle = prNode.create<nodeame>Element(pernrList);
    prNode.addElement(prEle);     
    // call BAPI execute method
    Once I execute the BAPI how do i iterate thru second table parameter PERNR_PERFRAT to get pernr and performance rating text
    Say your node name is  PERNR_PERFRAT
    for (int i = 0; i < wdContext.nodePERNR_PERFRAT().size(); i++) {
    wdContext.nodePERNR_PERFRAT().getPERNR_PERFRATElementAt(i).getPernr();
    wdContext.nodePERNR_PERFRAT().getPERNR_PERFRATElementAt(i).getPerfrat();
    Regards,
    Siva

  • Why we use Tables statement in case of using SELECT-OPTIONS:

    hi all,
    Why we use Tables statement in case of using the following coding in an ABAP program ...
    tables: vbak.
    SELECT-OPTIONS: s1 for vbak-vbeln.
    here if we dont provide the tables statement why it does not work ????
    pls answwer ....???

    Hi
    This statement is not allowed in classes and declares a data object table_wa as a table work area whose data type is adopted from the identically named structured data type table_wa from the ABAP Dictionary. table_wa must be defined as a flat structure in the ABAP Dictionary. You can specify database tables or Views for table_wa.
    Work table areas declared with TABLES are interface work areas and should only be declared in the global declaration section of a program for the following purpose:
    reward if usefull
    The statement TABLES is required for exchanging data between screen fields that were defined in a program screen when transferring from the ABAP Dictionary and the ABAP program. For the screen event PBO, the content of the table work area is transferred to identically named screen fields; for PAI, the system adopts the data from identically named screen fields.
    In executable programs, flat table work areas can be used for adopting data that were provided for the event GET table_wa from a linked logical database. TABLES is synonymous with the statement NODES for this purpose.
    Work table areas declared with TABLES behave like the data declared with the addition COMMON PART, meaning the data are used by the programs of a program group.
    Table work areas declared with TABLES can be declared in subroutines and
    function modules. However, this is not recommended. A table work area declared in a procedure is not local but belongs to the context of a framework program. The table work area can be viewed starting from the declaration in the framework program and lives as long as the framework program. In contrast to normal program-global data, the content of the table work areas declared in subroutines and function modules is stored temporarily when these subroutines and function modules are called. Value assignments that were made during runtime of the procedure are preserved until the procedure is completed. When exiting the procedure, the table work areas are filled with the contents that they contained when the procedure was called. Table work areas declared in procedures behave like global data to which the statement LOCAL is applied in the procedure.
    The form TABLES * is obsolete.

  • Getting Compilation error when used SET or MULTISET operator on nested tabl

    Dear All,
    I am getting Compilation error when used SET or MULTISET operator on nested tables inside a procedure.
    This is working fine in other DB installations of 10g but does not work in another 10g DB.
    it says "wrong number of parameter or datatype used in SET"
    Can any one suggest what went wrong here?
    Thanks in advance.

    Can any one suggest what went wrong here?Only if you would post the query and Oracle versions on both databases.
    Besides, this forum deals with issues in Oracle product installation. So post this query in SQL PL/SQL forum for better response.

  • Compilation error when used SET or MULTISET operator on nested tables

    Dear All,
    I am getting Compilation error when used SET or MULTISET operator on nested tables inside a procedure.
    This is working fine in other DB installations of 10g but does not work in another 10g DB.
    it says "wrong number of parameter or datatype used in SET"
    Can any one suggest what went wrong here?
    Thanks in advance.

    Hi,
    Thanks for ur reply...
    Since MULTISET and SET operators are the new additions in base 10g release for manipulation of nested tables data, I am surprised that same is working in similar 5 DBs installations with 10.2.0.1.0 version, but does not work in the sixth.
    SET and MULTISET operators are used inside the PL/SQL procedure which is getting compiled in the above mentioned 5 DBs but not in sixth DB.
    it gives
    On line: 3112
    PLS-00306: wrong number or types of arguments in call to 'SET'
    Hope this clarifies the issue...

  • Why we use INTO CORRESPONDING FIELDS OF TABLE

    why we use INTO CORRESPONDING FIELDS OF TABLE

    INTO CORRESPONDING FIELDS OF TABLE  is transferring the value from select clause to itab where the field names are same.
    suppose you have
    data : begin of itab occurs 0,
             matnr like mara-matnr,
             menge like mseg-menge,
            lgort   like mard-lgort,
           end of itab.
    select matnr lgort into table from mard where....
    it may give an error because you are not filling menge here or it may fetch the value in matnr and menge field.
    but if you use INTO CORRESPONDING FIELDS OF TABLE then it will fetch the data to matnr and lgort field only.
    INTO CORRESPONDING FIELDS OF TABLE  is only matching by name not by datatype be careful.
    regards
    shiba dutta

  • Why we use crmd_link table ........?

    Hi,
    I am new bee in CRM. I am doing my first program in crm . Can any one explain me why we use CRMD_LINK table.
    Why we pass guid in guid_hi and get guid_set ? what is diffrent between them ?
    Help will be rewarded ...
    Regards
    Gurprit Bhatia

    A CRM transaction (e.g. contract) data info is not contained in a single table. We need to use different tables for the same.
    guid_hi and guid_set are used for different categories of data like partner info, billing info, etc.
    Some numeric ids are there for guid_hi and guid_set
    Using help, u can find out which id stands for which category of data.

  • Why to give  New Run Name every time for  filling up the Set UP Tables

    Hi,
    While filling up the SETUP Tables we have to  give RUN Name.
    Every time while filling the SETUP Tables we have to give New Run Name.Is there any special reason for this
    every time we have to give NEW Run Name while filling up  the SET UP Tables?
    Thanks and Regards,
    Asim
    Edited by: asim khan on Apr 19, 2011 4:09 PM
    Edited by: asim khan on Apr 19, 2011 4:11 PM

    Hi,
    Thats true but my question is why to give NEW Run name every time while filling up the SET UP Tables.
    Why it wont take  old run name . Whats the logic behind this.
    Thanks for the Reply.
    Asim

Maybe you are looking for