ABAP Keyword Documentation → ABAP - Release-Specific Changes → Changes in Releases 4.xx → Changes in Release 4.6A
Further Changes in Release 4.6A
2. Time zone handling in RFC calls
3. Bit operations with differing operand lengths
4. Multiple-field ASSIGN on method parameters
5. Obsolete reads on database tables
6. Error handling for file commands
Other versions: 7.31 | 7.40 | 7.54
Modification 1
Loop in Extracts
As with internal tables, SY-SUBRC is now set to 4 in an extract if, in a
LOOP ... ENDLOOP, the loop pass is not executed.
Modification 2
Time Zone Handling in RFC Calls
RFC calls in AS ABAP where the default time zone differs from the personal time zone of the user are now executed using the caller's personal time zone.
Modification 3
Bit Operations with Differing Operand Lengths
If operands with differing lengths are joined using statements such as
COMPUTE x = bitexp., all operands are standardized to the length of the
longest operand involved. The shorter operands are padded with trailing HEX 0 characters. Until now,
the length of the target field was respected, but now only the operands of the right side are considered in the calculation.
Modification 4
Multiple-Field ASSIGN on Method Parameters
ASSIGN f TO <fs> statements
on method parameters passed by reference that exceed the length of the parameter are now forbidden. This used to be allowed as long as the statement did not exceed the segment length.
Modification 5
Obsolete Read Access to Database Tables
When database tables are accessed 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-like type. Both statements are obsolete anyway, and can be replaced using appropriate SELECT statements.
Modification 6
Error Handling for File Commands
All file commands now include error handling, which means that any errors detected raise a handleable exception. Previously, only some statements set a return code in the field SY-SUBRC.