Get Example source ABAP code based on a different SAP table
VERSION 5 IN
ABAP Language Versions Each ABAP program has the program property ABAP language version, which is defined internally by a version ID. The version of a program determines which language elements and which repository objects can be used in the program and which syntax rules apply. The following versions are currently available: Language VersionMeaningVersion ID ABAP_STANDARD This version of ABAP is the universal basic version. It is an unrestricted ABAP language version that covers the entire language scope of ABAP that can be used in Unicode systems and apart from the static package concept, access to all other repository objects is allowed. The syntax check for Standard ABAP is performed as Unicode check, which is the minimum requirement for a Unicode system. The documentation of this version describes all ABAP language elements. X ABAP_FOR_KEY_USERS This version of ABAP is intended for the secure implementation of enhancements by key users within the scope of enhancement options provided by SAP. ABAP_FOR_KEY_USERS is a restricted ABAP language version where the general rules for ABAP_STANDARD apply but only a very restricted set of language elements is supported and access to repository objects is restricted as described here. Furthermore, enhancements can be implemented in methods only, where the stricter syntax rules for classes automatically apply and no obsolete language elements are allowed. The documentation of ABAP_FOR_KEY_USERS is an appropriately restricted version of the full documentation. 2 ABAP_FOR_CLOUD This version of ABAP is intended for developments in the ABAP_SAP_BTP_ENV and in the ABAP_S4_CLOUD_ENV . ABAP_FOR_CLOUD is a restricted ABAP language version where the general rules for ABAP_STANDARD apply but only a very restricted set of language elements is supported and access to repository objects is restricted as described here. Furthermore, most developments can be implemented in methods only, where the stricter syntax rules of classes automatically apply. Almost no obsolete language elements are allowed. For ABAP SQL , the most strict syntax check mode currently available is applied. The documentation for ABAP_FOR_CLOUD is a restricted version of the full documentation. 5 BEGIN_SECTION VERSION 5 OUT The version ID of a program is generally transparent for developers. From a technical perspective, the version ID is stored in the column UCCHECK of the database table TRDIR of the program properties and is usually set by the respective tools. In the statements INSERT REPORT and SYNTAX-CHECK for program processing, the version is either set implicitly or explicitly using the additions VERSION and DIRECTORY ENTRY. END_SECTION VERSION 5 OUT
Latest notes:
If a program has a version ID that is not listed in the table above, it is handled in the same way as a version that does not support any language elements.
The ABAP language versions ABAP_FOR_KEY_USERS and ABAP_FOR_CLOUD are restricted compared to standard ABAP. A restricted ABAP language version must be used in a strict ABAP development environment.
The topic Language Elements in ABAP Versions provides an overview of the ABAP language elements that are allowed in the restricted ABAP language versions compared to Standard ABAP, which is an unrestricted ABAP language version .
The topic Released APIs provides an overview of APIs that are released for the restricted ABAP language versions in the current system.
Besides ABAP programs, other repository objects can also have a property named ABAP language version.
For an overview, see also ABAP Language Versions, Release Contracts and Released APIs. NON_V5_HINTS
In addition to the ABAP language versions above, there are also some obsolete ABAP language versions that should not or can no longer be used. ABAP_HINT_END VX_EXA_ONLY
ABAP_EXAMPLE_VX The program DEMO_ABAP_VERSIONS makes it possible to check ABAP source code using the syntax rules of the different ABAP language versions. ABAP_EXAMPLE_END
