Hierarchy
⤷
⤷
Basic Data
| Data Element | RMSAE_VRS_INS |
| Short Description | Insertion of Versions is Allowed |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | RMSAD_FLG | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| 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 | Ins. Allwd |
| Medium | 20 | Insertion Allowed |
| Long | 40 | Insertion of Versions Allowed |
| Heading | 40 | Insertion of Versions Allowed |
Documentation
Definition
Enables versions to be inserted in a version chain.
Use
If you do not set this indicator, the version counter determines the order in the version chain. This means that you cannot insert further versions between versions 1 and 2 in a version chain, for example.
If this indicator is set, the valid-from date of the individual versions determines the order in the version chain. You can insert versions with a higher version number in the version chain. The rule that consecutive versions are sorted by their valid-from date, and not by their version number, still applies however, even if the indicator is set.
Dependencies
Example
By setting this indicator, you can create the following version chain:
Version Valid-from date
EXAMPLE.001 1/1/2002
EXAMPLE.003 1/1/2003
EXAMPLE.002 1/1/2004
This version chain is not possible if you do not set this indicator. You can, however, create the following version chain:
Version Valid-from date
EXAMPLE.001 1/1/2002
EXAMPLE.002 1/1/2003
EXAMPLE.003 1/1/2004
History
| Last changed by/on | SAP | 20031212 |
| SAP Release Created in | 210 |