Problem in running Delta load for 2LIS_13_VDKON

Hi Friends,
I am working on LO Data Source i.e., 2LIS_13_VDKON, i have run the INIT setup tables through OLI9BW. There were 2389443 records.
Now, since in BW these records multiply depending on condition types I didn't want unnecessary records. So I have run multiple INITs in BW with selection criterias as I wanted data only from 01-Jan-10. Having done that, now I want to run deltas but the BW system is not letting me do. If I click on Delta in the infopackage (in update rule) then it selection criteria it adds up all those INIT selection criteria that I have run and I can't change it (as in it becomes non-updatable); why is it adding up all those selection criteria in Delta infopackage?
I want to fetch all deltas from the day I ran OLI9BW...How to run delta for those records updated after run of OLI9BW.
Thanks!

Hi,
Follow the steps, these steps are for SD module, but for your datasource, change the Tcode to fill setup tables and replace the SD DataSource with your datasource in the following steps.
1. First Install the DataSOurce in RSA5 and see it in RSA6 and activate in LBWE.
Before doing the steps from 2 to 6 lock the ECC System, i.e. no transaction will happen
2. Then delete the Queues in LBWQ like below
     MCEX11  --> For 2LIS_11_* 
     MCEX12  --> For 2LIS_12_* 
     MCEX13  --> For 2LIS_13_* 
  Be carefull while doing all these deleations in Production Servers
3. Then delete if any entry is there in RSA7
     Eg:
     2LIS_11_*
     2LIS_12_*
     2LIS_13_*
4. Then delete setp tables using LBWG Tocde and select Application Number. i.e. 11, 12 and 13.
5. Then Load Setup Tables using OLI7BW, OLI8BW and OLI9BW.
   Give Name of run = XYZ, Termination Date = tomorrows date and execute it in background.
   i.e. Program-->Execute in Background.
   2LIS_11_*  Use OLI7BW Tcode to fill the Setup tables
   2LIS_12_*  Use OLI8BW Tcode to fill the Setup tables
   2LIS_13_*  Use OLI9BW Tcode to fill the Setup tables
At the time of setup table filling no entry will exists in LBWQ in ECC for the following Queues.
     MCEX11  --> For 2LIS_11_* 
     MCEX12  --> For 2LIS_12_* 
     MCEX13  --> For 2LIS_13_* 
6. Check the job status in SM37 and once finish it then goto RSA3 and then execute it and check.
7. Then Replicate the DataSource in BW.
8. Install InfoCube/DSO from Business Content or cretae InfoCube/DSO and then Map the ECC DataSOurce Fields and BW          InfoObejcts in Transfer Rules (in BW 3.5) or in Transfermations (in BI 7.0).
9. Map the InfoObejcts in InfoSource and InfoObejects in InfoCube/DSO in in Update Rules (in BW 3.5) or in Transfermations
   (in BI 7.0).
10.Create InfoPackage and Load Init/Full.
11.Using DTP you can load to InfoCube/DSO (if it is BI 7.0) 
Thanks
Reddy

Similar Messages

  • Delta load for 0customer

    Hi Friends,
    I have a issue in delta load for 0customer. The load was initialized with data transfer for the first time load ,The data was loaded succesfully , now we have enhaced the 0customer_attr with customer group .In RSA3 if we check we are getting values for customer group. we created one delta infopackage with update status as delta and scheduled the load .we are getting data load success status but with 0 records. Please can anybody share the process for delta load for master data objects. Iam facing similar problem while uploading delta load for 0MATERIAL.
    Regards,
    Dippy

    Hi
    in source system, check whether your enhanced field is with hide check box ticked.
    As soon as you add filed in append structure by default it is having that field is hidden. You have to uncheck it.
    Then replicate the datasource in BW.
    Now if delta is the issue that you are not getting ant record, that may be because there is no change in master data, delta will only bring records when there will be nay change in master data update.
    So my suggestion is to crate a full repair infopackage, extract everything in to PSA and then load the data with FULL DTP.
    I hope this will work.
    Thank-You.
    Regards,
    Vinod

  • Delta load for 2LIS_06_INV is failing after EHP5 upgrade of ECC system

    Hi Experts,
    Our ECC Production system was upgraded to EHP5 last weekend.
    Since then Delta load for datasource 2LIS_06_INV is failing. This is the only datasource got impacted. Full Load and Initialization Loads are running fine. Only Delta load is failing because of following error:
    Error in the ABAP Application Program
    The current ABAP program "SAPMSSY1" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program "/BI0/SAPLQI2LIS_06_INV " in
    include "/BI0/LQI2LIS_06_INVU04 " in
    line 1:
    "Function "/BI0/QI2LIS_06_INV0002" not found in Function Library."
    Thanks and Regards,
    Sandeep Sharma

    SAP suggested Note to fix this issue.

  • Records are Missing when we run Delta Load( FIGL-ACCOUNT ITEMS)

    Hi,
      Some records are missing when we run Delta load.
    We have one generic data source on FAGLFLEXA table.
    We select  Field nm TIMESTAMP
    TIME STAMP IS LOCAL.
    upper limit is Blank
    Lower limit is 1000.
    we run this process chain every day.
    we select delta settings is New status for changed records.
    Please give me any idea why records are missing when we run deltas.
    Thanks
    Naik

    Hi Anju,
    Please ensure that you are following the below steps while Initilizing the application 13:
    1. All the users in source system, must be locked.
    2. Ensure that SMQ1 and RSA7 are having no data for application 13. Delete the application 13 datasource entries from RSA7.
    3. Delete and refill the setup tables for application 13.
    4. Run a INIT with data transfer load for the required datasources of application 13.
    5. The Deltas can follow from the next day.
    This will ensure that your deltas are fetching correct data. Note that, delta will pick up the same conditions on which the INIT load was run.
    Please let me know if you need any more information.
    Regards,
    Pankaj

  • Delta Loads for 2lis_02_scl and 2lis_02_itm

    Hi Experts,
    I am facing an issue, After initializing the setup tables and doing the init load for 2lis_02_scl and 2lis_02_itm whenever I do the delta loading for these two, all the dataload finish with green status and extracting 0 from 0 records.
    I can see the queues for both these datasources in RSA7 in R/3, yet no record is extracted.
    Any help will be appreciated.
    Regards.

    Hi,
    have a look into transaction smq1. there you should be able to see your extraction queues with the entry MCEX02 (or likewise)
    Please schedule the program RMBWV302 and when this one is finished, start the deltapackage.
    hth
    cheers
    sven

  • I can not make delta load for some component of public sector management

    Hello All:
    I´am using these three data source 0PU_IS_PS_31, 0PU_IS_PS_32 and 0PU_IS_PS_42 and I realize that I can not make delta loads. When I make the full load everything is correct even when I made the delta, the problem is that the Delta load is not extracting any new data or changed data.
    Do you have any idea to fix this issue?
    Thanks
    Message was edited by: Víctor Olivera

    Hello Victor,
    As u have already tried the delta load,I assume that u have already done the init load too.As system will not allow u to do delta load without doing an init load first.
    The first datasource u talked about..31..it needs new records created in table FMIOI table.
    What happens is..if u run a delta load immediately after an init load,there might not be new or changed records created in the system..therefore there arent any records in the delta queue.
    Could u try creating some commitment document transaction data,so that records get added in FMIOI table.Then see if the delta queue for this datasource shows any records.
    Links to BC pages for these datasources are below..
    http://help.sap.com/saphelp_nw04/helpdata/en/1a/8c425e8afe11d496d80000e835339d/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/1a/8c42618afe11d496d80000e835339d/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/e1/46a53ec5f0c0428fa8b9cfcdcd9fcd/frameset.htm
    Note that for 42 datasource..page says that delta update is not supported(though it does talk about updating delta queue).
    For 32 datasource source tables are FMIFIIT and FMIFIHD.
    For 42 datasource table is FMBDP.
    cheers,
    Vishvesh

  • Re: Delta Load for master attribute CUSTOMER

    Dear All,
    I have got the delta loading into 0customer_attr and 0 material_attr in production. Yesterday the load failed because the previous change run run has been terminated and locked the attributes of characterstics 0 material and 0customer.
    To solve this i went back and ran the attribute change run and all the locks got released.
    Now i know that i need to repaeat the delta load.
    If we go to the RSMO for the failed load i see that under details tab in processin option we have as follows
    Transfer rules(67-->67 records):No errors(This is Green)
       Master data received:Processing being started(Green)
       Transfer 67 data records in communication structure(Green)
    This is where the processing stopped.
    Update(0new/0changed)(in red): Errors occured
    My doubt is if i now repeat the load in process chain will the 67 records come into the0customer infoobject.
    Will this have any impact on the next day  delta load.
    Kindly advice.
    Regards
    Madhuri

    Hi abhijit,
    When i tried to do a repeat delta  the load failed again and when i check  for the error message i get the following
    Diagnosis
        The application program for the extraction of the data was called using
        update mode R . However, this is not supported by the InfoSource.
    System Response
        The data extraction is terminated.
    Procedure
        Check for relevant OSS Notes, or send a problem message of your own.
    Procedure for System Administration
    How do i proceed further.
    Regards
    Madhuri

  • Problem in initialization delta load

    Hi All,
    I am facing a problem while doing an initialization delta from one ODS obj to another.
    Error says "data is not been updated in PSA table"
    The ODS object I am trying to load is getting data from 3 ods below ODS obj, out of 3ODS's 2 were successfully loaded.
    While doing this particular load it's coming with the same error. I tried full load also, but results are same.
    Can anyone have some answers?
    Regards,
    Kironmoy

    Hi,
    In first init the data will move from the active data table to further data target then we will run delta at that tome the dat will go from change log table to further datatarget in our case u rrunning init but there is no daa in active data table so it is happening
    here two options are there
    1)either u can delete the change log table data and reload the data once again and do INIT with data transfer for further data target then it goes for next onwords delta data will come from change log table.
    2)otherwise u go for INIT WITH OUT DATATRANSFER now no records will come to ur targeted datatarget just it gives delta flexibility only (by default 1 record willl come it is for delta initilization) now u go for the delta. now which are the records are avilable in change log those records will move from changelog to ur targeted datatarget.
    Thanks
    sathish

  • First time delta process for 2lis_13_vdkon in bw 3.5?

    Hi all,
    Till now the data was loaded through setup tables, and there is no delta process being setup for 2lis_13_vdkon.
    Can anyone let me know how to carry out the delta process, so that the daily updates runs in the system rather than updating through a full update.
    Thanks
    Pooja

    Hi Pooja,
    Once you delete the setup table, it deletes the data for all the DataSources for the application area. In your case 13 (sales).
    Then, initialise the setup table. Make sure there is no transaction happening when the initialisation run is executed.
    Once the initialisation is complete in R/3 side, run the initialisation InfoPackage for the DataSource.
    Next load onwards, all the data will be stored in the delta queue in case of direct delta and in the update queue in ccase of queued delta. In any case you will get the delta data. You might have to create a new InfoPackage for delta.
    Roy

  • About delta loading for master data attribute

    Hi all,
    We have a master data attribute loading failed which is a delta loading. I have to fix this problem but I have two questions:
    1. how can I find the those delta requests because I need to delete all these failed requests first, am I right ? Master data is not like cube or ods that we can find the requests in Manage, for master data how can we find them ?
    2. Could you please let me know the detailed procedures to perform this delta loading again ?
    Thanks a lot

    Hi...
    1. how can I find the those delta requests because I need to delete all these failed requests first, am I right ? Master data is not like cube or ods that we can find the requests in Manage, for master data how can we find them ?
    Look.....for master data.....no need to delete request from the target..........just make the status red.......and repeat the load.....But problem is that master data sometimes does'nt support Repeat delta..........if u repeat......then load will again fail with Update mode R.........in that case u hav to do re-init.......
    1) delete the init flag.......(In the IP scheduler >> in the top Scheduler tab >> Initialization option for source system)
    2) Init with data transfer(if failed load picks some records)..........otherwise .....init without data transfer.....if the last delta failed picking 0 records.......
    3) then Delta.......
    2. Could you please let me know the detailed procedures to perform this delta loading again ?
    1) Make the QM status red.........to set back the init pointer.......
    2) Repeat the load.....
    After that.........if again load failed with Update mode R.....
    1) delete the init flag.......
    2) Init with data transfer(if failed load picks some records)..........otherwise init without data transfer.....
    3) then Delta.......
    Regards,
    Debjani.....

  • Is it possible to make a delta load for a Master data with Standard DS

    I have a full load bringing huge data for master data with standard datasource.
    I want to run a delta due to huge no. of records but when I create a new Infopackage it dont give a option for delta update.
    Are delta loads specific to only standard or customized DS's or any other reason behind that ?

    I kind of understand what you are asking about, but I am unclear as to how it pertains to our BO SDK.
    You are wanting to find the differences between a large dataset and another large dataset.
    I am not sure what an Infopackage is.
    Are you using the BO Enterprise SDK or some other product?
    Jason

  • Query running very slow for 2LIS_13_VDKON Extractor.

    Dear Experts
    Having no Standard InfoCube to accommodate the data from 2LIS_13_VDKON Extractor, I've created an InfoCube having the Standard DSO inbetween. The Data Flow is as below:
    2LIS_13_VDKON -> ZSD_DS17 (which is a copy of BCT DSO 0SD_O06) -> ZSD_C17 ---> ZSD_M02 (MultiProvider)
    We went live last week and there are only 1252377 records in the InfoCube at the moment in Production. The BEx Query designed on top of the MultiProvider runs by default for the last 3 Months (Variable created) initially and the User will be able to look up only the last 13 Months (another Variable created) of data at any given point in time.
    The User doesn't want any Selection Parameters on this Report and that's how it is created.
    The problem now is.. this 'Margin on Agreed Cost' Report taking about 3 Minutes and 5 Seconds to run.
    I have RSRV on the InfoCube and everything seems to be ok, tried Aggregates (though I understand that this number of records wouldn't need one to be created) and have also tried Query Cache today but no good.
    Is there anything that I might have overlooked when designing the InfoCube and the BEx Query? Attached are the screenshots of the InfoCube, MultiProvider and the BEx Query for your reference.
    Any suggestions are very much appreciated.
    Thanks in advance for your time.
    Chandu

    Hi Anshu
    Thanks for your time.
    The link you've sent was very useful indeed.
    I followed instructions from your link and below are the statistics 4 days after this Cube went into Production:
    As you could see, the InfoCube design is very fine.
    We have noticed that the Report runs within a few seconds when it is run by 0BILL_DATE in Selection Parameters. Therefore, we are trying to buy the End User to have some Selection Parameters so that the performance of the Report will improve.
    I have already created Aggregates for this Cube but in vain!
    Can anyone please send me the Screenshots of the InfoCube Design which captures all the fields of 2LIS_13_VDKON Extractor?
    Thanks,
    Chandu

  • Delta load for a data source not enabled

    Dear Experts,
    We have got the requirement to create reports on shipment details.
    Based on the requirement we have identified the
    Infosouce/ Data source : 0OI_TD_OIGSII
    Info Cube: 0OI_TDC01. we think this cube will satisfy the requiremnt.
    But the problem is the data source is not delta enabled. so how do we extract the data and how to capture the delta.
    when we checked in Roosource table the delta field is blank (Delta only with Full Upload (ODS or InfoPackage Selection))
    These data sources are IS OIL specific, so dont know the data extraction procedure.
    Please through some light and help me.
    Please advise.
    Regards
    venu

    Delete duplicate request is a process chain variant, which will allow you to set the duplicate request deletion options. You need to explore those options.
    Now say you have a routine in the DTPs.
    DTP1 = Current Month
    DTP2 = Prevoius Month
    In the month of July,
    DTP1 = 07/2009
    DTP2 = 06/2009
    On daily basis DTP1 will load data for July and DTP2 will load data for June. Now delete duplicate request will delete the previous requests loaded by each of them for the same month. Meaning delete duplicate request for DTP1, will delete the request loaded for 07/2009 and DTP2 will delete the duplicate request for 06/2009.
    Now when you will be in Aug, the routine will change the selection criteria
    DTP1 = 08/2009
    DTP2 = 07/2009, so now DTP2 will delete teh duplicate request for 07/2009 and load the new data. Now the data changed for 06/2009 is not possible to load as you have only 2 DTPs.
    For safer side, you can create 3 DTPs to take care of the last 3 months, but first test the logic for two DTPs and then go further for the third DTP.
    - Danny

  • Delta loading for 0HR_PY_1

    Hi!
    We are trying to do a delta load fot the 0HR_PY_1 Infosource.If we simulate the delta extraction in R3, the Data Source extracts data , however when we load data into BW , no data are loaded.
    Can anyboby help us?
    Thank you very much

    hi Carolina,
    check if authorization problem
    Note 672514 - BW extraction for 0HR_PY_1 does not deliver any data records
    Symptom
    The payroll extractor does not return any data to the BW system. The data is selected if you call transaction RSA3 (Extractor Checker) in the source system.
    Other terms
    0HR_PY_1, hrms_biw_extract_py1, payroll
    Reason and Prerequisites
    This problem is caused by missing authorizations for the BW remote user in the source system.
    Solution
    also  Note 964569 - Extractor 0HR_PY_1 extracts no data
    hope this helps.

  • Delta loads - for DB Connect  and master data.

    Hi there,
    Would appreciate if any one clarify me on:
    1) Are delta loads are possible as far as Master data is concerned?
    2) What are all types of data loads (Initial/ delta/ Full)are possible as far extracting data from DB connect is concerned?
    Thanks in anticipation.
    Rgds,
    A.
    Message was edited by: Ash

    Hi Ash,
    As far as I know, with DB connect you have the only option to have delta functionality - to use ODSs. Make full load from the source system to ODSs. Then update data targets from ODSs. During this update you'll have an option for init/full/delta load.
    Best regards,
    Eugene

Maybe you are looking for