SAP ABAP Data Element ESEVERSFLG (Report must be versioned)
Hierarchy
☛
EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials
⤷
EHS-SAF (Application Component) Product Safety
⤷
CBUI (Package) Company Environment Information System
EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials⤷
EHS-SAF (Application Component) Product Safety⤷
CBUI (Package) Company Environment Information System
Basic Data
| Data Element | ESEVERSFLG |
| Short Description | Report must be versioned |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR1 | |
| 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 | Vers. ind. |
| Medium | 16 | Vers. indicator |
| Long | 25 | Version requirement |
| Heading | 3 | VIn |
Documentation
Use
The indicator belongs to the generation variant. If the indicator is set, the corresponding report must be versioned.
Dependencies
The report is versioned during status change from CO (Complete) to RE (Released).
If the SAP system does not find a previous version, a dialog box appears in which you can define the version yourself.
If the SAP system does find a previous version, it assigns the new version automatically, whilst taking the relevancy indicator into account:
- If the relevancy indicator is set, the main version is promoted (v1.0 -> v2.0, for example).
- If the relevancy indicator is not set, the sub-version is promoted (v1.1 -> v1.2, for example).
History
| Last changed by/on | SAP | 20011002 |
| SAP Release Created in |
