Get Example source ABAP code based on a different SAP table
Internal Tables in ABAP Release 6.10 In ABAP_RELEASE 6.10, the following enhancements have been made to internal tables: ITOC
ABAP_MODIFICATION_NN Creating a Table Object>
Any table objects can be created at runtime by using the statement CREATE DATA>>. If the table type is known in full, this is respected by the syntax check.
ABAP_MODIFICATION_NN Checking the Convertibility of Key Fields>
In the case of the statements READ TABLE itab WITH KEY k1 = v1 .... kn = vn>> and DELETE TABLE itab WITH KEY = v1 .... kn = vn>>, the system already checks whether the key values are convertible to the component type in the syntax check. This convertibility check is also effective for the newer variant READ ... WITH TABLE KEY ...>. Previously, the runtime error MOVE_NOT_SUPPORTED> was raised if the conversion was not possible.
ABAP_MODIFICATION_NN Duplicate or Overlapping Key Specifications >
In the case of duplicate or overlapping key specifications, the statement READ TABLE itab WITH KEY k1 = v1 .... kn = vn>> now raises a syntax error instead of a syntax warning. If specified dynamically, it was previously the case that the last key specification was used; now the runtime error DYN_KEY_DUPLICATE> is raised.
ABAP_MODIFICATION_NN Support for Accessing Attributes>
The addition ... COMPARING o->attr> now makes it possible to access the attributes of objects that are components of internal tables, similar to when reading, changing, deleting, or sorting internal tables.
ABAP_MODIFICATION_NN Table Categories for Text Pools and IN > Conditions>
Alongside standard tables>, the tables categories> HASHED> and SORTED > are supported for the statements READ> >, DELETE>>, and INSERT TEXTPOOL ... >>. The IN> conditions for SELECT ... WHERE >> and LOOP ... WHERE> > are also no longer dependent on the table category.