SAP ABAP Data Element VERSKORRNO (Version Management: Version Request Number)

Hierarchy

☛ SAP_BASIS (Software Component) SAP Basis Component
   ⤷ BC-CTS-ORG (Application Component) Transport Organizer
     ⤷ SVRS (Package) Basis Versions

Basic Data

Data Element	VERSKORRNO
Short Description	Version Management: Version Request Number

Data Type

Category of Dictionary Type	D	Domain
Type of Object Referenced		No Information
Domain / Name of Reference Type	TRKORR
Data Type	CHAR	Character String
Length	20
Decimal Places	0
Output Length	20
Value Table	E070

Further Characteristics

Search Help: Name
Search Help: Parameters
Parameter ID
Default Component name
Change document	☐
No Input History	☐
Basic direction is set to LTR	☐
No BIDI Filtering	☐

Field Label

	Length	Field Label
Short	10	Request
Medium	15	Request no.
Long	20	Request number
Heading	10	Req. no.

Documentation

Definition

Request number for the version

Use

You can change objects only when they are in requests. When you release an object, its current data is saved as a version. A version of an object is also created when it is imported.

If there is a request for a version in the version database, the version contains the object data at the time when the request was released. If it is an imported request, the version contains the object data after the request was imported.

If there is a request for the active or revised version, then the object is being changed in this request, or the object was imported in this request.

In some exceptions, there are no requests:

1. UPGRADE<rel>: In these requests, versions are created of objects that have been delivered in the repository switch (as of Release 3.0). These requests do not actually exist since the entire repository is switched simultaneously, and not by request.
2. LOCAL: Local objects, which are not managed in requests, have LOCAL entered in this field instead of a request number.

History

Last changed by/on	SAP	19990505
SAP Release Created in