Hierarchy
EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials⤷
PLM-RM (Application Component) Recipe Management⤷
RMSATLVRS (Package) RMS-ATL: Versioning / Sequencing
Basic Data
| Data Element | RMSAE_FLG_VRS |
| Short Description | Create a Version |
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 | Version |
| Medium | 15 | Version |
| Long | 20 | Version |
| Heading | 13 | Version |
Documentation
Definition
Specifies that a new version is created.
Use
Dependencies
The version category of the object type determines whether you are allowed to create versions and drafts for an object. When you create an object, the system automatically adds the version or draft number by incrementing the object's highest existing version or draft number. The full object key then contains the object key plus the version or draft number separated by a separator.
You define the version category, separator, and length of the individual parts of the complete key for the object subtypes in Customizing for Recipe Management in the IMG activity Versioning Settings.
Example
The complete key of the EXAMPLE object is structured as follows (with a period (.) as a separator):
Version Type Complete Key
No version EXAMPLE
Simple version EXAMPLE.001
Version that can be assigned drafts EXAMPLE.001.000
Draft EXAMPLE.001.005
History
| Last changed by/on | SAP | 20031212 |
| SAP Release Created in | 471 |
