Repeat Delta problem

Hai,
  I have a delta update from 2LIS_02_SGR to an Infocube. For the past 5 days, the pull had failed. To repull that delta, I had to set the QM status to RED and delete the requests from the Infoprovider. But for few requests, the requests were set to RED in the (INFOCOUBE - > MANAGE request) and deleted instead of setting it to RED in RSMO. Now, after i deleting the requests I realized it and then i set the status to RED in RSMO. Now if  I repull the data, I get that window that asks if the delta has to be repulled. I clicked on REQUEST AGAIN. But I don't find all the failed delta data to have come into BW. Why is it so?
Regards,
Neha Solanki

Hi Neha,
I suppose that you neede not worry much because system has prompted you the option of repeat delta.
As you have selected request again it will bring the data that should have been pulled in last delta also.
If you would like to cross check the data, i think, you can use some date selections and see the data records in R/3 tables and match them with BW.
Hope this helps.
Regards,
Sagar

Similar Messages

  • Inconsistencies data between ODS and RSA3 in SAP system (delta problem??)

    Hi everyone,
    I have a problem in my SAP BW production system. There is inconsistencies data between ODS (using tcode LISTCUBE) and Datasource in SAP system (tcode RSA3).
    I'm using Datasource: 0FI_GL_10 and ODS: 0FIGL_O10.
    In SAP system (using RSA3):
    GL Account: 1202012091
    Comp Code : 5400
    Bus Area: 5401
    Fiscal Year :2008
    Period: 07
    Accum Balance : $0
    Credit Total: $350
    Debit Total: $350
    Sales : $0 
    And in ODS (using ListCube):
    GL Account: 1202012091
    Comp Code : 5400
    Bus Area: 5401
    Fiscal Year :2008
    Period: 07
    0BALANCE : $350  (it should be $0,shouldn't it? )
    0CREDIT: $0 (it should be $350,shouldn't it? )
    0DEBIT: $350
    0SALES: $350 (it should be $0,shouldn't it?)
    I have tried these :
    1. Check if there is a start routine / routine or not in transfer or update rules....and...i get nothing
    2. Check the data using tcode FBL3N..but the data is ok
    And then i tried to trace the process chain and find error on delta infopackage which pull these data
    Date
    07.30.2008 : 231141 records --> error (ODS activation) --> request has deleted forever
    07.31.2008 : 2848 records   --> error (ODS activation) --> request has deleted forever
    08.01.2008 : 135679 records --> error (ODS activation) --> request has deleted forever
    08.02.2008 : 135679 records --> successfull repeat delta action
    From 30 July until 1 August there is an error on delta infopackage because
    fail to activate ODS (No SID found for value 'RIM' of characteristic 0UNIT). On 2 August someone delete the red requests and repeat the delta and success. Is there any possibilities that this problem arise because of this? If this the cause, how to bring back 2848 and 231141 records which has deleted?
    Thank you and Regards,
    -Satria-

    Hi everyone,
    I have solved my problem. I executed my infopackage again (selection condition using GL Account which have wrong amount) with update mode 'Full update' and choose Scheduler > Repair Full Request and tick the checkbox.Thank you.
    Regards,
    -Satria-

  • Repeat Delta in case we loss the data from BWP

    Dear Experts
    I am facing a critical Problem related to Delta records uploading in BWP server. I have uploaded the Delta records yesterday (16.06.2011) in the Morning from (6.00A.M. to 14.00P.M) and pull the delta records in SAPBW. then in the night due to some reason our BWP server crashed. Now its Up and the data is restored upto 16.06.2011 Morning upto 06.00 A.M. i.e. before the execution of process chains on 16.01.2011 . My Question is
    1. If I execute the Process chains today will it breing the Delta records of 16.06.2011 as well (Repeat delta) Automatically or do i have to perform some configration.
    2. Whether the Repeat delta is possible only if we make the request RED and not when we loose the data as we have.
    Pl advice Urgently........................
    Thanks in advance.
    Dinesh Sharma

    1. delta load done to PSA. records edited and loaded to targets.
    2. repeat delta done to PSA. It contains all records from step 1 and any new records written to delta queue. this is deleted.
    3. Next day repeat happens. This brings records from step 2 (already has records from step 1) and any new records written to delta queue.
    The procedure followed was not correct and hence resulted in duplicates. When a repeat delta is done, the delta records from the previous delta request will be fetched along with any new records that have come into the queue after that.

  • Repeat delta data issue

    Hello guys,
    I have a strange issue here. I load say ODS2 from ODS1. When trying to load ODS2 one day, i find and issue and the load is turned red. When i executed the delta IP again, it asked for the repeat of the delta, for which i said yes. I did not delete any datamart status from ODS1. This repeat got me double records than the original request, and now i have doubled records in ODS2. Since ODS2 is on addition, the doubling data issue. Does anyone had this problem? Why the repeat of delta updated double the number of records than what it shud be? will be great if anyone can come up with a clarification.
    Regards
    Sriram

    Hi Sriram,
    At First you need to Delete the Request from ODS2,
    Question is which request should be deleted. answered below.
    In ODS1 --> Note the Request where Repeat of delta has occured. Check the datamart Request  of that Repeat Request. This datamark request clearly shows that At what request in ODS2 its updated.
    Now your job step by step as below:-
    1. Delete request in ODS2 (Please note :request which you had taken in the datamart of ODS1).
    2. Delete the Datamart of the ODS1 at the Repeat delta request.
    3. Delete Request of ODS1(till where you had removed the datamart for this ODS)
    4. Go to reconstruction tab and reconstruct the request which are correct (eliminate failed request)
    Please note:- please reconstruct one(1) request and then datamart. Once you do this you will come to know the logic behind.
    5. Then Datamart to ODS2.
    If its complicated to understand, please call call me
    Thanks
    Regards
    Hari

  • Pl help me with repeat delta for text info object

    Hello during the delta loads delta got failed for some text object, I know how to repeat the request for transction data but not sure how to request the repeat delta for text object like 0material_text.
    I mean i am not sure is there way i can go and change the QM status of request to red and then request repeat delta again, so do we follow same procedure for text objects or something else pl suggest.
    Pl suggest the steps
    due point will be assigned.
    Krish

    Hi Krish,
    With master data delta repeats sometimes you have problems, and you may get a message that Update Mode R is not supported. The only way out of this situation is to do a reinit and load the data again so that you are not missing records. Since this is just master data, the data volume is not going to be too high, and it overwrites so no issues with data either.
    See here for reference... Re: Update mode R is not supported by the extraction API
    Hope this helps...

  • Master data Extraction and Repeat delta

    hi Expert's I am extracting master data from R/3.These are Delta loads.Now when I started extracting it is pops up message stating earlier request is not correct so repeat must be done.could any one of analyse the problem and give the solution.I also dont know how to do repeat delta.Plz explain with steps.
    Thanks in Advance.
    vasu.

    Hi Vasu,
    Goto Manage, Select the Request and make it red(See below how to make it red), then click on the Monitor icon(just side to it). It will take you to Monitor screen.
    here select the particular load, on the right side, on the status tab, click on the load and make it red.
    Now goback to the infopackage, schedule, it will do repeat delta.If the Problem still persist, then delete the Requet in the Manage screen and schedule again. This should work
    Regards
    Vj

  • Repeat Delta bringing previous delta too

    Hi BIs,
    SAP system sometimes acting strangely by bringing Current days delta + previous days delta when Delta Info package was requested again.In Monitor it is displaying as Repeat delta only.
    This strange behavior is occuring once in a while and not evry time
    Could any one tell me why it is behaving like this,if so any possible ways to avoid this
    Thanks and regards
    Bala

    HI ,
    generally if you make the delta request red and then repeat it that only will set your init pointer ..
    but i think  there is some problem with the init pointer setting .. so can try one thing run once init without data transfer that will set you init flag .. and run your deltas... this might solve  your problem ..
    Regards,
    shikha

  • Issue with Repeat Delta

    Hi,
    R/3 system was down and delta failed for delivery scl lines. This event happened five days back. We have deleted the red request with zero records in the DSO and then tried to re-load..we got a pop up saying last delta was incorrect so we did a repeat delta. Now we noticed, the repeat delta brought the successful records of the previous day. (DUPLICATE records)
    Ex: Day1 - 10 delta records
          Day2 - 15 delta records - Loads Failed/Repeat Delta - In these 15 records 10 of them are from Day 1.
    The key figures are addition in the DSO. Currently the quantities have doubled for day 1 deliveries. Has any body encountered this situation if so how was it handled without re-init. If i'm not clear please don't hesitate to ask.
    Thanks,
    Varma.

    HI RVarma,
    As suggested in above post you will be require to do the selective deletion for the duplicate records that come result in wrong value for keyfigure. Now for selective deletion  DSO-> manage>Content tab> Selective-> Deletion selection -> give the selction value for keyfield->start---> copy the job ---> sm37 monitor itand wait it to finish.
    once finsih, check the contemt of a dso  by running the query or display data make sure the data deletes. Now for getting the data
    Double click on infopackage --->Scheduler -
    > repir full request ---> select .
    This will solve your problem
    Thanks,
    Deepak

  • Repeat Delta mechanism for FI-CO & Generic extractor.

    Hello Guys,
    Can any one please let me know whether there is repeat delta is possible for FI/CO data sources if we miss any daily dela loads.
    If its there, how it works.
    thanks in advance
    peter.

    Hi,
    Yes, it is possible to repeat the failed delta for FICO extractors. One thing you need to note is that you need to request the delta second time only then you will get records to BW. First time repeat will fetch 0 records.
    Hope this helps
    Regards.,
    Srni

  • Option in Infopack for Load of Repeat Delta

    Hi , I would like to know what option is avilable to load repeat delta in Infopack.
    When i run RSA7 , and select by Datasource , There is 28 records in the Repeted Delta Queue.
    Thanks

    Hi Ashwani,
    If a delta load from a datasource fails or is manually marked as 'RED' in the monitor, the next time you run the 'Delta' InfoPackage for that datasource, you will get a message asking you whether you want to repeat the previous delta request since it had failed. This mechanism is provided so that in case of errors during data loads, none of the records are missed out in a subsequent load.

  • Repeat delta are failing

    Hello experts,
    I have an imp production issue. We had delta failing in one of LO Cockpit extractor for last 4 days.
    Message: Error occurred in the data selection
    Job terminated in source system --> Request set to red
    Message no. RSM078
    I did repeat delta (by changing status to red and deleting requests). But still I get same message.
    Please help.
    Rita.

    SM 37 LOG:
    Job started
    Step 001 started (program SBIE0001, variant &0000000017045, user ID ALEREMO
    Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks)
    DATASOURCE = 2LIS_18_I0NOTIF
    RLOGSYS    = PRODCLNT200
    REQUNR     = REQU_D4VWYY4JTTY9ODFHL16WPLR5M
    UPDMODE    = R
    LANGUAGES  = *
             Current Values for Selected Profile Parameters               *
    abap/heap_area_nondia......... 0                                       *
    abap/heap_area_total.......... 8588886016                              *
    abap/heaplimit................ 40000000                                *
    zcsa/installed_languages...... 123ACEFIJKLMNOPSUVc                     *
    zcsa/system_language.......... E                                       *
    ztta/max_memreq_MB............ 2047                                    *
    ztta/roll_area................ 6500000                                 *
    ztta/roll_extension........... 2000000000                              *
    Call customer enhancement BW_BTE_CALL_BW204010_E (BTE) with 1,491 records
    Result of customer enhancement: 1,491 records
    Call customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 1,491 records
    ABAP/4 processor: COMPUTE_INT_TIMES_OVERFLOW
    Job cancelled

  • Repeat delta

    How to do "Repeat delta"? Is there any direct option available from BW side for this? If not, from R/3 side using RSA7 transaction when doing "Delta repetition" it is asking for a variant to Save. What does this mean? What are the other input fields that we need to fill in on this screen?

    Hi,
    You do a repeat delta when the original delta load fails or the delta request gets deleted from the infoprovider.
    In this case, mark the request red in the infoprovider and delete it. Run the delta infopackage again. It'll ask you for repeating the delta. Say yes and repeat delta will take place. One word of caution though is if the original delta has failed, make sure you remove the cause of the error before running the repeat delta as that'll fail too if the original cause of the error is not removed.
    In terms of repeat delta you don't have to do anything on the R3 side. As mentioned above just follow the steps and rerun the delta infopackage for the repeat delta.
    Cheers,
    Kedar

  • I installed Adobe CS6 Design & Web Premium on my Mac Book Pro a few years ago but have repeatedly encountered problems with the programs freezing or not opening properly. It's a Student and Teacher Licensing version so an academic ID is required but I am

    I installed Adobe CS6 Design & Web Premium on my Mac Book Pro a few years ago but have repeatedly encountered problems with the programs freezing or not opening properly. It's a Student and Teacher Licensing version so an academic ID is required but I am no longer a student--can I still reinstall it since my academic ID may no longer be valid?

    Erin Elzo as long as the serial number has been registered under your account at http://www.adobe.com/ then you should be able to continue to utilize the software.  You can find details on how to locate your registered serial number at Find your serial number quickly - http://helpx.adobe.com/x-productkb/global/find-serial-number.html.

  • Repeat Delta extraction behaviour

    Hi experts,
    Ive been getting conflicting thoughts on delta extraction behaviour, so I thought Id just ask it out here. Here are two prominent scenarios:
    1. Our delta failed on sunday, we execute a repeat delta on monday. It only picks up the sunday failed data, it does not pick up any other new records that came in monday.  This is for a generic extractor, R/3 to Cube.
    - My understanding is that when we do a repeat delta, it should pick up the failed request + any new records to date.  Or does a repeat delta ONLY pick up the failed request and disregards new data? Is the behaviour extractor specific? 
    2. Our delta failed on sunday, we execute a repeat delta on monday. The request comes up with 0 transferred, we kick of another delta which now picks up everything from the failed request up to the present including new data. This is for 0FI_AR_4.
    - Why is it this repeat delta behaviour differs from the first?  Is it because this is a FI extractor with inherent behaviour?  Instead of picking up the failed request, it picks up 0 records and then a delta is required to pick up all the data.
    mark

    Hi,
    Repeat delta means the data that was collected by the delta queue and not updated to BW vl be updated to the data target., i.e. it picks only the failed request data , not the new ones which are updated in the mean time.
    The next delta vl pick up the new records.
    It is general to all the extractors except COPA.
    For COPA , it updates data based on the time stamp.
    Please check the below document for COPA extraction (deltas).
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sapportals.km.docs/library/biw/g-i/how%20to%20co-pa%20extraction%203.0x
    Assign points if it helps.....

  • Repeat delta in BI

    Hi,
    My delta load worked fine but my PSA load via DTP failed due to an incorrect data.
    How can I do another load by scratch and repeat the delta?
    Do i need to delete the PSA and turn the delta load to "red" for BI to realize the delta did not happen?
    Thanks for your reply.
    Cesar

    HI,
    Select the incorrect request and Manually make it to Red in techinical status and also in manage of Info provider.
    Later on delete the request in info provider and also PSA>.
    And reschudule the load in using info package tyhen it askds for the repeat of delta.
    Select the repeat delta and load till PSA and later on Run DTP.

Maybe you are looking for