SAP ABAP Data Element TSEGVERTYP (Version type of event / time)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
CRM-BF (Application Component) Basic Functions
⤷
VLTS (Package) Time segment
BBPCRM (Software Component) BBPCRM⤷
CRM-BF (Application Component) Basic Functions⤷
VLTS (Package) Time segment
Basic Data
| Data Element | TSEGVERTYP |
| Short Description | Version type of event / time |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | TSEGVERTYP | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table | TTSEGVERT |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | VERSION_TYPE | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Vers. type |
| Medium | 15 | Version type |
| Long | 20 | Version type |
| Heading | 22 | Version type |
Documentation
Definition
Events can be saved in parallel versions (planned, actual, forecasting). For example, you can save the planned or the actual deadline for arrival at the customer.
Use
You assign one of the three pre-defined version types (actual, planned, or forecasting) to the application document data (date and time or time zone and time stamp).
You cannot define some version types.
For example, you specify the version type when defining the inline time.
History
| Last changed by/on | SAP | 19990421 |
| SAP Release Created in |
