Get Example source ABAP code based on a different SAP table
Further Changes in ABAP Release 4.6A ITOC
ABAP_MODIFICATION_NN 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.
ABAP_MODIFICATION_NN 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.
ABAP_MODIFICATION_NN 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.
ABAP_MODIFICATION_NN Multiple-Field ASSIGN> on Method Parameters>
ASSIGN f TO <(><)>>> 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.
ABAP_MODIFICATION_NN 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.