Regarding Delta Record

Hi,
Is the delta record is capture for any field changes (Including KF, CHAR) for a particular sales/Delivery/Billing document or on changes of specific fields for sales/Delivery/Billing document.
If delta capture for specific fields change then where (Tables) these fields are maintained and how to find out this.
Points asssured....
Thanks,
Debasish

I meant a ZFIELD added in VBRP (billing docs items) for instance... If you use a standard SD exit to populate this field, the change will be captured by the delta mechanism just before the system COMMITS the transaction (this particular billing document change)...
Adding a ZFIELD in your extract structure will not suffice: suppose that you are adding a ZFIELD in your billing items extract structure; let's assume that your enhancement is populating this field with a simple lookup to VBRK (the header of a billing document).
In few words you want to capture a change in you billdoc head and extract it with your billitm DSource.
This won't work: if a user change the header of a billdoc, only 2LIS_13_VDHDR will capture a delta. 2LIS_13_VDITM won't get any delta record since no item has been changed... Note that enabling this feature would considerably "complexify"  the extraction in oddition to bring way much more records... indeed a before image reversal and an after image of the record (before and after COMMIT) would have to be extracted in order to avoid double records in BW....
The above stuff should better be done in BW itself by staging your data with DSOs or even with modelling...
hope this shed light...
Olivier.

Similar Messages

  • Delta Records is not getting updated in delta queus when changes done

    Hi All,
    In Quality system , when a user makes a change to an order's ship-to address, the changes are "triggering" a delta record into the delta tables for BI to extract. This can be seen via tcode rsa3's delta tester.
    In Productionn System, when the user makes the exact same change, nothing is added to the delta table and the changes never come over to BI unless a full extract is request for the order.
    Why changes not getting updated, please give your inputs.
    Thanks & Regards,
    Venkat Vanarasi.

    Do you have your V3 update job active and running? THis job wites changes to the delta queue. Of course your datasource has to been initialized and a delta queue should be setup. You can check it in RSA7.
    Regards,
    Juergen

  • Impact of Delta Records on Key Figure Summation in DSO

    Hi experts,
    I have a key figure with aggregation type "summation" in a DSO. I would like to know the impact of delta records on the key figure.
    E.g.
    source DSO
    doc_id (key) | doc_pos | type | amount
    4711 | 1 | A | 100 USD
    4711 | 2 | B | 20 USD
    target DSO
    doc_id (key) | amount
    4711 | 120 USD
    If the first record is modified ("type" from A to C) as follows and delta-loaded to target DSO:
    4711 | 1 | C | 100 USD
    This will lead to incorrect amount:
    target DSO
    doc_id (key) | amount
    4711 | 220 USD
    How can I handle this situation?
    Thanks in advance.
    Regards,
    Meng

    Hi..
    I believe one document number and document Item will have only one type.
    Like 4711      1    should have only one type ( A / B / C).
    If the above assumption is true then just remove Doc Type from Key field of source DSO.
    Then From Source to Target Change Log table can handle this.
    Regards
    Anindya

  • Delta records not updating from DSO to CUBE in BI 7

    Hi Experts,
    Delta records not updating from DSO to CUBE
    in DSO keyfigure value showing '0' but in CUBE same record showing '-I '
    I cheked in Change log table in DSO its have 5 records
    ODSR_4LKIX7QHZX0VQB9IDR9MVQ65M -  -1
    ODSR_4LKIX7QHZX0VQB9IDR9MVQ65M -   0
    ODSR_4LIF02ZV32F1M85DXHUCSH0DL -   0
    ODSR_4LIF02ZV32F1M85DXHUCSH0DL -   1
    ODSR_4LH8CXKUJPW2JDS0LC775N4MH -   0
    but active data table have one record - 0
    how to corrcct the delta load??
    Regards,
    Jai

    Hi,
    I think initially the value was 0 (ODSR_4LH8CXKUJPW2JDS0LC775N4MH - 0, new image in changelog) and this got loaded to the cube.
    Then the value got changed to 1 (ODSR_4LIF02ZV32F1M85DXHUCSH0DL - 0, before image & ODSR_4LIF02ZV32F1M85DXHUCSH0DL - 1, after image). Now this record updates the cube with value 1. The cube has 2 records, one with 0 value and the other with 1.
    The value got changed again to 0 (ODSR_4LKIX7QHZX0VQB9IDR9MVQ65M - (-1), before image &
    ODSR_4LKIX7QHZX0VQB9IDR9MVQ65M - 0, after image). Now these records get aggregated and update the cube with (-1).
    The cube has 3 records, with 0, 1 and -1 values....the effective total is 0 which is correct.
    Is this not what you see in the cube? were the earlier req deleted from the cube?

  • How to reprocess delta records during subsequent update of data targets

    Hi,
    I have an ODS which sends in delta records to a cube above it. Now there is a data load, happening monthy from a flat file, which was successful upto the ODS, but failed in the cube due to one invalid record. How do I reprocess this data load after correction of the invalid records in the source flat file?
    The method I currently follow is to delete the failed request from the cube and then do a selective delete of records from the ODS and then reload the last data after correction.
    Is there a better way to just reprocess the last load from the flat file?
    Thanks & regards,
    Nikhil

    Hi Bhanu,
    Thanks for the response. I will explain a bit more in detail. Suppose there are 5 records coming in from the flat file - now 4 of those records are correct and one has invalid data.
    All 5 records get loaded to the ODS successfully but in the cube we have a function module which works on the data and aborts the entire data package if it finds even one invalid record. So nothing gets loaded into the cube at all.
    Now if we correct the one invalid record and then reload into the ODS - it will just send this corrected record over to the cube and we will miss out on the other 4 records which were originally correct since the ODS does not detect them as changed.
    If we delete the request from the ODS (rather than doing the selective delete) then it disables the delta in the ODS asnd we have to reinitialise everything - which we cannot afford to do in a production environment.
    Hope the problem is a bit more clear now.
    I was looking for some way to just resend all the five records - with the one corrected record to the cube without going through this selective delete process sinc eits too cumbersome and we run the risk of messing up with actual data ina  production environment.
    Thanks for the help,
    regards,
    Nikhil

  • Loading Last three days of delta records in Production Server

    Hi
    I have a Process Chain in BI-Production Server which runs dailiy  and loads the delta records dailiy  . I have 'Custom DataSource' which loads the data from QM-Tables .
    My Process Chain is failied due to the "Caller 09 Error for the datasource". So now i transported that datasource from R/3-Dev To R/3-Production and replicated into BI-Production Server .
    So how can i load the delta records of last three days . I mean , how can i scehdule the last three days of delta updated records .
    pls let me  know
    regards
    Kumar

    Remove the failed request. Repeat the delta. This will upload previous failed request
    Repeat the delta again with infopackage selection for 3 days

  • Missing Delta Records for 2LIS_02_ITM & SCL

    Hi Experts,
    this is how my problem goes.
    i have done my set up table filled on 12th Dec 2010 and from that time onwards the delta were running everyday and filling the DSO and Cube.
    Accidently by some others PC in prod all my delta loads and the setup table load is being deleted except yesterday in PSA for these 2 extractors and now because of some change i have to do a full load to DSO.
    But as the PSA is emply and have only yesterday's request i have, deleted that one as well and done a Init Delta to it and i found out that only the Set up table is comming now and all the deltas in between are missing.
    i have tried a full LOAd to PSA and the result is same.
    How can i get those missing delta records from 12th Dec last year till today with out doing another set up table fill  or Do i have to have fill the set up table again till today and thats the only way? i will set the delta again after that.
    Do we have to have all the user locked for the setup table fill (for Queued Delta type) ? Lot of people says yes you have to and others says no you don't require. i got one white paper and it clearly says no user locking is required. please find the link below. what is the correct way?
    [http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d019f683-eac1-2b10-40a6-cfe48796a4ca?quicklink=index&overridelayout=true]

    Hi,
    As per my knowledge you want load particular period of data try repair request may issue solve.
    Regards
    Sivaraju

  • Delta record not getting created

    Hello Experts -
    I'm working with 0mat_plant_attr datasource.
    In ECC, I made changes to some materials in MM02. I changed the values of MRP Type and Rounding Value in MRP1 tab. The data is saved correctly but a delta record is not getting created. In RSA7, no records are there for 0mat_plant_attr. MRP Type, Rounding Values are attributes of 0mat_plant. I did run the initial infopackage from BW to enable the delta.
    Can someone please help me with this? I'm not doing something correctly.
    Thanks!

    Hi Syed,
    I think you may have to run an attribute change run after executing your infopackage to see the changes.  The modified attribute needs to be set as active in by the attribute change run.
    Master data & attribute chage run
    Regards,
    John

  • Delivery Delta Records missing

    Hi Friends !
    We have missd the delta records for 4 days. Only way I know to run the setup table again & get all the records till date. Then schedule V3 jobs & next day onwards delta records will be pulled. Do we have any other way to get those missed records? Please advise.
    With Regards
    Rekha

    Hi Rekha,
    Please follow the below steps in R3 side
    goto RSA3-->give DS name press enter
    below you will get selection screen
    give you delivery numbers as selections
    then execute, if you get records here then definitely you should get records when you run the IP.
    Hope this helps
    Regards,
    Venkatesh.

  • Re Delta records

    Hi All,
    We are loading data ecc to bw system (datasource to cube) and by mistake last two request(2days) got deleted even in PSA data is not available,
    So can any one  help me out to get last few days delta records,
    Is any process/tcode to recover delta request...
    Regards,
    Stanzal

    Hi  Lucy
    Check this below thread.
    Re: Job is runnning after failed job in PSA
    ..and its not possible to give exact suggestion until and unless we know DataSource name.
    Delta mechanism varies with DataSource
    Regards
    Anindya

  • How to debug Delta records..urgent

    Hi All,
    I loaded some records with delta mode.
    In rsa3, I select delta mode D, and clk Excute button, But It is saying  "Error During Execution".
    A. What is the reason Can any one explain?
    B. How to Debug my delta records?
    Pls explain Urgent.
    Thanks & Regards,
    Lakshmi.K.

    Hi,
    in case of simulation of update mode D you also have to provide the name of your target system. Then check the box debug mode. After clicking the execution button you are in the coding right before the extraction fm gets called. Jump into in by pressing F5 ....
    But first of all you need to make sure that your datasource provides a delta (this may cause the 'error during execution').
    regards
    Siggi

  • Generating deltas records after a work order status change

    Hi
    We are currently reporting on Work Order status changes in BW. However, the process team has written an ABAP program that allows users to change a Work Order status or an Opeartion status. Any changes using this method do not trigger a delta record to be written to the Outbound Queue MCEX17 and subsequently we do not pick them up in BW without having to to a re-initialise.
    Could anyone tell me how we could trigger a delta to be written to the Outbound Queue in the same manner as the standard Work Order change transaction IW32.
    Cheers, Mark

    Hi
    I m not sure about functionality though but you can create delta by using FM...
    Search SDN and you will get doc for that..
    Regards
    Guarav
    Assign points if it helps

  • Delta Records

    Hi All,
    We have a delta load, by mistakenly we have deleted the delta request and we have delete the backupdata also(PSA request)There are apporximatly 12000 records.
    Is there any way to get back these delta records......i know the only way to do full load.
    but still i want to know is there any way at r/3 side to know daily wise delta records....
    This DS belogs to HR application.
    please suggest.

    Hi,
    Dont you have the request in the reconstruction tab of the cube?YOu will if you are using 3.X flow.
    If yes then reconstruct it...
    or else follow Sreekanth's advice.
    You will see the request in RSMO under deleted requests.
    Regards,
    Mansi
    Edited by: mansi dandavate on May 20, 2009 11:55 AM

  • "Error when reading ATP delta records"

    Hi,
    I have created Integration models for Location, Product, ATP Check, ATP Configuration, Stock and Sales Order.
    After creating IM's when I tried to run ATP on my Sales Order I'm getting  error " "Error when reading ATP delta records".
    Can anyone provide me why I'm facing this error.
    Thanks in Advance.
    Ram

    Dear Ram,
    For the product/locations you are checking, it appears that ATP objects in the liveCache are missing which normally are created automatically  when products and locations are created in APO.
    I would advise to recreate all needed products and locations.
    In APO, i.e. make again an initial data transfer of the master data from R/3. Previously the existing ones should be deleted to be sure that they will be created again. Then the problem should be solved. 
    If this does not help please check the the connection and LC settings to LDA and please try to restart the livecache. A potential explanation for the error would be an incorrectly maintained LDA connection to liveCache. Please check this by running transaction  /SAPAPO/OM13 and selecting the 'checks' section.                    
    The problem with the LDA connection could be e.g. very simple. If you check the table dbcon, which contains the description of the liveCache connections , if the liveCache names for LCA and LDA are different you should ensure, that the connections LCA and LDA are setup for the same liveCache (con_env in dbcon).                  
    I hope this helps.
    Regards,
    TIbor

  • No.of transferred records do not match with delta records in RSA7

    Hi,
    The full update was failing since a number of days in 0vendor because of error in the source system. So I did an initialize with data transfer and corrected the PSA data and updated it using scheduler in the infoobject. In this case the number of transferred records was 24300 and added records was 0.Next I executed the delta infopackage and was expecting 0 records,since there were 0 records in rsa7. But I got 16000 records.Can you explain me why this happened?
    Regards,
    Shalaka

    Hi Shalaka,
    In which version of SAP you are working?
    You might want to have a look at the table BDCP2 which is a different table that handles the delta mechanism for the change pointers.
    You can reset the processing status using the program RSA1BDCP ex with following entries.
    Now, coming to your issue - to verify the initial loads I am listing some basic checks(step by step).
    You can give it a try in Dev/QAS if you have any restrictions in Prod.
    1. Check and verify if the RSA7 delta queue is present.
    2. In BW system, delete the INITIALIZATION request from infopackage - This should delete the delta queue from RSA7 in ECC system. (I am not 100% sure about this so try this once)
    3. Re-initialize the datasource from BW system and note the no. of incoming records in BW. This should match with LFA1 entries.
    4. Check the delta queue in RSA7 - There should be a new delta queue created
    5. Start the Delta load - The should not be any records coming in to BW
    6. Check the entries in table BDCP2 and its process indicator.
    7. Create a new vendor from XK01 and check the entry again in BDCP2 table.
    8. Run the delta again in BW and this time delta should have the newly created vendor.
    Also be aware that since its a master data datasource and deals with change pointers you will not see any entries in RSA7.
    A possible reason I could think of you getting 16000 records in delta is because you might have initialize the datasource is past and then started the FULL loads. So the deltas actually started accumulated in BDCP2 with processing status as BLANK and then when you triggered delta again back now all the historical deltas are processed.
    This apply with BDCPV too if you are on older version of SAP.
    Did you tried running delta's multiple times - you should not face any delta records when the processing status of change pointers is set to 'Processed' i.e. 'X'.
    PS: You can find the message type for 0VENDOR_ATTR in ROOSGEN table. This will be useful in looking at table BDCP2.
    Please let me know if there are any questions.
    Thanks
    Amit

Maybe you are looking for