Skip to content

ABAP Keyword Documentation →  ABAP − Reference →  Creating Objects and Values →  Shared Objects →  Shared Objects - Area Instance Versions 

Shared Objects - States of Area Instance Versions

Area instance versions can have the following states.

  • "Building"
    • An area instance version that has a change lock is being built. Change locks create a building version automatically.
  • "Active"
    • The area instance version whose build or update was last released using the method DETACH_COMMIT (and a database commit in the case of transactional areas) is active. All shared locks are set automatically to the current active version.
  • "Obsolete"
    • If a new version becomes complete when reads are performed on the currently active version of the build, the new version becomes active and the version that was previously active becomes obsolete. The shared locks on the obsolete version remain until the read is complete. Any new shared locks for the area instance, however, are always set on the active version.
  • "Expired"
    • Once the last shared lock on an obsolete version is removed, the version expires (it is deleted by the garbage collector). No locks can be set on expired versions and they are ignored when the version number is determined.

    In an area without area instance versioning, there is always only one area instance version and this version exists in one of the states mentioned. In an area with versioning, there can be multiple states in an area instance at the same time:

    • There can be a maximum of one change lock on an area instance, which means there is a maximum of one building version for each area instance at any given time.
    • There is a maximum of one active version for each area instance.
    • Depending on the maximum number of versions, multiple obsolete versions can exist in parallel.

    Other versions: 7.31 | 7.40 | 7.54


    Note

    If a large number of obsolete area instance versions in an area still have shared locks, but there is an updated version in an active state, this can indicate a problem with the use of shared objects.


    Example

    In a simple case with a maximum of two versions, the following maximums apply:

    • One active version and one building version
    • One active version and one obsolete version
    • One building version and one obsolete version