SAP NEWS-753-ABAP SQL Get Example source ABAP code based on a different SAP tableSAP Help
AB_SQL in ABAP Release 7.53 ITOC
ABAP_MODIFICATION_NN Open SQL Renamed as AB_SQL The existing name
Open SQL has been changed to AB_SQL . This renaming reflects that some parts of AB_SQL now only support certain database platforms, specifically SAP HANA database, and hence that it is no longer fully platform-independent. ABAP_MODIFICATION_NN Access to Hierarchy Data hierarchies and hierarchy navigators data sources. Accessing hierarchy data triggers the ABAP_STRICT_773 strict mode from ABAP_RELEASE ABAP_773 / . ABAP_MODIFICATION_NN Secondary Connections SAP HANA database as its standard database, only those secondary connections should be used from the database table DBCON whose secondary database is also a SAP HANA database. Alongside the CONNECTION addition in ABAP SQL, this also applies to Native SQL (ADBC and EXEC SQL). SAP HANA Smart Data Access (SDA) should be used instead. In SDA, secondary databases are addressed from the SAP HANA database using special qualified names or by using virtual tables. If a SAP HANA database is used as a standard AS ABAP database, ABAP programs can use these names across the standard connection. This is only possible in AMDP and Native SQL. Database Shared Libraries (DBSL) are no longer required here. ABAP_MODIFICATION_NN Relational Expression IS INITIAL IS $[NOT$] INITIAL can now be used in a condition sql_cond to compare operands with their type-dependent initial value. ABAP_MODIFICATION_NN Date/Time Functions Time functions TIMS_IS_VALID Time stamp functions TSTMP_IS_VALID TSTMP_CURRENT_UTCTIMESTAMP TSTMP_SECONDS_BETWEEN TSTMP_ADD_SECONDS Date/time conversions TSTMP_TO_DATS TSTMP_TO_TIMS TSTMP_TO_DST DATS_TIMS_TO_TSTMP Time zone functions ABAP_SYSTEM_TIMEZONE ABAP_USER_TIMEZONE ABAP_MODIFICATION_NN Exposing CDS Associations of Common Table Expressions CDS views are accessed within a common table expression, the addition WITH ASSOCIATIONS of the statement WITH can now be used to publish associations of these views for use in path expressions of the current WITH statement. The addition REDIRECTED TO can also be used to replace the target data source of the published association with a previous CTE or the current CTE. ABAP_MODIFICATION_NN Numeric Literals in the SELECT List numeric literals whose value matched the value range of the type INT4 could be specified as elementary SQL expressions in the SELECT list of a query. Now numeric literals of up to 31 digits can be specified, which are interpreted as numbers of the type DEC if the value range of INT4 is exceeded. ABAP_MODIFICATION_NN Enhanced Cast Matrix cast expression can now be used to convert the data types INT1, INT2, INT4, and INT8 to DEC. ABAP_MODIFICATION_NN Client Handling in Subquery of the Statement INSERT USING CLIENT of the statement INSERT can now be specified in a subquery. This means that the client specified for the target table of the insert operation can be different from the client specified for the data source of the subquery. USING CLIENT is not specified in the subquery, the current client ID is now always applied to automatic client handling. Before ABAP_RELEASE ABAP_773 , the client ID specified after INSERT using USING CLIENT was also used in the subquery. FROM clause of the subquery can now access the database table or classic view filled using the INSERT statement. This makes it possible to copy the data from one client to another. USING CLIENT or accessing the database table or classic view filled by the INSERT statement enables ABAP_STRICT_773 strict mode from ABAP_RELEASE ABAP_773 / . ABAP_MODIFICATION_NN Subquery as Data Source of MODIFY MODIFY , a parenthesized subquery SELECT subquery_clauses can now be specified as a data source after FROM. The rows of the results set of the subquery are modified or inserted in the target table directly on the database. No data transport is required between the database and AS ABAP. When used in MODIFY , a subquery demands ABAP_STRICT_773 strict mode from ABAP_RELEASE ABAP_773 / . ABAP_MODIFICATION_NN USING CLIENT and Session Variable client queries access client-specific CDS views and the client handling method is defined using the annotation @ClientHandling.algorithm:#SESSION_VARIABLE, the session variable client (which corresponds to the ABAP-specific session variable CDS_CLIENT on the SAP HANA database) must be set to the same value in all of these queries. The runtime error SAPSQL_DIFFERENT_CLIENT_VALUES occurs if USING CLIENT is used to specify a different client ID in one of these queries. This situation can occur in the statement WITH or when using UNION. ABAP_MODIFICATION_NN Null Values in the Table Buffer table buffer now supports real null values. In table buffering, null values are no longer transformed to type-dependent initial values. When the buffer is accessed, the same results are produced as when the database is accessed directly. The corresponding restrictions now no longer apply. The following are some of the aspects affected: Relational expressions with operands that contain null values. The result of a comparison of this type is now also unknown when the comparison is made in the buffer (except in the expression IS $[NOT$] NULL). If used, IS $[NOT$] NULL no longer bypasses table buffering. Accesses to buffered CDS views. When the buffer is accessed, the same results are now produced as when the database is accessed directly. Null values are often produced by outer joins or in expressions such as case distinction expressions. The restriction specifying that only those CDS views are buffered whose elements do not contain null values no longer applies. ABAP_MODIFICATION_NN Restrictions Removed For certain SQL expressions and functions , an AB-SQL read statement no longer bypasses table buffering. AB-SQL read statements no longer bypass table buffering in cases where a column is specified on the right side of comparisons or of BETWEEN in a condition that is not required to identify a single row or a generic range. The prerequisite for this is that both operands are numeric but do not have the type DF16_DEC or DF34_DEC, that both operands are character-like, or that both operands have the type RAW with the same lengths. ABAP_MODIFICATION_NN Weaker Check extended program checks instead. ABAP_MODIFICATION_NN New Check internal table needs to be transported to the database in cases where the internal table is used as a data source of the AB-SQL statement SELECT, a syntax check warning occurs that can be hidden using the pragma ##itab_db_select. ABAP_MODIFICATION_NN Replacement Service in Program Calls ACTIVATE_REPLACEMENT of the class CL_OSQL_REPLACE has the new parameter FLG_SURVIVE_SUBMIT, which now also permits redirections in called programs. ABAP_MODIFICATION_NN GROUP BY Addition GROUPING SETS SELECT statement, the GROUP BY addition GROUPING SETS can now be used. The addition GROUPING SETS makes it possible to group multiple grouping sets under one GROUP BY clause. This is the same as specifying UNION ALL with different GROUP BY clauses. The addition GROUPING SETS has an advantage over a UNION clause grouping because the SELECT clause only needs to be specified once. GROUPING SETS triggers ABAP_STRICT_773 strict mode from ABAP_RELEASE ABAP_773 / . ABAP_MODIFICATION_NN Aggregate Function GROUPING GROUPING can now be used in a SELECT statement. The grouping function GROUPING can be used to verify whether a specific column is part of the aggregation. The grouping function can be used only if the GROUP BY clause contains the addition GROUPING SETS. ABAP_MODIFICATION_NN Stricter Checks on Syntax Rules strict modes of the syntax check, these violations already produced a syntax error. Outside the strict modes, they produced a syntax check warning and in most cases a runtime error when the program was executed. When a view is accessed, its key fields must be located together at the start. The additions USING CLIENT and CLIENT SPECIFIED cannot be used when a CDS entity is accessed that is associated with a CDS role. Even when using path expressions, the addition CLIENT SPECIFIED can only be used for client-specific data sources. When a column is specified, the actual names of the components must be used for a database table containing an 