Hierarchy
MDG_FND (Software Component) MDG Foundation⤷
CA-MDG-AF (Application Component) Application Framework⤷
USMD1 (Package) Master Data: Data Modeling
Basic Data
| Data Element | USMD_CLOSED |
| Short Description | Edition Type: Retired |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | USMD_CLOSED | |
| 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 | Off |
| Medium | 15 | Retired |
| Long | 20 | Retired |
| Heading | 0 |
Documentation
Definition
Retires an edition type. A retired edition type can no longer be used for creating a new edition.
Use
Once an edition type is retired, it can no longer be activated.
Retired edition types are not used in consistency checks for data slices (for checking overlaps).
Dependencies
You can retire only edition types that have no more open editions.
You can no longer create change request types for retired edition types.
The contents of editions of retired edition types can still be read and, for example, distributed or included in an edition comparison.
Example
Until now you worked without data slices or you now want to cut an existing data slice in a different manner. In this case, you retire the respective edition types you have used up to now (after all associated open editions have been released) by selecting this indicator. Then you create new edition types with the appropriate data slices.
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in | 702 |
