About datasource delta upload

[Former Member]

Dear Expert,

since there are 100 data records were wrong in datasource, I want to correct these incorrect data, so, I delete some requests which contains these 100 data records from datasource.

I re-run infopackage upload data from source system to PSA and then re-run DTP to upload these data from PSA to datasource by delta upload.

I want to know the delta upload mechanism:

1. data flow: source system -> PSA

which delta update mode should be chose? is full update or delta update or initialize delta process?

2. data flow: PSA -> datasource

which extraction mode should be chose? is full or delta mode?

Please tell me the reason of your choice, many thanks!

[Former Member]

Hi,

1)From source system -> PSA

IF the delta ran succesfully (request in green) the all the records after arriving to Bw, will not be available in Delta queue.

If you want all the data from the source, run fullload.

Else, You need to run the full load based on filtrs to get the required records,

2)From PSA -> data target.

you can run delta (what ever may be the update mode in infopackage).

If you run delta it will update only the requests that are not updated from the PSA.

In our case, I suggest to Run repair full load rather than delete and re-load the data.

Cheers,

Srinath.

[Former Member]

Hi Srinath,

1)From source system -> PSA

for delta mode, what is the program logic to select data? in other words, is BW program select all data records from database and then compare it with PSA to find the difference?

2) you suggest to Run repair full load rather than delete and re-load the data.

because in my scenario, there are some fields wasn't overwrite in transformation, if we chose full upload , some fields values will be incorrect.

[Former Member]

Hi,

1)we have the concept of delta initialization to set delta pointer in source syste.

it goes like this

initially we will run full load and then run init delta.

once the delta init is succesful,all the new recorde will be collected in the delta queue.

so when you run delta,only the new recordsm are updated to the PSa and if we fetch the records succesfully from source system, the delta queue will be cleared.

So new records will be ariving in to the queue from then on.

2)Even though the key figures are not in overwrite mode, Repairfull request will do the needful here.

It is entirely different from full load.

Repair ful request brings the full load data and then compares this ddata with that of the target.

any discripencies will get replaced(its basically repairing the dat in target).

Cheers,

Srinath.

[Former Member]

Srinath,

thank you in advance, but still understood, so, I want ask you more.

1) you said "new record will be collected in the delta queue." I want to know the new record how to fetch from database, compare all data with PSA?

2) Repair full request. how to do it? how to create this kind of DTP, please give more details.

[dennis_scoville4]

How about running a Full Repair InfoPackage with the keys of the records that you had to correct and then load these, via delta DTP to the target InfoProvider? That should get you only those records that you need into the PSA and into the target.

[Former Member]

Hi,

1)we cannot get the new records in to the delta queue.

IT is systenmm which is doing this and for acheiving this, cmparision will not work out.

There is a queue in source system called delta queue where in all the new records that got generated are collected.

once we run delta and fetch the records, the queue will be cleared (zero records in the queue again)

so any records comming after that will get collected in the delta queue.

2)If you want to do a repair full request, create an infopackage to do a full load and then go to the first menu option SCHEDULER in the menu bar and click on Repair full request and check the checkbox saying "Indicate request as repair request".

hope this helps.

Cheers,

Srinath.

[Former Member]

Srinath,

Can you tell me how does the new data records generated in delta queue? for e.g. I deleted 100 records from datasource and PSA. how many records should be got in delta queue?

How does the delta queue collect data in ECC? (use time-stamp?)

[Former Member]

let me explain you with an example.

cosider the scenario

Day 1 there are 100 records (total no of records in source system,nothing to do with delta here)in source system and every day 10 records add up in the system

So, Day2 total no of records will be 110

Let us suppose i am running full load here, so i will get the110 records in to the PSA.

After that i run ann init. sodelta pointer will be set after 110 records.

so what all the records that come after initializing delta (after this 110) will be collected in RSA7(delta queue)

so day3 10 records will be added , now total records in source is 120 and in delta queue is 10(records that came after initializing.

when we run the delta, these 10 records from the delta queue will be fetched in to PSA. so total records in BI is also 110(full load)+10(deltaload).

After running this delta and records are fetched in to BI, delta queue will be cleared in source system

so day4 10 records will be added, so total records will be 130 and in delta queue it will be 10(previous 10 got erased after loading delta)

So when you run delta now, oonly the latest 10 records will be fetched an delta queue will be cleared.

As explained ,Delta doesnt work on comparision,so it doesnt load the deleted records in to delta queue.

so you need to run full load with selection conition to bring back that data

Lt me know if this is helpful

Regards,

Srinath

Edited by: Srinath Singamsetti on Aug 4, 2009 1:47 AM

[Former Member]

Srinath,

great thanks! your explanation is very clear! I understand it now.

[Former Member]

Hi,

So, if your question is answered please mark it as answered.

Cheers,

Srinath.