Reloading delta requests

[Former Member]

Hello,

We have a delta load from R/3 -> ODS1 -> ODS2 -> ODS3 -> Cube in an BW 3.5 system.

In the update rules between ODS2 and ODS3 some additional key figures are added from masterdata using ABAP. Because of an error the required masterdata was not available for at least one load and we need to reload those data to get those additional key figures.

I know I can easily fix the issue by deleting all data in ODS 3 and the cube and run a new init load because the number of loads and records so far is quite small. I want however to understand how to do it without deleting all data. (What if the number of records were really huge?)

Can reconstruction be used? Is it possible to delete only a single load and reload it? Do I have to delete all subsequent requests as well or can this be avoided? Do we have to reconstruct all the way from R/3 or can we reconstruct from ODS2 only (which of course would be preferable)?

Regards,

Christoffer Owe

[Former Member]

Hi,

Is the update rule for key figures from ODS2-ODS3 all set to overwrite? If it's so, then I think you can perform a full load from ODS2->ODS3, then let ODS3 takes care of the changes and subsequent update into infocube.

Thanks.

[former_member345199]

Hi,

This blog will help you.

Repair bad data and subsequent data targets with delta update

/people/aaron.wang3/blog/2007/04/11/repair-bad-data-and-subsequent-data-targets-with-delta-update

Hope this helps.

Thanks,

JituK

[Former Member]

Correction: have to delete starting from the cube back.

[Former Member]

There is only one question: what is your setting in the InfoPackage? Should always use one of the “with PSA” loads, option 1 to 3 in the “Processing” tab. Then you can delete all requests starting from ODS3 back. We sometimes call this “to reverse” the requests. Yes, you have to delete also all subsequent requests. May get very complex if other updates to same ODSs. ODS is a delta generator. For the delta in the change log to be correct you have to reverse all requests and get to that state in time where the error occurred and continue from that point. Now you can reconstruct in the correct sequence in time.