SAP ABAP Data Element SCPL_RELEASE_LEVEL (Level of a Release (Screenplay internal usage))
Hierarchy
☛
MDG_FND (Software Component) MDG Foundation
⤷
CA-MDG-APP-BP (Application Component) MDG Business Partner (Central Part)
⤷
MDG_BS_BP_GENIL_NO_TRANSL (Package) Master Data Governance: GENIL

⤷

⤷

Basic Data
Data Element | SCPL_RELEASE_LEVEL |
Short Description | Level of a Release (Screenplay internal usage) |
Data Type
Category of Dictionary Type | Direct Type Entry | |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | ||
Data Type | INT1 | 1-byte integer, integer number <= 255 |
Length | 3 | |
Decimal Places | 0 | |
Output Length | 3 | |
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 | Level |
Medium | 15 | Level |
Long | 20 | Level |
Heading | 5 | Level |
Documentation
Definition
Level of a release, only used internally by Screenplay.
Use
Releases are organised in a tree-like manner, starting with the direct remakes of an original having the lowest level. Afterwards all remakes of those remakes are added to the next level and so on up to the highest level of remake releases out there.
Dependencies
As this information is only internally used don't rely on its content in any way. In fact, currently in database table SCPLT_REMAKE this release level is contained but never filled. This might change without further notice. Hence, it is strictly recommended to not refer to the level of releases anywhere or anyhow.
Example
History
Last changed by/on | SAP | 20130604 |
SAP Release Created in | 732 |