diff between init with data transfer and repair full request

[Former Member]

hi,

i have observed that even in the new flow we are doing init without data transfer and then repair full request

if i do init with data transfer also i can achieve the same?

i want to know why we need to do this ,do we have any advantage of doing init without transfer and repair full request?

please suggest me

[ram_pandey]

Hi Venkat,

A repair full request is loaded in cases where you get erroneous records or where there are missing records which you want to load. In such cases, a repair full request for the selective records can be loaded and is the most efficient way to correct the data, since you won't be required to load the entire data once again. Also you acheive the desired result without disturbing the delta. (You are not required to do an init w/o data transfer after a repair full, people just do it a a precaution)

However, repair full requests should only be loaded to infoproviders with update mode 'overwrite'. Otherwise, if the InfoProvider, its very probable that you might double the value of the key-figures due to rows being added twice - in case of an InfoProvider with update mode 'Additive'. So, if your InfoProvider is additive, you will need to delete the entire data and do an 'init with data transfer' to avoid corrupting the data. (Note: you can do a repair full request for an additive infoprovider in case of lost records or if you can delete erroneous records with selective deletion.But you have to be careful with the selections lest you inadvertently load other records than required and corrupt the data)

[former_member184494]

Venkat,

Please search the forums before posting... this is an oft discussed topic and the questions you have asked have been answered before.....

Arun

[Former Member]

Hi Venkat,

You can achieve the same as you mentioned with Init data with transfer.

We used to do the init without data transfer just to fix a time stamp or to set up the queue in RSA7.

We usually use this kinda procedure in LO Cockpit. Where in the Repair full request will get the data from Set up tables ( History Data) and Detla from Delta queus.

Since history data will take more time we will set up the delta queue in RSA7 of R3 and do the repair full request to get history data.Mean time you can have the Delta records in the queue and extract the same once repair full request is completed.

More over its just to save the down time of the R3 system.means once you fill the set up table you can do init without data transfer to set up the queue and you can release the system for users and start extracting the data to BW without disturbing the business.

Hope this helps you,

Thanks,

R@ngzz