Skip to Content
author's profile photo Former Member
Former Member

Delta load form one DSO to another DSO

Hello,

I have one requirement where I need to delta load form one DSO (ZDSO_01) to another DSO (ZDSO_02) in follow conditions:

the DSO (ZDSO_01) is refresh an hourly basis and DSO (ZDSO_02) is refresh an daily basis.

Delete all data from ZDSO_02 every day and load with only delta records form ZDSO_01. I am wondering how can I achieve that goal.

Any tips and suggestions??

Thanks in advance.

Regards,

Md

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Feb 01, 2010 at 09:45 PM

    Hi.

    I would go for loading the delta to 02 and then read the change log of that one with a custom program after each delta load, keeping track of when the last read was OR reading the last delta req to enter 02 from some monitor table (rsreqdone, rsseldone ??). and store this in another DSO.

    Or maybe you can do it straight off 01...?

    regards

    Jacob

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Feb 01, 2010 at 10:04 PM

    MD,

    Is there any kind of characteristic field you can use as an indicator to show the new records being loaded into DSO_1 as being the new ones? Typical indicators being a Timestamp or Date field being entered.

    If not, in cases like that, we typically do several things.

    First, the data being loaded into DSO_1:

    First thing we would do is add in a characteristic field to the DSO... an info-object of type char, length of 1. In the Update Rules, we would make this new char a constant value. We usually use the letter X as our indicator. What this will do is mark all new Delta records going into DSO_1 with your value of X.

    Now that new delta records being loaded into DSO_1 have an X marked, we can create an Info-Package for DSO_2 that does a FULL LOAD Repair Request... and in the selection area, add in the X value into your new field selection. This will ensure that your only loading records that came over into DSO_1 on the last Delta load. Once those records are loaded into DSO_2, you will then need to execute a stand-alone ABAP program that goes through the DSO_1 table, and CLEARS ALL values in your new Characteristic field. This deletes all the X's (be careful you don't delete the records), to help ensure that you won't be re-loading the same records into DSO_2. When the next hour comes along, the process is repeated.. delete all data from DSO_2, execute your Delta load into DSO_1... the new records going into DSO_1 get flagged with an X... the load into the second level will grab ONLY those records, and then your abap program clears out the X's from all records in DSO_1 table to make sure your ready for the next hour.

    Doing this ensures that you will always retain ALL of your data in DSO_1, while clearing out, then uploading only the records that are new/changed from the previous hour into DSO_2

    We do this quite often... it's like creating your own "Delta" indicator and comes in handy quite a bit.

    Hope this helps.

    Edited by: Craig Walters on Feb 1, 2010 4:05 PM

    Edited by: Craig Walters on Feb 1, 2010 4:07 PM

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi.

      Depending on what sort of load is going into 01, you can flag the records and delete the flag again - it the updatemode of the source doesn't allow it (full with overwrite), you will need to load to one more DSO in between to get the delta isolated.

      In that scenario, you might as well read from the change log what came in from 01 and got activated since you last read the log. Like that you would only have to keep track of when you last read it and not need to clear a flag...

      regards

      Jacob

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.