.png)
Direct Delta
New records are directly taken to delta queue... delta queue can be viewed using Tcode RSA7
this mode is the fastest method... but delta queue have a limitation of 10000 LUWs... so this method can be used only when number of records are low.. otherwise we have a chance of losing data..
Unserialized V3 Update
In this mode, New data is taken to update queue first, Update queue have no limitation for LUWs..
We don't have a sorting done in Update queue.. there is no priority... so this mode is selected when we dont want data in a sorted manner... mainly used in Inventory...
Moving data from update queue to delta queue is done using a process called V3 collective run
Can see update queue using Tcode SM13
Queued Delta
The extraction data from the concerned application is collected in an Extraction Queue. Then the data will be transferred to Delta queue, in a similar manner to the V3 update, with an update Collections run.
This process is especially recommended for customers with a high occurrence of
documents.
By collecting new document data during the delta-init request, the downtime in the initialization
process can be reduced for the reconstruction run (filling of the setup tables).
Collective run clearly performs better than the serialized V3. Especially the critical aspect of multiple
languages does not apply here.
In contrast to the V3 collective run, a definite end for the collective run is measurable, and a
subsequent process can be scheduled. After the collective run for an application has ended, an
event (&MCEX_11,...) is automatically triggered which, if defined, can be used at the start of the
subsequent job.
Extraction is independent of success of the V2 update.
Tcode LBWE
Unserialized V3 Update
Please note that update method is not for individual data sources... it is applicable for whole Application component..
when You fill setup tables.. every setup tables under that application component will be filled..
when new data is posted, it will be reflected in SM13.. as we have chosen Unserialized V3 update method...
when we have new posting,, we can see it here..
Now to move data from SM13 (Update queue) to Delta queue.. we have to do a V3 collective run...
Queued Delta
New data can be viewed from LBWQ (extractor queue)
Now move data from LBWQ to Delta queue...
Hi...
ReplyDeletei have some doubt on update mode in LO
1.what do u mean by Filling Set table? and what is the purpose behind this.
2.What is difference b/w ECC extraction and LO extraction or ECC data source and LO data source?
Plz give some live example for LO?
Thanks
Manish..
Set table is an intermediate table used between LO Datasources and BW...
DeleteSet table is used only in Full and INIT... soon after INIT , delta queue is created.. after that DELTA is pulled directly from Delta queue.
Hi Mohamed,
ReplyDeleteYour documents are very good .Can u explain clearly about the V!,V2,V3 updates.
Document update is where the transaction (documents) are updated in the application tables.
DeleteStatistical update is the update of statistics for the transaction – like LIS or extractors for BW.
V1 – synchronous update. If the update is set to V1, then all tables are update and if any one fails, all are rolled back. Done for all transaction plus critical statistics .
V2 – asynchronous update – transactions are updated and statistical updates are done when the processesor has free resources. If the statistical update fails, the transaction would have still gone through and these failures have to be addressed separately.
V3 – batch update – statistics are updated using a batch (periodic) job like every hour or end of the day. Failure behaviour is same as V2 updates.
Statistical update is also used as to describe the initial setup of the statistical tables for LO/LIS. When old transactions are updated in LO/LIS as a one time exercise, then it is called a statistical update also. Once these tables are upto date will all transactions, then every transaction is updated in them using V1, V2 or V3.
V2 Plays any role any of the update mode??
ReplyDelete