SAP NetWeaver AS ABAP Release 740, ©Copyright 2014 SAP AG. All rights reserved.
ABAP Keyword Documentation → ABAP − Release-Specific Changes → Changes in Release 4.6A →
Further Changes in Release 4.6A
2. Time zone handling with Remote Function Calls
3. Bit operations with differing operand lengths
4. Multiple-field ASSIGN with method parameters
5. Obsolete read access to database tables
6. Error handling for file commands
Loop in Extracts
As with internal tables, SY-SUBRC is now set to 4 in an extract if the loop pass is not executed in a
LOOP ... ENDLOOP structure.
Time Zone Handling With Remote Function Calls
Remote Function Calls in AS ABAP, of which the default time zone differs from the personal time zone of the user are now executed using the caller's personal time zone.
Bit Operations with Differing Operand Lengths
If you link operands with differing lengths using statements such as
COMPUTE x = bitexp., all operands are extended to the length of the longest operand involved.
Shorter operands are filled with trailing HEX 0 characters. Until now, the length of the target field was also considered. Now, only the operations from the right-hand side of the calculation.
Multiple-Field ASSIGN With Method Parameters
An ASSIGN f TO <fs> statement
on a method parameter passed by reference that exceeds the length of the parameter is now forbidden. It used to be allowed as long as the statement did not exceed the segment length.
Obsolete Read Access to Database Tables
When you access database tables using the statements
READ TABLE dbtab and LOOP
AT dbtab, a runtime error occurs if the key of the database table contains components that
do not have a character type. Both statements are obsolete anyway, and can be replaced using appropriate SELECT statements.
Error handling for file commands
All file commands now include error handling, which means that errors that are recognized cause an exception that can be handled. Previously, a return value was only set in the field SY-SUBRC by some statements.