Unserrialized delta for non cumulative keyfigure

Question

Hello Friends ,
Why the update mode is unserillized delta at the time of non cumulative KF extraction ?
Regards,

Answer 1

Hi..
As per my knowledge there is no such rule........
There are three Update modes :
V1 - Synchronous update{DIRECT DELTA}
V2 - Asynchronous update{QUEUED DELTA}
V3 - Batch asynchronous update{UNSERIALIZED V3 UPDATE}
V1 >> Synchronous Update Method – When we use this type of update method after the first successfully entered the signal comes back as the first record is entered successfully. Then only the next record will enters into the file. If the first record fails, then there is no further process. Even though the first record enters into the file successfully, the 2nd record will wait until the signal comes back. So here a performance is decreases. One more point is that there is no background process for V1 update method.
V2 >> Asynchronous Update Method –When we use this type of method there no need to the signal comes back to enter the second record. It automatically the 2nd record will enters into the file. If there is any in the first record, it will not wait until it is corrected; the 2nd record enters into the file. Here the first drawback is over comes here. But the 2nd one is there i.e. here also there no background process.
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.
Check this link :
/people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
Hope this helps you.....
Regards,
Debjani.......