Populate setup table impact on delta loading

Hi  Expert,
     For a ECC standard data source supporting delta mode; Taking 2lis_03_bf for example, now DSO A is loading data from 2lis_03_bf; but there are new requirement need to load the history data from this data source. So i want to populate the setup table of 2lis_03_bf and then make a full upload to another DSO B. If i do this, any impact on delta loading to DSO A ?
    In my opinion, populating the setup table is not impact on the delta loading data to DSO A ! Because delta loading is related to Delta Queue and full upload is related to setup table.
Thanks,
Dragon

Hi Draco,
Are you in 3.x or 7.0 version?
This scenario needs to be addressed diffferently based on the version.
If its 3.x version, then you need to create a full repair request (Overwrite mode in DSO A) and load the data into two targets
or
Create a full update infopack, remove tick from data target tab for DSO A and load to DSO B.
If 7.x version.
Create a full upload info pack and extract the data into PSA and using the new DTP from PSA to DSO B.
Create another DTP on PSA to DSO A and do the inti without data transfer and run regular deltas. If you dont do this, then the DTP for DSO a will pick up the full update request from PSA in delta run.
Gurus: what are your comments on this approach?
thanks
Srikanth

Similar Messages

  • Urgent: How to Populate SETUP table in LO for perticular period

    Hi Expert,
    I want to populate SETUP tables for perticuler period. Which one is the selection field.

    Hi,
    You can not add new selection fields to the selection screen for filling up the set up tables. The fields available for selection actually depends on the application you are referring to.
    If you see in the below transactions for filling up of set up tables for different applications, you will see that a certain date field is available for selection for some of them. Please refer below. You can also check it directly in the system using the transaction.
    Tcode: Application number: Date filed available
    OLI1BW: Application 03(material movements): Posting Date
    OLI3BW: Application 02: Document date
    OLI4BW: Application 04: Created on date
    OLI7BW: Application 11: No date selection possible
    OLI8BW: Application 12: No date selection possible
    OLI9BW: Application 13: No date selection possible
    Hope this helps,
    Regards,
    Shilpa

  • Data in setup tables and qued delta

    Hi Samuris'
    How can I see  1. the data in setup tables  2. Data in qued delta
    3.From which table(in R/3)  the data is extracted when we schedule a IP for a delta.
    Do we have any transaction code to view 1,2.
    Could anyone let me know exact flow of data when a request is raised from BW.I mean if it is a full load request,from which table in R/3, data gets captured.Also if it is delta load request,from which table in R/3, data gets captured.
    Any help is appreciated,
    Thanks in Advance!
    James

    Hi,
    first it depends on the data source....
    I guess you are talking about LO DSources.
    1. you can open the table itself (usually MCaax_SETUP, e.g MC03BF0SETUP) but this will be raw data, like in a trfc LUW); otherwise call transaction RSA3 with your LO datasource in full mode and you'll see the data as it will be extracted to BW.
    2 call SMQ1, double click MCEX03 for instance, again the queue name in the next screen, you'll see pending transactions (LUWS) to be updated in the BW delta queue, double clicking the TID will lead you to the data in the transaction...
    The corresponding table is ARFCSDATA and it is populated when, in our example, a material document is commited.
    3. it depends on your DSource: LO datasources will take their data from ARFCSDATA, other might extract their data directly from several DB tables...
    hope this helps...
    Olivier.
    Message was edited by:
            Olivier Cora

  • Table with Full / Delta Load information?

    Is there a table I can go to where I can see if a cube is a full load vs delta?
    Thanks, I will assign points!
    ~Nathaniel

    Hi,
    ckeck the table ROOSPRMSC in R/3.It gives you the complete details of your Init and Delta Loads.
    hope this helps.
    Assign points if useful.
    Regards,
    Venkat

  • LIS11 - will fill setup table again conflict with delta?

    Hi experts,
    we are using LIS11 delta mechanism. LIS11 data is used for two different dataflows in BW.
    Because of a delta problem with the R3 enhancements the delta doesn't work properly for one of these.
    For this one we want to do a full load until the problem in R3 is solved.
    Therefore we have to fill the setup tables again each time we want to do a full load.
    My question:
    Does filling the setup tables again conflict with the delta mechanism for the other flow?
    Or will delta continue to work properly?
    Marco

    hi,
    The delta type for all 2LIS_11* DS is ABR--Complete Delta with Deletion Flag Via Delta Queue.
    This means that there will be no conflict of data duplication in case of full repair, the delta is independent of set up tables.
    Delete and reload the setup tables and the delta will not be effected and also the data will also not be duplicated in cube.
    regards,
    Arvind.
    Edited by: Arvind Tekra on May 4, 2011 9:35 AM

  • BI Delta Load (Email Notification)

    Dear Experts,
    I'm wondering how can I setup an alert when Delta loads finishes either with the error or the success. Can someone please help?
    Your help is really appreciated!
    Thanks,
    Afnan

    Hi,
    This issue can happen while loading to PSA, where if one of the fields from Source has more number of digits than the actual limit of that data element.
    For Ex: If a key figure X is declared as an Integer with Length 10. It cannot accommodate a value that has more than 10 digits.
    Please check if any of your data has such huge data coming in with any of the fields. Characteristic fields can be an exception as they can accommodate any digits, I would prefer checking on Key Figure fields.

  • 2LIS_03_UM - FULL LOAD VIA SETUP TABLE NOT EQUAL TO DELTA

    Hello,
    I try to load stock data with 2LIS_03_UM.
    When I extract data using setup table and full load I don't get the same records as I get with delta load. Although the key figures values are the same, the documents numbers are different. Most documents from delta load are ML (material ledger) documents while documents from full load (via setup table) are mainly FI documents.
    What can be the reason? How can I fix it?
    Thank you,
    Hadar

    Hi,
    Delta load extracts data from Delta Queue based on your update mode selected in LBWE.
    Full Load or Init load extracts data from Setup tables, here if you are extracting data from setup tables ? did you fill the setup tables now or not after deleting the existing data of the setup tables?
    are you getting same values when compare to R/3 and BW data for some document numbers?

  • 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

  • Question regarding deltas and filling of setup tables

    Hello Friends,
    We are using the Sales Order Item Datasource 2LIS_11_VAITM. We have transported it to BI Production. We have initialized the delta and the deltas are running for the past 3-4 months.
    Now we had a new requirement which was getting satisfied by the Sales Order Header and Sales Order Header Status DataSources, 2LIS_11_VAHDR & 2LIS_11_VASTH respectively.
    Now we wan to transfer both these (header & header status) DataSources to BI Procution. My question is:
    1) Do we have to refill the setup tables again in R/3 for the Sales (11) application?
    2) Do we have to reload the entire Sales data again from scratch.
    3) Is there any way to transport the 2 new DataSources to BI Production and without disturbing the already running deltas of Sales Order Item Datasource?
    Regards,
    Prem.

    Hi,
    1) Do we have to refill the setup tables again in R/3 for the Sales (11) application?.
    Yes you need to refill the setuptables, because if you want to load deltas, you need to do Init then deltas, other wise first time when you are filled setup tables, (first load init with the existing data in setuptables) from that day to till date you can do full then you can set delta.
    It is better and good to fill setup tables and load.
    2) Do we have to reload the entire Sales data again from scratch.
    Any way you need down time to load the other 2 datasources, and also for 11 application you are filling setuptables.So for perfectness it is better to load from first.
    3) Is there any way to transport the 2 new DataSources to BI Production and without disturbing the already running deltas of Sales Order Item Datasource?
    If you transport the new datasources then delta won't distrub in BW. If you did any changes to DataSource and trying to transport it to production then it will give error, because LBWQ and RSA7 will have data so first you need to clear it and then transport it.
    Thanks
    Reddy

  • Setup table Administration with Direct Delta mode

    Hi guys,
    I have a direct delta as update mode for my 2LIS_11_VAITM extractor in R/3.
    I'd like to know if I have to manage the relative setup table (MC11VA0ITMSETUP) with this update mode also. 
    For instance, If I delete an ODS content and restart a new INIT on BW system, do I need to delete and then to fill the setup table?
    In general, Do I need always to menage the setup table with each kind of update mode (direct delta, queued delta and V3 update)?
    if you know the answers, please reply me direcly without insert link.
    Many Thanks.

    yes, you do....the initial loads for lo datasources are completely independent of the delta loads and hence of the delta method...
    /people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
    M.

  • 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,

  • LIS setup table loading and check after doing deletion and uploading

    Dear All,
    We are doing SAP HR upgrade in our ECC system for which there is a prerequisite to delete all the
    data from set up tables,can we skip this process while upgrade and if not than pls clarify me the follwing points
    1)what point we should consider for deletion and loading  of the data from setup tables .
    2)how we will ensure that after filling the setup tables the data will come right in BW system(how to test)
    if anyone of you have come across this scenario then pls help me.
    Thanks,
    Jyoti

    Hi sapta,
    Ok.  If you need to delete data then follow the following steps:
    (For all the LO datasources like SD/Pur/MM/PP)
    1. Pull all the delta data in BI. Delete it.
    2.Delete the data in RSA7 and LBWQ.
    3.Delete the setup table data in LBWG or by menu option from SBIW.
    Filling of setup table is through OLIBW( is the data source number) or by menu option in SBIW.
    You need to take downtime for ECC to fill setup tables so that you dont miss any postings.
    Hope it answers your question.
    Regards,
    Gaurav
    Edited by: Kanungo Gaurav on Jul 2, 2009 12:41 PM

  • Whats the Actual use of the Setup table apart from the Full/Init  loads

    Hi  guru's
      could u explain  whats the Actual use of the Setup table apart from the Full/Init  loads  in Lo Extraction

    Hello Guru,
    The Setup table is used mainly for storing the Historical data whereas the new and changed records will be maintained in the Update table.
    By storing the Historical data in the setup table you don't need to disturb the Application table anymore.
    Please go through the following blogs
    /people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
    /people/sap.user72/blog/2004/12/23/logistic-cockpit-delta-mechanism--episode-two-v3-update-when-some-problems-can-occur
    /people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
    /people/sap.user72/blog/2005/04/19/logistic-cockpit-a-new-deal-overshadowed-by-the-old-fashioned-lis
    /people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it
    /people/vikash.agrawal/blog/2006/12/18/one-stop-shop-for-all-your-lo-cockpit-needs
    https://websmp201.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700002719062002E
    Hope it helps
    Thanks,
    Chandran

  • Setup table and delta mechanisim

    Hi,
    Can anyone explain in detail setup table concept in LO extraction and
    Delta mechanisim?
    Sridhar

    Hi
    LO Cockpit Step By Step
    Here is LO Cockpit Step By Step
    LO EXTRACTION
    - Go to Transaction LBWE (LO Customizing Cockpit)
    1). Select Logistics Application
           SD Sales BW
                Extract Structures
    2). Select the desired Extract Structure and deactivate it first.
    3). Give the Transport Request number and continue
    4). Click on `Maintenance' to maintain such Extract Structure
           Select the fields of your choice and continue
                 Maintain DataSource if needed
    5). Activate the extract structure
    6). Give the Transport Request number and continue
    - Next step is to Delete the setup tables
    7). Go to T-Code SBIW
    8). Select Business Information Warehouse
    i. Setting for Application-Specific Datasources
    ii. Logistics
    iii. Managing Extract Structures
    iv. Initialization
    v. Delete the content of Setup tables (T-Code LBWG)
    vi. Select the application (01 u2013 Sales & Distribution) and Execute
    - Now, Fill the Setup tables
    9). Select Business Information Warehouse
    i. Setting for Application-Specific Datasources
    ii. Logistics
    iii. Managing Extract Structures
    iv. Initialization
    v. Filling the Setup tables
    vi. Application-Specific Setup of statistical data
    vii. SD Sales Orders u2013 Perform Setup (T-Code OLI7BW)
            Specify a Run Name and time and Date (put future date)
                 Execute
    - Check the data in Setup tables at RSA3
    - Replicate the DataSource
    Use of setup tables:
    You should fill the setup table in the R/3 system and extract the data to BW - the setup tables is in SBIW - after that you can do delta extractions by initialize the extractor.
    Full loads are always taken from the setup tables
    1. Data Flow
    Relevant T-Codes
    a) Initializtion
    LBWE: Maintain Extract Structure, DataSource, Active Status, Job Control, Update Mode
    SBIW, then follow tree menu path: Settings for App-Specific DS(PI) -> Logistics -> Managing Extract Structures -> Initialization -> App-Specific Setup of Statistical Data -> Choose XX Application  -> Delete/Fill Setup(reconstructing) Table content
    RSA3: Check content of setup table
    b) Delta upload
    SM13: Display update table/Extraction Queue content
    RSA7: Display Delta Queue content
    Edited by: Tapashi Saha on Jul 24, 2008 7:33 AM

  • Filtering Setup-Table and same filtering for Delta-Queue needed

    Dear All,
    I'm looking for the best solution to do the filtering for the delta-queue.
    In program RMCVNEUA I'm filtering (excluding specific SalesOrg) data for the setup-table creation. I'm loading these data to the BW system.
    BUT now my issue is, that with the delta-queue I'm getting also data for the SalesOrg I have excluded in the setup-table, as I have no filter for the delta-queue.
    My Question: Where/How to filter by the same criteria the entries for the delta-queue?
    Thanks for your support,
    Peggy
    some more details: Application 11; Queue-Name MCEX11; using 2LIS_11_VAHDR, 2LIS_11_VASTH, 2LIS_11_VAITM, 2LIS_11_V_SSL

    Dear Arvind,
    if there is no way in R/3 the solution must be in BW, but how exactly should that look like in the best/smartest way?
    Let us look in detail at an Example:
    DSO 0SD_O03 is getting data from 2LIS_11_VAHDR and 2LIS_11_VASTH.
    1) For VAHDR I have the chance to delete not needed VKORG already in the InfoPackage, or load first to PSA and than filter in DTP or delete in Startroutine in Transformation.
    2) BUT for VASTH, which has no VKORG information at all, I'm only able to delete the Dataset after it's loaded/activated in the DSO, as the rubbish-Dataset won't have any 0SALESORG. How to do that?
    Thx,
    Peggy

Maybe you are looking for