What are V3 updates?

[Former Member]

Hi,

SAP Note 447925 (Known problems with Support Packages in Basis 6.20) has a section about V3 Update Entries - what are these and how do I know if they have been processed?

Thanks.

Richard

[Peter_Inotai]

Check OSS note 552300 (FAQ: Update) for details.

Incho

<i>[2] Question: What is a collective run?

Unlike V1 and V2 updates, V3 updates (or collective runs) are not

started directly - instead the update is performed via a background job

(report RSM13005).In this case, the update requests are not updated

separately, but rather all modules of the same category are updated in a

single database transaction.Since the database can therefore operate

with far fewer database transactions, system performance is dramatically

improved.Background jobs should be started in the Customizing or the

corresponding applications that use the V3 update.

[3] Question: What is the difference between V1, V2 and V3 (collective

run) modules?

The type of update module for a function module is defined by the

developer and then saved as an attribute of the function module.The

attributes are defined as follows:

V1: The update should be performed soon.The update record is protected

by R/3 locks.The update is critical for the operational consistency of

the system.

V2: The update does not have to be performed soon.The update is not

protected by locks.The update modules do not contain "vital" data.

V3: As V2, however, you start the updates using the RSM13005 report.

Bear in mind that the V3 update offers an advantage with regard to speed

when considering its disadvantages.Report RSM13005 also eliminates some

of the disadvantages of the V3 update.

</i>

[Former Member]

Hi,

V3 is introduced in 470 or 460 I believe. Recently, we have gone live in 470 and we had lots of V2 update task failures of standard SIS structure (db lock failure). Based on research I found replacing the V2 with V3 (timed async updates) will help resolve this issue and no more abends after changing the V2 with V3.

Basically, it works like V2 except you need to run a batch job (I do not remember the SAP program name) to collectively process all the pending V3 updates. Tremendous performance improvement after changing to V3.

Hope this helps.

Senthil