SAP ABAP Data Element TRNLICENSE (License)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-CTS-ORG (Application Component) Transport Organizer
⤷ SCTS_NSP (Package) CTS: Namespaces and Naming Conventions
⤷ BC-CTS-ORG (Application Component) Transport Organizer
⤷ SCTS_NSP (Package) CTS: Namespaces and Naming Conventions
Basic Data
Data Element | TRNLICENSE |
Short Description | License |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | TRNLICENSE | |
Data Type | CHAR | Character String |
Length | 20 | |
Decimal Places | 0 | |
Output Length | 20 | |
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 | License |
Medium | 15 | License |
Long | 20 | License |
Heading | 6 | Licnse |
Documentation
Definition
To ensure that a namespace is used exclusively by its owner, changes in namespaces are protected by license checks.
There are two types of licenses:
- Development licenses
A valid development license allows SAP components and products to be developed on the basis of SAP applications. The installation number of the respective development system is encrypted in the development licenses. The license keys cannot therefore be used for other SAP Systems and must be obtained from SAP for each development system.
The namespace owner can request a development license from SAP. - Repair licenses
Repairs can be made to namespace developments with a valid license key. The license keys depend on the installation and can be delivered by the namespace owner to his customers, if necessary, to allow them to correct errors.
History
Last changed by/on | SAP | 20010130 |
SAP Release Created in |