Hierarchy
PI_BASIS (Software Component) Basis Plug-In⤷
CA (Application Component) Cross-Application Components⤷
POR4 (Package) Drag&Relate (Workplace Plug-in) with Rel. 4.0
Basic Data
| Data Element | DR_LOGVERS |
| Short Description | Metadata Version |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | DR_LOGVERS | |
| Data Type | CHAR | Character String |
| Length | 8 | |
| Decimal Places | 0 | |
| Output Length | 8 | |
| Value Table |
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 | Version |
| Medium | 15 | Version |
| Long | 20 | Metadata Version |
| Heading | 0 |
Documentation
Definition
Different versions of the metadata are maintained. Metadata delivered by SAP (or created in SAP mode) are available in the delivery version.
The Unifier and the runtime always use the active version, that is the metadata must be activated in this case.
If metadata is changed, an inactive version is created when the data is stored. When this data is activated, it becomes the active version. The inactive data can be deleted as long as it has not been activated. Any changes made to the data might be lost.
There is also a transport version that must be activated after the import (it might be activated automatically, see Transport Settings).
Depending on the transport mode and the existing versions, there is a default version that can be edited. The other versions cannot be edited.
If there is no editable version, but there are version(s) that cannot be edited, you can create an editable version using the 'Aktivierate in Expert Mode' function.
History
| Last changed by/on | SAP | 20080415 |
| SAP Release Created in |
