Skip to Content
author's profile photo Former Member
Former Member

What are V3 updates?


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?



Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • Posted on May 10, 2004 at 08:33 AM

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


    <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.


    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on May 09, 2004 at 04:06 PM


    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.


    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.