This blog doesn't contain any copied information or copyright content from other sites. Every topic i presented in this blog is authored myself. Every time i tried to help the sapients to understand the concept in an easier way. Thats it. Have a Grt Day!



V3 - batch asynchronous update:
• v3 is defined as un-serialized is collective update / synchronous with background schedule or batch synchronous update, uses delta queue technology and the nature of update is never automatic, which runs in background uses report rsm13005.
• the process can be done at any time after v1, v2 updates. I.e. V3 uses v1 or v2 +v3 update, reads data from documents & uses delta queue collective run call and writes to application tables.
• v3 can be scheduled at any time, with a mandatory step of locking users to prevent simultaneous updates.

Deep Analysis: Unserialized v3 update

Data extracted from application tables is written to update tables using un-serialized v3 update mode. By using collective update the so extracted data is processed. The important point to consider here is that the data is read without a sequence from update tables and are transferred to BW delta queue. Un serialized update, which is run after v1 & v2 doesn’t guarantee serialization of the document data posted to delta queue. This method is not suggestible as the entries in the delta queue are not equal to the updates that made to application. This method v3 results erroneous data, when data from DataSource is updated to DSO in overwrite mode, so the previous data is over written by the last update. But this v3 is suggestible when updating data to o d s or InfoCube. V3 runs and process the data after v2 with which the data is processed.

Suitability : suitable for customers with high amount of documents
Serialization by document : no serialization as it’s a statistical update, which is run after v1 & v2 but the un serialized v3 doesn’t guarantee serialization of the document data.
Extraction : collective
Down time : not efficient
Implementation : less


Suitability : not suggested if documents subjected to large changes with tracking changes
Post a Comment
There was an error in this gadget