Hi Experts...Im new to SAP BW & BI...I have few doubts how u guys can clear

Question

HI Experts,
Can anyone explain how these updates works..
FULL Update,
Delta Update,
init update,
initialize with data transfer,
intialize without data transfer.
V1 Update
V2 Update
V3 Update.
Thanks
Manu

Answer 1

Hi...
Full Update >> Loads all the data from the source system..every time you run a Full upload it will pick old as well as new changed records from the source system.In this case generally number of records is huge and IP takes a long time to get completed...
In this case each time we need to fill the set up table in the source system..
Delta load >> Delta loads only brings the changed records from the source system.To initialise a delta load:
1) first run full load
2) then run init IP without datatransfer
3) run delta load...
In this no need to fill the set up table repeatedly..
Just fill it once first time when you are executing full load..after that when you will run init IP...delta queue will get generated..
It saves time...
One thing I want to mention here...
Suppose any delta loads fails...then it is must to make the toatal staus in the IP monitor manually red before deleting the request from the target....to set back the init flag...otherwise it will not allow repeat delta and data will be lost
In full load if you no need to make the Total Status manually red.
Init update is to set the Init flag...
Suppose somehow delta mechanism got corrupted...
In this situation we have to delete the init flag >> If last failed delta load picks some records...then we will do delta with data transfer...if last failed delta IP picks 0 records...then we will do delta without data transfer...
After running the init IP...we will run Delta IP...
V1 Update >> Synchronous update >> Taking an example -
If you create/change a purchase order (me21n/me22n), when you press 'SAVE' and see a success message (PO.... changed..), the update to underlying tables EKKO/EKPO has happened (before you saw the message). This update was executed in the V1 work process.
V2 Update >> Asynchronous update >> There are some statistics collecting tables in the system which can capture data for reporting. For example, LIS table S012 stores purchasing data (it is the same data as EKKO/EKPO stored redundantly, but in a different structure to optimize reporting). Now, these tables are updated with the transaction you just posted, in a V2 process. Depending on system load, this may happen a few seconds later (after you saw the success message).
V3 Update >> Batch asynchronous update >> V3 is specifically for BW extraction. The update LUW for these is sent to V3 but is not executed immediately. You have to schedule a job (eg in LBWE definitions) to process these. This is again to optimize performance.
V2 and V3 are separated from V1 as these are not as realtime critical (updating statistical data). If all these updates were put together in one LUW, system performance (concurrency, locking etc) would be impacted.
Serialized V3 update is called after V2 has happened (this is how the code running these updates is written) so if you have both V2 and V3 updates from a txn, if V2 fails or is waiting, V3 will not happen yet.
Kindly assign me some points if this helps you...
Regards,
Debjani...
Edited by: Debjani  Mukherjee on Sep 5, 2008 9:58 AM