Kontakt

Ansicht
Dokumentation

ABENSHM_AREA_INSTANCE_STATE - SHM AREA INSTANCE STATE

ABENSHM_AREA_INSTANCE_STATE - SHM AREA INSTANCE STATE

ABAP Short Reference   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.
SAP E-Book

- States of Area Instance Versions

Area instance versions can have the following states.

  • "Under Construction"
An area instance version that has a change lock is being built. Change locks automatically create a version under construction.
  • "Active"
The area instance version whose construction or update was last released using the method DETACH_COMMIT (and a database commit in the case of transactional areas) is active. All read locks are automatically set to the currently active version.
  • "Obsolete"
If the construction of a new version is completed during read access on the currently active version, the new version becomes active and the version that was previously active becomes obsolete. The read locks on the obsolete version remain until the read is completed, but new read locks for the area instance, however, are always set on the active version.
  • "Expired"
Once the last read lock on an obsolete version is removed, the version expires, that is, 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 that exists in one of the states listed above. In an area with versioning, there can be multiple versions of different states in an area instance at the same time:

  • Since there can be a maximum of one change lock on an area instance, there is a maximum of one version under construction 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, there can be multiple obsolete versions can exist in parallel.

Note

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

Example

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

  • One active version and one version under construction
  • One active version and one obsolete version
  • One version under construction and one obsolete version






SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 2899 Date: 20240424 Time: 174800     sap01-206 ( 49 ms )