Get Example source ABAP code based on a different SAP table
AB_SQL in ABAP Release 7.71 ITOC
ABAP_MODIFICATION_NN Null Values in the Table Buffer>
The 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 Date/Time Functions>
AB_SQL now supports the following new 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> When used, these functions require the ABAP_STRICT_771 strict mode from ABAP_RELEASE ABAP_771 / .
ABAP_MODIFICATION_NN Restrictions Removed>
For certain SQL expressions and functions> , an AB-SQL read statement no longer bypasses table buffering>.
ABAP_MODIFICATION_NN Weaker Check>
AB-SQL statements that exploit a database property not supported by all database platforms no longer produce a syntax check warning and produce a syntax warning in the extended program checks> instead.
ABAP_MODIFICATION_NN New Check>
If the data of the 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>.