V1, V2, V3 Update: 2 questions: Getting clarification on Roberto's Blog

Question

Hi,
In a blog by Roberto, /people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146, I have 2 questions on two QUOTES from this article:
1. On quote A:
Now, from point #3, it states that if successfully processed by V2; So if it has successfully been processed by V2, why would you then want to process it again with V3?
Or, is it suggesting that V2 updates the tables in R3 automatically, but stays in those tables utill V3 is scheduled in LBWE?
2. On quote B:
Also, in LBWE, I found the options Direct Delta, Queued Delta, Unserialized V3 update. From the article, there was no mention of Direct Delta, Queued Delta. When are they used instead of the V3?
Can you help me understand what Quote B was all about? I got lost.
Can you help me follow how the delivery status example in this quote is implemented regarding the ODS?
(LBWE talks about Unserialized but Roberto spoke about Serialized was that  a mistake?)
QUOTE A
"Normally in R/3 there are three types of update available:
1.Synchronous update (V1 update)
Statistics update is carried out at the same time (synchronous) as the document update (in the application tables).
2. Asynchronous update (V2 update)
Document update and the statistics update take place in different tasks.
So, V1 and V2 updates donu2019t require any scheduling activity.
3. Collective update (V3 update)
As for the previous point (V2), document update is managed in a separate moment from the statistics update one, but, unlike the V2 update, the V3 collective update must be scheduled as a job (via LBWE).
Remember that the V3 update only processes the update data that is successfully processed with the V2 update. "
Quote B
"..But since updating in ODS objects is permitted in the logistics extraction for almost all DataSources, we have to consider any effects that can derive from the u2018overwriteu2019 update mode (specific of the ODS object).
For example, the consistent storage of a status field (e.g. delivery status) in ODS objects can only be ensured only with a right (serialized) delta sequence: if the record with u2018open deliveryu2019 status (created as first record in R/3) arrives later than the record with u2018closed deliveryu2019 one (created as second one in R/3), we would have a false representation of the reality.
Since the normal existing update methods actually does not recognize the serialized processing of update data, the Serialized V3 Update function was created (also thanks to subsequent several corrections in SAP Basis) in order to be able to serialize step A..."

Answer 1

Hi Amanda,
Would appreciate if you could update the article link in the thread as this will help others.
Regards,
Nitin S.