aaron.

wang3: Repair bad data and

subsequent data targets with delta update
Posted by Aaron Wang Apr 11, 2007
Initialization / Delta update is what we do everyday and the update method for most data targets.Delta
mechanism ensures the consistency of transactional data. So if some data is wrong in the early stage
of data flow, we have to not only correct itself but also correct the related records in subsequent data
targets. Unfortunately such kind of data can't be avoided in daily extraction. In some situations the
data to ODS is correct but reports error while loading from ODS to Cubes. Here is one example: Some
FI documents transferred in R/3 with LSMW's background mode and one of the line items 'Negative
posting signal' was inputted with 'x' while the right one should be 'X'. This line time stays cool in my
ODS Z1CCWO01 but encounters error while loaded into several Cubes during process chain's running.

Request
25344 is bad It's easy to modify the data in PSA of ODS and then re-construct it.But please don't do that
immediately - if we simply delete the delta requests in Cubes afterwards and then re-load delta again, it won't
reach your expectation because the delta is broken! If we want to fix both data in ODS / Cubes and keep the
right delta, just take the following steps: 1, Set the request's QM status in all your data targets(in my case,4
cubes and 1 ODS)to red and then delete all of them. This will cause a repeat delta load in the following steps.

Generated by Jive on 2015-04-17+02:00

1

aaron.wang3: Repair bad data and subsequent data targets with delta update

2, Open table RSDMDELTA via SE16.Here stores the successful

DataMarted request. Delete the request contains the bad data (25344 in my

case)
3, Open table RSBODSLOGSTATE and change fields 'Max. delta slice that was extracted by all receivers'
and 'Max. delta slice extracted until now' to the latest right request number.( 25344 to 24860 in my

case)
4,Since the Data Mart Status of the bad request has been cleared, we can thus delete the request and
modify data in PSA. But still mark the QM status in 'Requests' tab to red (not in Monitor). 5, Modify data in

Generated by Jive on 2015-04-17+02:00

2

aaron.wang3: Repair bad data and subsequent data targets with delta update

PSA.
bad request (25344) in ODS and activate

6, Re-construct

it.
7, Load the delta package in Data Mart from ODS to subsequent data targets. A warning of 'repeat delta'

Generated by Jive on 2015-04-17+02:00

3

aaron.wang3: Repair bad data and subsequent data targets with delta update

will populate and choose 'request again'. The above steps could ensure right delta after PSA change and
reconstruction for all data targets in the data flow. It's somewhat complicated but I still didn't find any better
solution instead of redo the whole initialization (which may contain several millions of records and affect all the
data targets!) Regards, Aaron Wang 3060 Views

sagar sapbi
Jul 10, 2009 3:38 AM
Great and good.
thanks for your contribution , now i clearly undertstood about repeat delta
Aaron Wang in response to Peri Subrahmanya Sarma on page 4
Sep 25, 2007 10:57 PM
Hi Sarma,
Just delete the particular request ( bad request ) . Don't touch the former good requests.Good luck.
Regards,
Aaron
Peri Subrahmanya Sarma
Sep 25, 2007 8:43 PM
Thanks for blog. I had a doubt in step1. Shall we delete all the requests in the data targets or only on the
perticular day request.
Thanks,
PSSarma.

Kalyan Dittakavi
Aug 1, 2007 1:18 PM
Keep up the great work...
I agree with you in terms of complexity but its the most robust way to keep delta pointers in sync
kalyan
Marilyn Pratt in response to Mukund Umalkar on page 4
Apr 12, 2007 6:42 AM
Really glad that Mukund found this content helpful, that Aaron was able to clarify and that Aaron was so
persistant and enthusiastic around becoming a "blogger from China".
Keep up the enthusiasm as you see it appreciated. And its wonderful to have such great international
interaction.
Mukund Umalkar in response to Aaron Wang on page 4
Apr 12, 2007 2:55 AM
Hey Aaron,
Thanks for your reply ! So, step1 just deletes the requests in data targets.
Step4 deletes the request (with error) in the ods so that we can do re-load it again.
Thanks a ton. Found this post very useful !!! Cheers !

Generated by Jive on 2015-04-17+02:00

4

aaron.wang3: Repair bad data and subsequent data targets with delta update

Aaron Wang in response to Mukund Umalkar on page 5

Apr 12, 2007 1:39 AM
Hi Mukund,
Thanks for your doubt! Cuz I found maybe I didn't speak very cleary.
In step 1, I did set the QM status and delete the requests, but this is NOT the bad request with bad data in
ODS (number 25344), but some requests in data targets.
In step 4, I deleted the bad request 25344 in ODS and re-construct afterwards.
Hope it's clear this time.
Regards,
Aaron
Mukund Umalkar
Apr 12, 2007 1:27 AM
hey ! great post ! loved it. very useful. i have a doubt though... in step 4.
in step 1, you are setting the QM status of the error request 25344 as red and also deleting it...
however, in step 4, you again ask to delete the request (the one with error) after we mark its QM status as
RED.
how is that ? can you please explain ? am i not understanding something wrong ? Hoping to hear from you.
Cheers,
Mukund.

Generated by Jive on 2015-04-17+02:00

5