Editing ABAP (section)

==History==
The following list only gives a rough overview about some important milestones in the history of the language ABAP. For more details, see [http://help.sap.com/abapdocu_740/en/abennews.htm ABAP – Release-Specific Changes].
{| class="wikitable"
! Version
! Release date
! Major changes
|-
| 4.6C
| May 2000
| 
* ABAP Objects
|-
| 6.40
| 2004
| 
* [https://blogs.sap.com/2004/12/09/netweaver-for-the-holidays-a-lession-in-sharing-abap-shared-memory/ Shared Objects]
|-
| 7.0
| 2006
| 
* Switch framework/Enhancement concept
|-
| 7.02
|
| 
* Expressions like: check lcl=>mi(1) + abs( -2 ) >= 3.
|-
| [http://scn.sap.com/community/abap/blog/2013/07/22/abap-news-for-release-740 7.40]
| 2012-11-29
| 
* "Code pushdown"—use advanced features from the underlying database
* Constructor expressions (NEW, VALUE, REF, CONV, CAST, EXACT, COND, SWITCH)
* Partially Implemented test classes' interfaces
* Table Expressions
* Internal table line existence/line index functions
|-
| [https://blogs.sap.com/2014/02/06/abap-news-for-release-740-sp05/ 7.40 SP05]
| December 2013
|
* MOVE-CORRESPONDING for internal tables
* LET expression in constructor expressions
* CORRESPONDING operator
* CDS Views
* ABAP Managed Database Procedures
|-
| [https://blogs.sap.com/2014/02/06/abap-news-for-release-740-sp05/ 7.40 SP08]
| September 2014
|
* FOR expressions
* Constructor operator REDUCE
* Start value for constructor expressions
* GROUP BY for internal tables
* Filter expressions and default values for table expressions
* Open SQL inline declarations after INTO statement
* Optional interface methods
|-
| [https://blogs.sap.com/2015/11/27/abap-language-news-for-release-750/ 7.50]
| November 2015
|
* New built-in data type INT8
* Relational expression IS INSTANCE OF
* Open SQL host expressions
* Open SQL expressions ROUND, CONCAT, LPAD, LENGTH, REPLACE, RIGHT, RTRIM and SUBSTRING
* Open SQL path expressions
* Open SQL SELECT UNION
* Open SQL INSERT FROM subquery
|-
| [https://blogs.sap.com/2016/11/04/abap-news-for-release-7.51/ 7.51]
| October 2016
|
* Enumerations
* Common table expressions in Open SQL
* Open SQL/CDS CROSS JOIN
* CDS client handling
* Metadata extensions in CDS
* Date and Time in Open SQL/CDS
* Floating point on Open SQL/CDS
|-
| [https://blogs.sap.com/2017/09/20/abap-news-for-release-7.52-virtual-sorting-of-internal-tables/ 7.52]
| September 2017
|
* Virtual sorting of internal tables
|-
| [https://help.sap.com/doc/abapdocu_latest_index_htm/latest/en-US/abennews-754.htm 7.54]
| September 2019
|
* New Built-In Data Types
* New Built-In ABAP Type <code>utclong</code>
* Calculation Assignments
* Decimal Places in Time Stamps
* Client Handling
* Extensions of the <code>INTO</code> Clause
* Definition of Associations
* New Aggregate Function <code>STRING_AGG</code>
* New Built-In Functions
* Addition <code>DISTINCT</code> Optional in Aggregate Function <code>COUNT</code>
* Window Expressions
* SQL Conditions Revised
* Temporal Hierarchies
* New Hierarchy Navigators
* Aggregate Expressions in SQL Expressions
* <code>CAST</code> Matrix Revised
* Strict Mode in the Syntax Check
* Syntax Check for Literals and Host Constants
* Annotation for Database Hints
* Annotations for Releasing Elements
* Specifying CDS Entities After <code>USING</code>
* Quotation Marks for Logical Schemas
* Addition <code>in place</code> of the Statement <code>late numbering</code>
* Addition <code>in class ... unique</code>
* External name of an action
* Static Field Control
* Arbitrary Name for Handler Methods
* Behavior Pool No Exceptions
* Entity Manipulation Language
* <code>TYPE STRUCTURE FOR</code>
* Response Information
* Absolute Type Names
* Business Service
* Authorization Checks in Updates
* Implicit Message Type in <code>IF_T100_DYN_MSG</code>
* Using Test Classes
* Addition <code>COMBINATION MODE OR|AND</code> of the Statement <code>GRANT SELECT ON</code>
* Addition <code>REDEFINITION</code> of the Statement <code>GRANT SELECT ON</code>
* Predicate <code>VOID</code>
* Addition <code>IN SCENARIO</code> of the Statement <code>GRANT SELECT ON</code>
* Generic Aspect Condition of the Statement <code>DEFINE ROLE</code>
* New Variant <code>INHERITING CONDITIONS FROM SUPER</code>
* Different <code>REPLACING</code> Operators
* Definition of a Generic Aspect
* DCL Restrictions for ABAP CDS Hierarchies
* DCL Restrictions for Transactional Projection View Entities
|-
| [https://help.sap.com/doc/abapdocu_latest_index_htm/latest/en-US/abennews-755.htm 7.55]
| September 2020
|
* The internal ABAP statement EXPORT NAMETAB cannot be used any more and leads to a runtime error.
* The internal ABAP statement IMPORT NAMETAB is still partly supported for reasons of downward compatibility. Any access to entries for DDIC table types leads to a runtime error. Any other access leads to errors from ATC.
* The former native database table DDNTF for separate nametab field descriptions is not supported any more and will be deleted.
* It is now possible to define new associations to external data sources in CDS projection views.
* A new kind of CDS view is available: the CDS view entity.
* The default value of profile parameter rdisp/max_alt_modes, that determines the possible number of ABAP sessions per user session, was enhanced from 6 to 16 and is now the same as the maximum number of ABAP sessions per user session.
* In the assignments behind the addition NEXT of the constructor operator REDUCE the calculation assignment operators +=, +=, *=, /= or &&=, can be used now and the respective rules apply.
* Support of Perl Compatible Regular Expressions
* Verbatim Replacements
* New Catchable Exception CX_SY_STRING_SIZE_TOO_LARGE
* Formatting option CURRENCY for decimal floating point numbers
* SQL: New aggregate function ALLOW_PRECISION_LOSS
* SQL: Optional window frame specification within a window function
* SQL: New window functions FIRST_VALUE and LAST_VALUE
* SQL: New date/time conversion functions for TIMESTAMPL, DATS and TIMS
* SQL: New time stamp functions UTCL_CURRENT, UTCL_ADD_SECONDS, and UTCL_SECONDS_BETWEEN
* SQL: New date functions DATN_DAYS_BETWEEN, DATN_ADD_DAYS, and DATN_ADD_MONTHS
* SQL: New additions after the ORDER BY clause: NULLS FIRST and NULLS LAST
* SQL: New aggregate functions MEDIAN, STDDEV, VAR, CORR, and CORR_SPEARMAN
* SQL: New geometry conversion function as_geo_json
* SQL conditions revised
* SQL: New window function NTILE
* SQL: SELECT, INTO target – host variables can now be declared inline even when the FROM-clause is dynamic
* SQL: New type conversion functions to_clob and to_blob
* SQL: New currency conversion function currency conversion
* SQL: Streaming and locators can now be used on SQL expressions
* SQL: Further data types allowed in elementary SQL expressions
* SQL: Hierarchy load options
* SQL: Typed literals
* SQL: New string functions
* SQL: Addition to the UPDATE FROM clause
* SQL: Strict mode of syntax check
* CDC Access: Check with element IS [NOT] INITIAL in a literal condition
* CDC Access: Addition bypass when
* CDC Access: Check on the user name in user conditions
* CDC Access: Data types
* CDC Access: Aspect bypass conditions
* Declaration of CX_NO_CHECK exceptions
|-
| [https://help.sap.com/doc/abapdocu_latest_index_htm/latest/en-US/abennews-756.htm 7.56]
| October 2021
|
* In ABAP Dictionary, the load unit has been extended. There are now the following settings available:
** Column Preferred
** Page Preferred
** Column Enforced
** Page Enforced
* The new statement EXTEND ABSTRACT ENTITY of the DDL of ABAP CDS makes it possible to add new elements to existing CDS abstract entities by using CDS abstract entity extensions
* In CDS abstract entities, it is now possible to define to-parent associations without ON condition. The ON condition can be left out if the association target is also a CDS abstract entity
* A hierarchy definition DEFINE HIERARCHY can now use the new addition CACHE ON|OFF|FORCE to specify the caching policy for a generated hierarchy
* For each CDS DDIC-based view (obsolete), a CDS-managed DDIC view (obsolete) is created in ABAP Dictionary upon activation
* In CDS view entities, it is now possible to reuse expressions defined in the SELECT list in other operand positions of the same CDS view entity by using the syntax $projection.reuse_exp
* UNION clauses are now supported in CDS view entities. There are a few differences to UNION clauses in CDS DDIC-based views. The most important difference is that branches of union clauses can be nested within each other in CDS view entities
* The addition DISTINCT is now available for SELECT statements in CDS view entities
* In CDS view entities, two new set operators are available:
** EXCEPT
** INTERSECT
* Two new conversion functions are available in CDS view entities:
** GET_NUMERIC_VALUE
** CURR_TO_DECFLOAT_AMOUNT
* Typed literals are now available for CDS view entities. Typed literals allow an explicit type declaration and they are available for many built-in ABAP Dictionary data types
* In CDS view entities, special handling for CDS amount fields and CDS quantity fields has been implemented. It differs from the handling of amount fields and quantity fields in DDIC, for example, more data types are possible and the currency key/unit key reference is considered in expressions
* In CDS view entities, the expression matrix has been extended:
** In the WHERE clause, arithmetic expressions and case expressions are supported as operands
** In the HAVING clause, arithmetic expressions and case expressions are supported as operands
** In a searched case expression, arithmetic expressions and case expressions are supported as operands
* In CDS projection views, it is now possible to redefine the CDS associations from the projected entity in the header part. This is done using the keyword REDEFINE ASSOCIATION. Redefinition can include a new filter, alias name, and redirection to a new association target, which must also be a CDS projection view, thus moving the complete data model to the projection layer
* It is now possible to specify a provider contract for CDS projection views using the keyword PROVIDER CONTRACT. The provider contract specifies in which scenario a CDS projection view is used, and the scenario in turn determines in which runtime the view is executed and which features are available
* The following documented ABAP program is now available for evaluating whether a migration from a CDS DDIC-based view (obsolete) to a CDS view entity is possible:
** RUTDDLS_MIGRATION_CANDIDATES
* The following documented ABAP program is now available for migrating CDS DDIC-based views to CDS view entities:
** RUTDDLSV2MIGRATION
* A new reference type for annotations is available:
** LocalDefinitionRef
* The following new AbapCatalog.extensibility annotations have been released:
** AbapCatalog.extensibility.allowNewdataSources
** AbapCatalog.extensibility.dataSources
** AbapCatalog.extensibility.elementSuffix
** AbapCatalog.extensibility.extensible
** AbapCatalog.extensibility.quota.maximumBytes
** AbapCatalog.extensibility.quota.maximumFields
* The following new CDS system table functions are available:
** ... SERIES_GENERATE_DATE( step = ... from_value = ... to_value = ... ) ...
** ... SERIES_GENERATE_INTEGER( step = ... from_value = ... to_value = ... ) ...
** ... SERIES_GENERATE_TIME( step = ... from_value = ... to_value = ... ) ...
** ... SERIES_GENERATE_TIMESTAMP( step = ... from_value = ... to_value = ... ) ...
* The following syntax can be used for the object component selector -> to access components and attributes dynamically now:
** ... { dref->(comp_name) } | { cref->(attr_name) } | { iref->(attr_name) } ...
* The dereferencing operator->* can be used for generically typed data reference variables in almost all operand positions now. Before, that was possible in the ASSIGN statement only
* It is now possible to specify MOVE-CORRESPONDING statements with the following additions in the context of nested tables in deep structures. Both ensure that nested tables of the deep target structures are not deleted and new lines of nested tables in deep source structures are added
* It is now possible to specify statements with the component operator CORRESPONDING with the following additions in the context of nested tables in deep structures. Both ensure that the nested tables of deep target structures are not deleted and new lines of nested tables in deep source structures are added:
** APPENDING BASE
* Besides the existing support of PCRE regular expressions and POSIX regular expressions (obsolete) ABAP supports now also XPath regular expressions and XSD regular expressions. Internally, those are transformed to PCRE regular expressions and processed by the PCRE2 Library
** Both kinds of regular expressions can be used by the new (factory) methods CREATE_XPATH2 and CREATE_XSD of the system classes CL_ABAP_REGEX and CL_ABAP_MATCHER
** XPath regular expressions can be used by the new argument xpath in some built-in functions
* The class CL_ABAP_MATCHER supports callouts in PCRE syntax now. The method SET_CALLOUT can be used to register a handler class that implements the interface IF_ABAP_MATCHER_CALLOUT. The special characters (?C...) of a PCRE regular expression then call the interface method CALLOUT when the method MATCH is executed
* Now, this restriction is partly removed. In the statements INSERT, APPEND, COLLECT, MODIFY, DELETE, READ, LOOP, and SORT, operands can be field symbols and formal parameters that are typed fully generically with TYPE data or TYPE any. Such operands can be used as if typed with any table. If an index access is involved, operands are still required that are typed at least with TYPE index_table
* Alias names can now be declared for secondary keys of internal tables by using the addition ALIAS of TYPES and DATA. This can be helpful when changing existing secondary keys without invalidating users
* ABAP SQL now supports the new string function INITCAP
* New Date and Time Functions
* New Casts
* ABAP SQL now supports the new set operators INTERSECT and EXCEPT
* The new parameter start can now be used in the function REPLACE_REGEXPR. Additionally, the parameter occurrence can now include expressions
* ABAP SQL now supports the new string function SUBSTRING_REGEXPR which supports regular expressions
* If one the new features listed above or one of the new CDS system table functions SERIES_GENERATE_ is used in an ABAP SQL statement, the syntax check is performed in a strict mode, which handles the statement more strictly than the regular syntax check
* From this release on, authors of access controls can mark a subset of the CDS elements used in their access conditions as optional, so that CDS entities which inherit their access conditions are not affected by a Day-1-impact any more
* With the new addition ALL, access conditions can express that access shall only be granted when from a set-valued association all values satisfy the condition
* At all locations of access controls, references to authorization objects, authorization fields, and SACF scenario names can be written in identifier syntax when they comply with it and in string syntax with single apostrophes as an alternative
* When using self-defined aspects, these can now denominate an arbitrary set of their elements (path expressions are supported) as filter element. These filter elements can by referenced when using the self-defined aspect in an access condition
* The REPLACING section formerly only available to entity-based inheritance INHERITING CONDITIONS FROM ENTITY cds_ntity is now also available for role-based inheritance INHERIT role FOR GRANT SELECT ON cds_entity
* The REPLACING section of condition inheritance now supports a generic replacement step to replace an arbitrary field or association of the inheritance source with an arbitrary field or association of the inheritance target
* Respecting settings in the switchable authorization framework (SACF) was already possible for dedicated PFCG conditions:
** ASPECT PFCG_AUTH ( S_OBJECT IN SCENARIO ... )
* For CDS hierarchies, access control was restricted to the use of conditions not resulting in database filtering. Now elements located in the declared hierarchy directory DIRECTORY ... FILTER BY can be used to formulate such conditions
* When operating the system with the emergency user SAP*, CDS access control is now deactivated
* From release 7.56 on, important settings of the ABAP Keyword Documentation can be configured explicitly. Before, the documentation was configured implicitly from system settings
* Program ABAP_DOCU_CONFIG allows a choice to be made between different sets of parameters:
** Parameter set typical for SAP development systems
** Parameter set typical for customer development systems
** Parameter set typical for SAP S/4HANA systems
** Parameter set typical for SAP S/4HANA Cloud ABAP Environment
** Parameter set typical for SAP BTP ABAP Environment
** Current parameter set
* The ABAP RESTful Application Programming Model (RAP) was enhanced
|-
| [https://help.sap.com/doc/abapdocu_latest_index_htm/latest/en-US/abennews-757.htm 7.57]
| October 2022
|
* Components of structures can be assigned to field symbols with the new syntax struc-(comp) that largely replaces the variant ASSIGN COMPONENT OF
* The new addition ELSE UNASSIGN can be specified for the following variants of the statement ASSIGN:
** dynamic assignments
** assignments of dynamic components
** dynamic access
** assignment of a table expression
* SAP HANA XSA replaces SAP HANA XSC. The access methods designed specifically for XSC objects are not suitable for XSA objects and have been declared obsolete. DDIC external views are one of those access methods. They have been declared obsolete. More information can be found in SAP Notes 2465027 and 3116165
* The new declaration operator FINAL declares an immutable variable that cannot be assigned another value at other write positions of the same context
* The new addition STEP defines the step size and the order for processing an internal table. For the statements LOOP and FOR, STEP can be used to control the step size and the processing order. For the statements APPEND, DELETE, INSERT, VALUE, and NEW, STEP can only be used to define the step size. It is not possible to change the processing order with STEP for these statements
* Access to a table index when accessing an internal table using a hash key (accessing a hashed table using its primary key or accessing any internal table using a hashed secondary key) is not allowed. When a hashed key is specified dynamically behind USING KEY in statement LOOP AT or expression FOR ... IN, usage of FROM and TO must result in an exception. This was not the case before release 7.57. From release 7.57 on, the runtime error ITAB_ILLEGAL_INDEX_OP occurs in such a situation. Before release 7.57, the behavior was undefined.
* When a negative value is specified for FROM in statement LOOP AT or expression FOR ... IN, it is set to 1 implicitly. Before release 7.57, this was not the case in the following situation:
** The internal table is accessed using a sorted key
** The internal table contains more than 10 table lines
** A WHERE condition is specified that can be optimized
* The statement IMPORT now allows assignments of data of type n to data objects of type c if they have the same length. This change might lead to incompatible behavior if handling of the former exception leads to different results than the new behavior
* CDS entity buffering was enhanced: View on view buffering is now supported, under the precondition that the CDS view entity used as data source meets certain requirements
* In CDS view entities, the addition ELSE NULL is available in simple and complex case distinctions. It defines the null value as return value of the ELSE branch
* New casting options have been added in CDS view entities
* Table buffering can be defined for CDS view entities now:
** Table buffering can be enabled and disabled with the annotation @AbapCatalog.entityBuffer.definitionAllowed: true|false
** The buffering type can be specified with a CDS entity buffer defined by DEFINE VIW ENTITY BUFFER ON cds_view_entity ...
* In CDS view entities, the SUBSTRING function has been enhanced. It now accepts not only literals, but also fields, parameters, expressions, and built-in functions as arguments pos and len
* In CDS view entities, the functions LEFT and RIGHT have been enhanced. They now accept literals, fields, parameters, expressions, and built-in functions as argument len
* In CDS view entities, two new application session variables are available:
** bs_system_id
** bs_zone_id
* Using CDS-managed DDIC views has been declared obsolete. The following ABAP program lists all repository objects that use CDS-managed DDIC views:
** RUT_WHERE_USE_SQLVIEW
* CDS analytical projection views for modelling analytical queries are available. A CDS analytical projection view is defined using DEFINE TRANSIENT VIEW ENTITY AS PROJECTION ON. The value for the provider contract must be set to ANALYTICAL_QUERY
* A new type of CDS projection view is available: the CDS transactional interface. CDS transactional interfaces serve as stable public interface layer in a CDS data model. They are typically used in the context of the ABAP RESTful Application Programming Model to provide the basis for a RAP BO interface. A CDS transactional interface view is defined using DEFINE VIEW ENTITY AS PROJECTION ON. The value for the provider contract must be set to TRANSACTIONAL_INTERFACE
* Special handling for CDS amount fields and CDS quantity fields for comparisons in CDS view entities has been implemented
* Data type abap.string is now supported for input parameters in the parameter list of a CDS view entity and in the parameter list of a CDS table function
* Data type abap.string is now supported when binding actual parameters to the input parameters of a CDS view entity, if a CDS table function is used as data source after FROM
* The new statement EXTEND CUSTOM ENTITY of the DDL of ABAP CDS makes it possible to add new elements to existing CDS custom entities by using CDS custom entity extensions
* CDS DDIC-based views (obsolete), defined using the statement DEFINE VIEW, are obsolete. When creating new data models, CDS view entities, defined using DEFINE VIEW ENTITY, should be used instead
* The obsolete ABAP language versions
** Static ABAP with restricted object use
** Standard ABAP with restricted object use
* SAP HANA XSA replaces SAP HANA XSC. The access methods designed specifically for XSC objects are not suitable for XSA objects and have been declared obsolete. This includes DDIC external views and database procedure proxies. More information can be found in SAP Notes 2465027 and 3116165
* The ABAP RESTful Application Programming Model (RAP) was enhanced
* ABAP Cheat Sheets are now available as part of the ABAP Keyword Documentation
|-
| [https://help.sap.com/doc/abapdocu_latest_index_htm/latest/en-US/abennews-758.htm 7.58]
| October 2023
|
* CDS analytical projection views can now also have analytical dimension views as projected entity.
* The CDS annotation @AbapCatalog.preserveKey is obsolete and has partly a different behavior now.
* CDS simple types define elementary data types natively in ABAP CDS. A CDS simple type can be enriched with metadata using CDS annotations. The syntax statement for defining a CDS simple type is DEFINE TYPE.
* CDS enumerated types define enumerated types natively in ABAP CDS. The syntax statement for defining a CDS enumerated type is DEFINE TYPE ENUM.
* The ABAP annotation Environment.sql.passValue is now also available for CDS parameters in CDS view entities, CDS projection views, and CDS hierarchies. The annotation scope has been enhanced.
* A new ABAP annotation is available in CDS view entities, CDS projection views, and CDS hierarchies: Environment.sql.passValueForClient. It works in a similar way to the annotation Environment.sql.passValue, but for client fields. It specifies whether a placeholder ? or a literal value is passed to the database in an ABAP SQL condition when the client field is compared with a host variable.
* A new syntax for specifying the cardinality of CDS associations, CDS joins, and of filter conditions of CDS path expressions is now available
* The new CDS entity is available: the CDS scalar function. It is defined using the CDS DDL statement DEFINE SCALAR FUNCTION. A CDS scalar function is linked with an AMDP function in which it is implemented using SQLScript.
* The matrix of types that can be converted to each other using CAST has been enhanced for CDS DDIC-based views (obsolete) and for CDS view entities. Data types DECFLOAT16 and DECFLOAT34 can now be cast into data type CURR.
* A WHERE condition is now available also for CDS transactional interfaces to restrict the result set that is returned when the transactional interface is accessed.
* Typed literals can now be used in more operand positions in ABAP CDS. They can now be used in the WHERE condition of CDS projection views and in the ON condition of CDS associations.
* A reuse expression $projection.Field can now also be used to reuse fields selected via a path expression.
* A new type of access rule is available for CDS projection views of type CDS transactional query: the projection_rule defined with the statement GRANT SELECT ON ... AS PROJECTION ON ... FALLBACK ASSOCIATION ....
* Two new DCL functions are available:
** SWITCH_RUNTIME_STATE
** TOGGLE_RUNTIME_STATE
* Two new system classes for numeric calculations are available:
** CL_ABAP_BIGINT contains methods for calculations with any size of integer in ABAP.
** CL_ABAP_RATIONAL contains methods for calculating with rational numbers without any precision loss.
* The new class CL_ABAP_DIFF compares the content of internal tables and returns information about any differences found.
* The new methods MOVE_TRUNC, MOVE_TO_SHORT_TRUNC, ADD_TO_SHORT_TRUNC and SUBTRACTSECS_TO_SHORT_TRUNC of system class CL_ABAP_TSTMP round the fractional seconds of long time stamps down while the existing methods MOVE, MOVE_TO_SHORT, ADD_TO_SHORT and SUBTRACTSECS_TO_SHORT round commercially. Since the latter might be unexpected, the new methods can be used now in order to preserve the integer part of a long time stamp.
* Using the new method GET_CURRENT_PHASE, you get information about the current RAP transactional phase.
* The new specification \LINE allows the line type of an internal table to be specified in an absolute type name. \LINE can be followed by -comp to specify the type of a component of the line type.
* In functional methods, the statement RETURN can be used to assign the result of an expression expr to the return value when terminating the method.
* The addition DEFAULT allows the assignment of values for a target component based on an expression.
* Up to now, an optimization of the WHERE condition by using key access took place only under very limited circumstances where the key value pairs had to be compared explicitly for equality and combined by AND. Now, the compiler analyzes the WHERE condition thoroughly and tries itself to extract the key/value pairs that are necessary for the key access.
* ABAP SQL expressions can be defined on the right side of a condition enclosed in parentheses.
* A new syntax for specifying the cardinality of joins is available: {MANY | ONE | {EXACT ONE}} TO {MANY | ONE | {EXACT ONE}}
* It is now possible to process multiple internal tables accessed with FROM @itab within one ABAP SQL statement with the ABAP SQL engine. Currently, this is restricted to joins of internal tables where no database tables are involved.
* With the new addition PRIVILEGED ACCESS, CDS access control can be disabled for a complete SELECT statement.
* From release 7.58 on, the ABAP Keyword Documentation display offers a function to send a feedback in non-SAP development systems and in the SAP Help Portal. Up to now, the possibility for a feedback mail existed only in SAP's own development systems. The function can be switched on or off in the configuration of the ABAP Keyword Documentation, see SAP Note 3051036.
* From release 7.58 on, the ABAP Keyword Documentation presents a new layout in ABAP development tools for Eclipse (ADT) where also a toggle between Standard ABAP and ABAP Cloud is available. The new layout includes:
** New header bar with links to the mail feedback and the web version
** Highlighted key blocks for hints, code blocks, and others
** Tables with zebra stripes
* In release 7.58, the ABAP RESTful Application Programming Model (RAP) was enhanced as follows:
** RAP BDL in ABAP Release 7.58
** ABAP EML in ABAP Release 7.58
|}