Difference between Queued Delta vs Unserialized V3 update

Question

Dear Experts,
I am using 2LIS_02_ITM datasource.
PO is created using a program.
The next step in the program, it can change a field in the PO depending on logic, using a abap command 'update'.
Sometimes, this change is not captured in the delta queue, it seems.
why i say this is the PO shows the field value but BI delta load does not.
It is using Queued Delta now.
I am wondering would changing to Unserialised V3 update help solve the problem since when documents are posted it writes to update table and from there it is processed to delta queue using collection run.
What is the difference between writing to the Extraction Queue compared to writing to Update table? Will using the update table mean abap command 'update' changes to a PO document will be captured ?
regards
Pascal

Answer 1

Hi Pascal ,
The basic difference between these two is how the delta moves from R/3 to BW side .
When we do any transaction in R/3, first the data goes into a Temporary table called V1 Update and from here data moves to Final table (Application)say VBPA,VBRK etc. this is called V2 Update.
After this we have queued delta or Unserialized V3 update at between R/3 and BW side .
1. Queued Delta
At V1 update data goes to  "Extraction Queue" (irrespective of V2 happen or not).Then when we run a "Extraction Run" program it pulls the data from  Extraction Queue  and sends it to  DELTA Queue  table (called V3 Update) from where it is transported to BW when a delta request is generated.
So if something is saved to application table, also get saved to Extraction Queue ( this is difference with direct delta) and you have to schedule a V3 job to move the data to the delta queue periodically .
2. Unserialized V3 Update
In this case when data is generated V1 update  takes place and data moves to another table known "Update Table" but only after V2 takes palce. So it waits for V2 update to happen and does not miss any record.After that from "Update Table" data goes to Delta Queue when update collection Run is executed and then  it goes to BW when Delta upload Request is generated.
The difference here is the sequence of document data in the BW delta queue that may be different from posting sequence of data so it is good when sequence of data does not matter due to the design of the data targets in BW.
ex: Inventory Management.
Hope this will throw some light on the concept you want to understand.
Regards,
Jaya