About setup tables

hi experts
happt new year to u all in advance.
i want o know that weither their wil set up tables in fi/sl & copa extraction .
and for what this set up tables meant for.
plz send answers to my mail id
kalyan11069@gmail
with regerds,
lakshmi raj.

there will be no setup tables for FI/SL and COPA extractions..
Go through the link:
http://help.sap.com/saphelp_nw04/helpdata/en/f3/3a69377f2b8032e10000009b38f8cf/content.htm
Regards
Manga
Assign points if it helps

Similar Messages

  • About setup tables in R/3 system

    Hello BI Gurus,
    During Production Support, if a requirement arises where new fields have to be included in a Datasource that is covered by the LO Cockpit, then in such a case do we need to necessarily delete the setup tables and reload.
    regards,
    gaurav

    Hi Guarav,
    As you need to clear setup tables, before transporting these changes to production system.
    After import changes, need to setup to load historic data into BW.
    Check: [How to retain deltas when you change LO extractor in Production system|http://sapbwneelam.blogspot.com/2007/09/how-to-retain-deltas-when-you-change-lo.html]
    Hope it Helps
    Srini

  • Setup table in LO Cockpit

    hi i have a very silly doubt,
    which is a correct statement about setup tables:
    1>setup tables are cluster tables, we can't see the data in the setup tables
    2>data in setup table can be checked using SE11
    can anyone please explain me significance of both the statements
    Thank you,
    sam

    Hi dear,
    yes, it's true, you can see data in setup tables, but you have to read as "you can see meaningful data in cluster tables".
    In other words, data can be checked in SE16 (not in SE11 that contains only fields definition) as number of entries, but nothing more; in other words you can check if there is something or the table is emprty, but you cannot check directly if there is something you need (for this purpose you have to use RSA3 extraction simulation).
    So, no contradiction in your two sentences !
    Hope now is clearer...
    Bye,
    Roberto

  • Setup tables in Lo Cockpit

    hi everybody,
      i need information about SETUP TABLES in LO COCKPIT(i had some information like(temporary location where we can do INIT/FULL load to cube))
    i need more information other than these

    Hi,
    U can find more information on SDn by giving a search word like ' Setup tables'
    Thanks,
    Message was edited by:
            SDN BW

  • Emptying Delta queues before filling a setup table

    How do I empty the delta queues?  I want to carry out this task just prior to filling a setup table.  Thanks

    Hi Sekhar,
    Thanks for that, I was on a flight anyway, just got home.  I was thinking on the plane about the previous point that you mentioned wrt the collection run.  I think I understand the point that you were trying to make is this a correct understanding
    1) System is locked
    2) Do a collection run - the reason for this is that there may be postings which have not been placed on the RSA7 queue since the last collection run
    3) Do Delta load twice
    Does that make sense.  The points that you have raised otherwise, I will post a question otherwise on the steps I will look to take just to get confirmation I am not missing anything

  • While filling setup table

    hi,
    whilw iam filling setup table iam getting the error
       <b>No extraction structure active or no BW</b>
    in rsa5 and rsa6 i did the procedure
    inlbwe that ds is active
    i deleted the set uptable
    after i fill the set up table
    iam getting this error
    iam experting a solutions from the experts
    regards
    kiran
    plz response to my mail id [email protected]

    Hi Kiran,
    It is not possible to modify the extract structure if
    1. Set up tables have been populated during preparation and contains data
    2. outstanding items in the extraction que (LBWQ) pending updates
    3. Unfinished delta load or items in delta que RSA7.
    What update method are you using ? Serialised V3 or the latest methods like
    Queued delta ? what version of PI are u using. As i assume u also have latest PI or PI > 2001.2.
    When u run SM13, make sure you select * or client and * for user. Also, the
    date selection - make sure u enter date like 01011990 to include any
    document that was posted. You will find some outstanding update records.If u
    find any, try deleting them or else force the update using the collective
    run.
    If you have modified and you get an error, you may have to set back the
    changes and reactivate the extract structure first and then do a collective
    run ( search for a program with R*02)- this program forces any outstanding
    updates for the modules under '02'. This program probably is the same in the
    'job control' but am not sure. It is safe to execute this report which will
    clear any o/s updates.
    Carry out the changes using the following steps.
    0. Lock transactions to be sure no postings are going to take place while
    you are about to make changes.
    1.There is a report you can run to check whethere changes to the extract
    structure is possbile without errors. Report name is RMCSBWCC. Enter all the
    comm tables related to purchasing ilike header, item and SCL while
    performing this check. You should get a green light for permitting changes
    to extract structure.Deactivating the extract structure has no effect so it
    can remain active.
    2. Delete the set up table for 02.
    3. Performa collective run to be sure all qued data is taken into delta que
    (even if u have never initialised).
    4. Delete if you find any in RSA7 for the datasources in question. you will
    lose the data but can be reinitialised later.
    5. Run RMCSBWCC again to check if it is ok for bring about changes to the
    extract structure.
    6. If OK, make the changes necessary and save, generate datasource,
    replicate and perform set up table before init run from BW. make sure no
    collective run is started before completion of init load if you are using
    serialised update.
    hope this helps
    award points if useful.
    regards
    Archna.

  • Missing PO in 2lis_02_itm init extraction / setup tables

    Hello Gurus,
    could anyone please help me out with this toppic:
    I want to extract Purchase Orders to BW via DS 2lis_02_itm. Source System is R/3 4.6c. Filling up the setup tables is working. My problem is, that there are several Purchase Orders which are not filled in the setup tables (so no extraction to bw)! I have checked these PO and for me they seem fine. I can´t find any reason why they aren´t extracted. Of course i am running all programms whithout any restrictions. I have debugged the programm rmceneua with one specific po which is not extracted but can not find a reason why it is not written to table MC02M_SETUP.
    Did i miss some customizing settings? Are there some kind of PO which are not extracted because of there PO Type (ZCO/ZB) do they eventually have a wrong status?
    I can not find any information about the functionality of programm rmceneua. Maybe you can help me out of this?
    Thanks a lot
    JANOS

    Did you check whether the process key is maintained properly?

  • How to stop document posting when filling setup tables for logistic app.

    Hello Boys
    I've read several threads and weblogs about data extraction from logistic applications i.e the ones which uses the infosources like 2lis_13_vditm, 2lis_02, 2lis_03, etc, etc,and now almost every thing is clear to me but one thing: how do i actually "close the system" while the process of filling setup tables i.e MC03BF0SETUP, MC03BX0SETUP, MC13VD0ITMSETUP,  are running?
    So I have some questions
    1) which is the procedure to prevent users from posting documents for an specific logistic applications (02,03, etc.) in a source system
    3) For example when using TC OLI9BW for statistical setup from billing documents (app no. 13), there is a check box "Block all billing documents?". Is this option for such pourpose?
    4) Every logistic applications has a different procedure??
    thanks (with points of course) for any help
    rgds
    A. Garduñ

    Hi Azael:
    Q1: usually the BW team will inform basis/secuity about the deletion and performing of setup tables. they will fix a time after the normal hours where in all users are locked out from the system. in a sense, R/3 will be down for that time.
    2. the check box which says, "block documents" is meant to block posting. for eg: you are doing setup tables late in the evening, and you assume that no user is assessing the system, but if there is a user(just by chance) who is doing some posting and when he try to save it, the system will not allow him to do save as you cheked this option.(normally we donot use this)
    3. some LO may have different procedures, for eg IM. but most of them have the same functionality.
    hope it helps.
    assign points if helpful
    kalyan

  • SETUP tables steps required

    <Moderator Message: Please search before posting. You can find a lot of information related to this issue searching the forums, the blogs and of course the online help.>
    Hi friends,
    I want do purchase extraction using LO cockpit extraction before doing this i want to know about R/3 steps & setting if any in R/3 system.
    I know about LO extraction steps apart from that if we have any steps in R/3 setting kindly forward to me.
    thanks
    Siri
    Edited by: Siegfried Szameitat on Jan 26, 2009 12:31 PM

    Hi Siri........
    U want to extract Logistic data........
    The following section describes the steps that are necessary to configure a data
    flow for logistics data extraction.
    1. Transfer the logistics DataSource for transaction data from Business Content
    With the transfer of the DataSource, the associated extraction structure is
    also delivered, but the extraction structure is based on LIS communication
    structures. Furthermore, based on the extraction structure for the DataSource,
    a restructuring table that is used for the initialization and full update to BI
    is generated.
    Naming convention:
    DataSource 2LIS_<Application>_<Event><Suffix>; where <Event> is
    optional
    Examples:
    2LIS_11_VAITM: 11 = SD Sales VA = sales order, delivery schedule ITM
    (u2192 ITEM) = document position
    2LIS_02_HDR: 02 = MM purchasing HDR (u2192 HEADER ) = Document
    header
    Extraction structure MC<Application><Event/group of
    events>0<Suffix>; where MC is derived from the associated communication
    structures and <Suffix> is optional
    Examples:
    MC11VA0ITM: Extraction structure for the DataSource 2LIS_11_VAITM
    MC02M_0HDR: Extraction structure for the DataSource 2LIS_02_HDR,
    where M_ indicates the group for the events MA (order), MD (delivery
    schedule), ME (contact) and MF (request).
    Restructuring table (= setup table) <Extraction structure>SETUP
    Example:
    Extraction structure: MC11VA0IT u21D2 Restructuring table:
    MC11VA0ITSETUP
    2. Maintain extraction structure (transaction LBWE)
    This means that fields can be added to the extraction structure that is
    delivered with the DataSource without modifying anything. On the one
    hand, fields from the LIS communication structures that are assigned to the
    extraction structure can be used, that means standard fields that SAP has
    not selected, and on the other hand, customer fields that were attached to
    the LIS communication structures with the append technique can be used.
    After the extraction structure is created, it is generated automatically and the
    associated restructuring table is adapted.
    3. Maintain/generate DataSource
    In the DataSource maintenance, you can assign the properties Selection,
    Hide, Inversion (= Cancellation) and Field Only Known in Customer Exit to
    the fields of the extraction structure. After enhancing the extraction structure,
    the DataSource always has to be generated again!
    4. Replicate and activate DataSource in SAP BI (=metadata upload)
    5. Maintain Data Target (Data Store Object, InfoCube)
    6. Maintain Transformations between DataSource and Data Target
    7. Create a Data Transfer Process
    the Data Transfer Process will be used later to update the data from the PSA
    table into the Data Target.
    8. Set extraction structure for updating to active (transaction LBWE)
    In this way, data can be written to the restructuring table or the delta queue
    from then on using the extraction structure (see following steps).
    9. Filling the restructuring table/restructure (OLI*BW)
    During this process, no documents should be created or changed in the
    system! In some applications, it is possible to fill the restructuring table
    beforehand in simulation mode. These results are listed in a log (transaction
    LBWF). Before filling the restructuring table, you must ensure that the
    content of the tables is deleted (transaction LBWG), preventing the table
    from being filled multiple times. Once the restructuring tables are filled,
    document editing can resume as long as Unserialized V3 Update or Queued
    Delta is selected in the next step. Be absolutely sure that no V3 collection
    run is started until the next successful posting of an InfoPackage for delta
    initialization (see step 11).
    10. Select update method
    • Unserialized V3 update
    • Queued delta
    • Direct delta
    11. Create an InfoPackage for the DataSource and schedule the Delta
    Initialization in the Scheduler
    This updates the BI-relevant data from the restructuring table to the
    PSA table. Since the restructuring table is no longer needed after delta
    initialization, the content can be deleted (transaction LBWG).
    Use the Data Transfer Process created in step 7 to update the data from
    the PSA table into the Data Targets. After successful delta initialization,
    document editing can resume, as long as the direct delta update method
    was selected in step 13. This means that BI-relevant delta data is written
    directly to the delta queue.
    Note:
    If the DataSource supports early-delta initialization, the delta data can
    be written to the delta queue during delta initialization. This feature is
    controlled with an indicator in the Scheduler.
    12. Start V3 collection run (transaction LBWE)
    This step is only necessary when the update method unserialized V3 Update
    or Queued Delta was selected in step 10. By starting a corresponding job for
    an application, the BI-relevant delta data is read from the update tables or
    extraction queue and written to the delta queue.
    13. Create an InfoPackage for the DataSource in BI and schedule the Delta
    Update in the Scheduler
    The BI-relevant delta data from the delta queue for the DataSource is updated
    to the PSA table. Use the Data Transfer Process created in step 7 to update
    the data from the PSA table into the Data Targets.
    Hope this helps.......
    Regards,
    Debjani......

  • What does a BI Developer need to know about SAP tables and why?

    Hi,
    i.
    As a BI Developer, to what extent do you need to know about SAP tables?
    e.g. if you work mainly in the functional areas LO and FI
    ii.
    For example, I know that in Finance, GL relates to the tables BSEG and BKPF.
    And if it is important to know about them, then which other tables need to be known and for what reasons?
    e.g. do I need to know all these tables: http://www.erpgenie.com/sap/abap/tables_fi.htm
    iii.
    I thought as a BI Developer, knowing that a particular datasource, e.g. 0FI_GL_4 contains line items is enough and you replicate it to BW and work with it. Why is there the need to know the tables from which this datasource gets is data?
    iv. What is the main difference between the FI datasources and the LO datasource?
    Thanks.

    Hi,
    i.  As a BI Developer, to what extent do you need to know about SAP tables?
    e.g. if you work mainly in the functional areas LO and FI
    Not required, but today business demands so you required this Knowelgde.
    ii.
    For example, I know that in Finance, GL relates to the tables BSEG and BKPF.
    And if it is important to know about them, then which other tables need to be known and for what reasons?
    e.g. do I need to know all these tables: http://www.erpgenie.com/sap/abap/tables_fi.htm
    We can't say yes or No, so based on your requirement you need to sit with Functional COnsultanst and the understand the Business Requirements and develop the OBjetcs.
    iii.
    I thought as a BI Developer, knowing that a particular datasource, e.g. 0FI_GL_4 contains line items is enough and you replicate it to BW and work with it. Why is there the need to know the tables from which this datasource gets is data?
    If you want to know the data flow and reconsilization then you need to know it else not required
    iv. What is the main difference between the FI datasources and the LO datasource?
    Yes, one main difference is There is no setup table concept for FI DataSource*
    Note: If you want to become a good BW consulatnt you must know about Tables for normal BW consultant it is not required.
    Thanks
    Reddy

  • How downtime can be reduced for setup table update.

    Hi;
    Can anyone tell me various ways to reduced system downtime for setup table updates.
    thanks
    Warm Regards
    Sharebw

    Hi,
    You will need to fill the set up tables in 'no postings period'. In other words when no trasnactions are posted for that area in R/3 otherwise those records will not come to BW. Discuss this with end user and decide. Weekends are a general choice for this activity.
    try Early Delta Initialization
    With early delta initialization, you have the option of writing the data into the delta queue or into the delta tables for the application during the initialization request in the source system. This means that you are able to execute the initialization of the delta process (the init request), without having to stop the posting of data in the source system. The option of executing an early delta initialization is only available if the DataSource extractor called in the source system with this data request supports this.
    Extractors that support early delta initialization are delivered with Plug-Ins as of Plug-In (-A) 2002.1.
    You cannot run an initialization simulation together with an early delta initialization.
    hope this link may make you clear about early delta init
    http://help.sap.com/saphelp_nw04s/helpdata/en/80/1a65dce07211d2acb80000e829fbfe/frameset.htm
    thanks,
    JituK

  • Ways to reduce downtime for filling up setup table

    Hi Experts,
    Can anyone tell me the step by step process so that i can reduce downtime for filling up setup tables?
    I know that setup tables can be filled by considering sales document numbers....but the further steps are not clear with me...........specially with data loadin till PSA and then to ODS/Cube
    So plz throw some light on this.......
    Regards,
    Vaishnavi.

    Hi,
    You will need to fill the set up tables in 'no postings period'. In other words when no trasnactions are posted for that area in R/3 otherwise those records will not come to BW. Discuss this with end user and decide. Weekends are a general choice for this activity.
    You can run them after business hours so that there wont be any transactions, or in the night times or you can do it on week ends so that there is no need to take down time.
    Fill the setup tables with already closed values and then fill up again with open values.This will reduce the down time.
    Initialize  closed periods first in which users wont enter data ( for example in 2007 or 2006), this initializations can be done while users are working. Then the initialize last period at night/weekends.holidays etc.
    If you know documents that are in closed periods, and you are sure that these documents can no longer be changed, you can only fill the SetUp tables for these documents or only for these periods, by continuing to post in open periods. You then initialize only for these intervals, delete the setup table, and only then do you fill the setup table with the rest of the documents  this procedure can drastically reduce the downtimes of your system.
    However, there is a risk that user exits (and in LIS, formulas and conditions) can be used to retrieve documents that are in periods that are already "closed periods".
    One more thing what you need to bear in mind is, to check if there are any Scheduled jobs which are updating the transaction tables, which would definitely cause Data Reconciliation Issues.
    Try Early Delta Initialization
    With early delta initialization, you have the option of writing the data into the delta queue or into the delta tables for the application during the initialization request in the source system. This means that you are able to execute the initialization of the delta process (the init request), without having to stop the posting of data in the source system. The option of executing an early delta initialization is only available if the DataSource extractor called in the source system with this data request supports this.
    Extractors that support early delta initialization are delivered with Plug-Ins as of Plug-In (-A) 2002.1.
    You cannot run an initialization simulation together with an early delta initialization.
    Hope this link may make you clear about Early Delta Initialization
    http://help.sap.com/saphelp_nw04s/helpdata/en/80/1a65dce07211d2acb80000e829fbfe/frameset.htm
    http://www.allinterview.com/showanswers/2907.html
    http://sap.ittoolbox.com/groups/technical-functional/sap-bw/early-delta-initialization-459379
    http://books.google.co.in/books?id=qYtz7kEHegEC&pg=PA293&lpg=PA293&dq=early+delta&source=web&ots=AM1PtX6wcZ&sig=xKOF85Gb8UtszY44zt06K6R0n3M&hl=en#PPA290,M1
    http://www.blackwellpublishing.com/journal.asp?ref=1069-6563&site=1
    EARLY DELTA
    Early delta Initialization
    How To… Minimize Downtime For Delta Initialization
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5d51aa90-0201-0010-749e-d6b993c7a0d6
    How To Minimize Effects of Planned Downtime (NW7.0)
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/901c5703-f197-2910-e290-a2851d1bf3bb
    Note 753654 - How can downtime be reduced for setup table update
    602260 - Procedure for reconstructing data for BW 
    437672 - LBWE: Performance for setup of extract structures 
    436393 - Performance improvement for filling the setup tables 
    Note 739863
    /thread/756626 [original link is broken]
    Re: How to Setup and INIT from 2LIS_13_VDITM with millions of records
    How downtime can be reduced for setup table update.
    Fill setup tables without locking users
    Initialization Setup Tables.
    Hope this helps.
    Thanks,
    JituK

  • Data loading for Logistics Data Extraction 2LIS_06_INV through setup tables

    Hi Guyz,
    I have LO Datasource 2LIS_06_INV which I am using for extracting Invoice Verification Data.
    I had intialized and loaded invoice data in BI system and was using chais to load daily.
    Now I want to load data again from scratch from source system.
    As of now I know we need to delete and fill up setup tables in source system keeping the users locked so that no new records are created that particular moment.
    But what about the delta queue and extraction queues.
    Do I need to do something over there because as I understand there will be records in both of them so before filling the setup tables I need to delete both the queues and then fill the setup tables so that duplicate records should be avoided.
    Please let me know what exactly should I do in detail.
    Appreciated in advance.
    Regards,
    raps.

    hi,
    this entirely depends upon the DS, if the DS delta type supports overwrite mode then you need not lock the users, you can start the setup job without deleting the delta queues as well coz even if the record is extracted twice the values won't mess up as the flow will be in overwrite mode. If delta type of DS is Additive in table ROOSOURCE then you need to lock down the users or run the job over a weekend when no users are logged in.
    regard,
    Arvind,

  • Setup table - Archiving run option

    Hi all,
            I want to check my inventory data have archiving run while filling setup table. Also archiving run data in which table i can find. If required R3 data in archiving table, we no need to think about backup data in BW.
    thanks

    Hey Raj,
    Your question is not clear?
    If you are talking about archived data
    - Archived data will be not be present in the source tables, you need to perform special mechanism to retrieve the archived data.
    - if you want to extract the data using the data source to BW you will not be able to extract the archived data.
      For this you need to write a exit in CMOD for that particular data source to additionally extract archived data where for example BSID-XARCH =x or BSEG-XARCH=X etc.
    or
    one more way is to extract the archived data by creating a generic data source on top of the archived tables for only those records which are archived (XARCH = X).
    Just perform a full update as the archived documents does not have updated records. you can go for creation of generic data source it would be a better option to extract the archived data instead of disturbing the existing data flow.
    Regards
    KP
    Edited by: prashanthk on Nov 17, 2011 11:58 AM

  • Delete setup tables

    Hi Friends
    We have data sources 2LIS_02_ITM, 2LIS_02_CGR, 2LIS_02_SCR and 2LIS_02_SGR activated and up and running delta properly.
    Due to some loads failed, we are doing re-init the loads.We are about to delete setup tables for purchase (02) component and refill the setup tables.
    If I delete the setup tables for 2LIS_02_ITM datasource, Is it going to delete setup tables for all data sources?
    How can i delete and re-fill the setup tables for only 2LIS_02_ITM data source?
    Regards,
    Chama.

    Don't worry, it won't affect any delta.
    1/ Setup tables affect only Full/Repair Full/ Init Delta loads
    2/ Delta queues affect only Delta Loads.
    These two processes are separate from each other. The only thing you should worry about is while your setup tables are being filled, no user o remote process creates or modifies any document referring to to your R/3 application, in your case being 02. Because if they do - you'll lose these new or modified docs.
    Cheers.

Maybe you are looking for